Internal transaction management device, internal transaction management method, and internal transaction management program

Abstract

The objective is to provide an internal transaction management system that enables appropriate internal transactions between the requesting department and the requesting department by detecting the difference between the cost amount and the allowable amount. [Solution] The internal transaction management device includes a display control unit that displays a budget input screen and a sales input screen on a display unit; a variance detection unit that compares a budget amount previously registered by the user on the requesting department side from the budget input screen with a cost amount registered by the user from the sales input screen, and detects whether the cost amount exceeds an allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount; a notification unit that notifies the user when the variance detection unit detects that the cost amount exceeds the allowable amount; and a screen switching unit that allows the user to input the variance factor from the sales input screen.

Description

Technical Field

[0001] The present invention relates to an in-company transaction management device, an in-company transaction management method, and an in-company transaction management program.

Background Art

[0002] For example, Patent Document 1 discloses an inter-company electronic transaction system, an inter-company electronic transaction method, and an inter-company electronic transaction program that can perform inter-company transactions between affiliated companies inefficiently and quickly.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, when a request is made between departments within a company and an in-company transaction is carried out between the requesting department and the receiving department, an additional contract is often not concluded when changes in the content occur. Therefore, there is a possibility that a difference occurs between the planned amount (budget amount) and the actual amount spent (cost amount), and as a result, it may be difficult to perform an appropriate in-company transaction between the requesting department and the receiving department.

[0005] The present invention has been made in view of the above circumstances, and an object thereof is to provide an in-company transaction management device, an in-company transaction management method, and an in-company transaction management program capable of performing an appropriate in-company transaction between a requesting department and a receiving department.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the internal transaction management device according to the present invention is an internal transaction management device that includes a control unit and manages the income and expenses arising from internal transactions to ensure fairness and transparency of said internal transactions, and is able to access an internal transaction cost variance rate master which associates a cost variance rate with each budget amount recorded as the sales amount of the requesting department, and the control unit is characterized by comprising: a display control unit which displays a budget input screen and a sales input screen on a display unit; a variance detection unit which compares a budget amount previously registered by a user on the requesting department side from the budget input screen with a cost amount registered by the user from the sales input screen and detects whether the cost amount exceeds an allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount; a notification unit which notifies the user when the variance detection unit detects that the cost amount exceeds the allowable amount; and a screen switching unit which causes the user to input the variance factor from the sales input screen.

[0007] Furthermore, the internal transaction management method according to the present invention is characterized by including: a display control step in which a display control unit causes a budget input screen and a sales input screen to be displayed on a display unit; a difference detection step in which a difference detection unit compares a budget amount previously registered by a user on the requesting department side from the budget input screen with a cost amount registered by the user from the sales input screen, and detects whether the cost amount exceeds an allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount; a notification step in which a notification unit notifies the user if the difference detection unit has detected that the cost amount exceeds the allowable amount; and a screen switching step in which a screen switching unit causes the user to input the difference factors from the sales input screen.

[0008] Furthermore, the internal transaction management program according to the present invention is designed to enable the internal transaction management device to function as: a display control means for displaying a budget input screen and a sales input screen on a display unit; a variance detection means for comparing a budget amount previously registered by a user on the client department side from the budget input screen with a cost amount registered by the user from the sales input screen, and detecting whether the cost amount exceeds an allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount; a notification means for notifying the user if it is detected that the cost amount exceeds the allowable amount; and a screen switching means for prompting the user to input the variance factors from the sales input screen. [Effects of the Invention]

[0009] This invention makes it possible to detect the difference between the cost amount and the allowable amount, and has the effect of enabling appropriate internal transactions between the requesting department and the requesting department. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the internal transaction management system according to this embodiment. [Figure 2] Figure 2 shows an example of an internal transaction expense master table in the internal transaction expense master stored in the storage unit of the internal transaction management device according to this embodiment. [Figure 3] Figure 3 shows an example of an internal transaction cost variance master table in the internal transaction cost variance master stored in the storage unit of the internal transaction management device according to this embodiment. [Figure 4] Figure 4 shows an example of a WF (Waveflow) performed by the internal transaction management system according to this embodiment. [Figure 5] Figure 5 shows an example of contract information data generated by the generation unit of the in-house transaction management device according to this embodiment. [Figure 6] Figure 6 shows an example of the budget input screen of the internal transaction management system according to this embodiment. [Figure 7] Figure 7 shows an example of budget data and budget detail data generated by the generation unit of the internal transaction management device according to this embodiment. [Figure 8] Figure 8 shows an example of contract information data generated by the generation unit of the in-house transaction management device according to this embodiment. [Figure 9] Figure 9 shows an example of the budget input screen of the internal transaction management system according to this embodiment. [Figure 10] Figure 10 shows an example of budget data and budget detail data generated by the generation unit of the internal transaction management device according to this embodiment. [Figure 11] Figure 11 shows an example of the WF unapproved list screen of the internal transaction management system according to this embodiment. [Figure 12] Figure 12 shows an example of an email sent by the notification unit of the internal transaction management system according to this embodiment. [Figure 13] Figure 13 shows an example of contract information data updated by the update unit of the in-house transaction management device according to this embodiment. [Figure 14] Figure 14 shows an example of the budget input screen of the internal transaction management system according to this embodiment. [Figure 15] Figure 15 shows an example of budget data and budget detail data generated by the generation unit of the internal transaction management device according to this embodiment. [Figure 16] Figure 16 shows an example of an email sent by the notification unit of the internal transaction management system according to this embodiment. [Figure 17] Figure 17 shows an example of contract information data updated by the update unit of the in-house transaction management device according to this embodiment. [Figure 18] Figure 18 shows an example of cost detail data generated by the generation unit of the in-house transaction management device according to this embodiment. [Figure 19] Figure 19 shows an example of the sales input screen of the in-house transaction management system according to this embodiment. [Figure 20]FIG. 20 is a diagram showing an example of sales data and detailed difference factor data generated by the generation unit of the in-company transaction management apparatus according to the present embodiment. [Figure 21] FIG. 21 is a diagram showing an example of a sales input screen of the in-company transaction management apparatus according to the present embodiment. [Figure 22] FIG. 22 is a diagram showing an example of accounting judgment item data generated by the generation unit of the in-company transaction management apparatus according to the present embodiment. [Figure 23] FIG. 23 is a diagram showing an example of a sales input screen of the in-company transaction management apparatus according to the present embodiment. [Embodiments for Carrying Out the Invention]

[0011] Embodiments of an in-company transaction management apparatus, an in-company transaction management method, and an in-company transaction management program according to the present invention will be described in detail below based on the drawings. Note that the present invention is not limited to the present embodiment.

[0012] [1. Configuration] An example of the configuration of the in-company transaction management apparatus 100 according to the present embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a block diagram showing an example of the configuration of the in-company transaction management apparatus 100.

[0013] The in-company transaction management apparatus 100 is for ensuring fairness and transparency of the in-company transaction by managing income and expenses generated in the in-company transaction. The in-company transaction management apparatus 100 is constructed based on a commercially available desktop personal computer. Note that the in-company transaction management apparatus 100 is not limited to being constructed based on a stationary information processing apparatus such as a desktop personal computer, and may be constructed based on a portable information processing apparatus such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0014] The internal transaction 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 component of the internal transaction management device 100 is connected to communicate via any communication path.

[0015] The communication interface unit 104 connects the internal transaction management 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 internal transaction management device 100 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). The data stored in the storage unit 106 may be stored in, for example, the server 200.

[0016] 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 home television), a speaker, or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. Note that in the following, the output device 114 may be referred to as the monitor 114.

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

[0018] The memory unit 106 stores master data such as the internal transaction expense master 106a and the internal transaction cost variance rate master 106b.

[0019] The internal transaction expense master 106a is a master created by the requesting department. Furthermore, the internal transaction expense master 106a stores a corresponding multiplier for each total budget amount of the requesting department to the requesting department.

[0020] Figure 2 shows an example of the internal transaction expense master table for internal transaction expense master 106a. As shown in Figure 2, a budget total amount of "¥500,000" is associated with a markup rate of "105%". Similarly, a budget total amount of "¥1,000,000" is associated with a markup rate of "110%". Furthermore, budget total amounts of "¥1,500,000", "¥2,000,000", and "¥2,500,000" are associated with a markup rate of "120%", respectively. The budget total amount here is the sum of the budget amounts set by the requesting department for the requesting department before the requesting department accepts the request, and the markup rate is the ratio of internal transaction expenses to the budget amount. Internal transaction expenses are the contract amount that arises between the requesting department and the requesting department when the requesting department accepts the request, that is, the sales amount of the requesting department to the requesting department. Furthermore, the total budget amount in the internal transaction expense master table shown in Figure 2 represents the upper limit of the amount to which the multiplier set corresponding to that total budget amount is applied. The total budget amount and the multiplier may also be stored together with the date on which the multiplier was determined or revised (the revision date shown in Figure 2). With this configuration, the internal transaction expense master 106a can identify the multiplier by the total budget amount of the requesting department to the requesting department.

[0021] The internal transaction cost variance rate master 106b stores cost variance rates associated with each budgeted amount recorded as sales revenue for the requesting department to the requesting department.

[0022] Figure 3 shows an example of the internal transaction cost variance master table of internal transaction cost variance master 106b. As shown in Figure 3, the lower limit of the cost variance rate, "90%", and the upper limit of the cost variance rate, "100%", are associated and stored with the sales amount "¥500,000". Also, the lower limit of the cost variance rate, "90%", and the upper limit of the cost variance rate, "105%", are associated and stored with the sales amount "¥1,000,000". Furthermore, the lower limit of the cost variance rate, "90%", and the upper limit of the cost variance rate, "110%", are associated and stored with the sales amount "¥2,000,000" and "¥2,500,000". The cost variance rate referred to here is the ratio of the cost amount (actual amount incurred) to the budget amount (planned amount). The lower and upper limits of the cost variance rate represent the acceptable range of cost amounts relative to the budget amount. The sales amount and cost variance rate may also be stored together with the date on which the cost variance rate was determined or revised (the revision date shown in Figure 3). With this configuration, the internal transaction cost variance rate master 106b can identify the acceptable range of cost amounts relative to the budget amount based on the sales amount of the requesting department relative to the requesting department.

[0023] Furthermore, the storage unit 106 stores transaction data such as contract information data 106c, budget data 106d, budget detail data 106e, cost detail data 106f, sales data 106g, variance factor detail data 106h, and accounting judgment item data 106i, which are generated by the generation unit 102g. Details will be described later.

[0024] The contract information data 106c shown in Figure 5 is data created by the requesting department. In the contract information data 106c in Figure 5, Project NO is a number used to manage projects handled by the requesting department, and Project Name is the name of the project. Contract Date is the date the project budget is registered, Department is the name of the department in charge of the project, i.e., the name of the requesting department. Customer is the name of the requesting department's business partner, Sales Amount is the contract amount for the project (construction in this embodiment) undertaken from the business partner, and Construction Period is the construction period (or the contract period between the requesting department and the business partner). In the following explanation, "project budget" will be simply referred to as "budget".

[0025] Furthermore, the contract information data 106c shown in Figure 8 is data created by the requesting department based on the contract information data 106c created by the requesting department. In the contract information data 106c in Figure 8, the Project No. is a number used to manage projects (internal transaction projects) that the requesting department is in charge of at the request of the requesting department, and the Project Name is the name of the project. The Department is the name of the department in charge of the project, i.e., the name of the requesting department, and the Customer is the name of the requesting department's business partner, i.e., the name of the requesting department. The Sales Amount is the contract amount incurred between the requesting department and the requesting department. The Construction Period is the construction period (internal transaction period between the requesting department and the requesting department). The Internal Transaction Project Number is a number corresponding to the Project No. in the contract information data 106c created by the requesting department. The Number of Internal Transaction Budget Changes is the number of times the budget amount of the requesting department to the requesting department has been changed. The Internal Transaction Detail Line Number is the line number in the budget detail data 106e described later.

[0026] Furthermore, the budget data 106d shown in Figure 7 is data created by the requesting department. In the budget data 106d in Figure 7, the Project No. is a number used to manage projects handled by the requesting department, and it corresponds to the Project No. in the contract information data 106c created by the requesting department. The budget registration date is the date the budget is registered or revised, and it corresponds to the contract date in the contract information data 106c created by the requesting department, or the date entered in the budget registration date field on the budget input screen P (see Figure 14) when the budget is revised by the requesting department. The number of budget changes is the number of times the budget amount of the requesting department has been changed. The sales amount is the contract amount for the project undertaken from the client, and it corresponds to the sales amount in the contract information data 106c created by the requesting department. The total budget amount is the total budget amount for the project, and the projected profit is the sales amount minus the total budget amount.

[0027] Furthermore, the budget data 106d shown in Figure 10 is data created by the requesting department. In the budget data 106d in Figure 10, the Project No. is a number used to manage projects handled by the requesting department at the request of the requesting department, and corresponds to the Project No. in the contract information data 106c created by the requesting department. The budget registration date is the date the budget is registered or revised, and corresponds to the budget registration date in the budget data 106d created by the requesting department. The number of budget changes is the number of times the budget amount of the requesting department has been changed, and corresponds to the number of budget changes in the budget data 106d created by the requesting department. The total budget amount is the sum of the budget amounts for the project. The sales amount is the contract amount that arises between the requesting department and the requesting department when the requesting department accepts the request, and is calculated by multiplying the total budget amount by the multiplier referenced from the internal transaction expense master 106a based on the total budget amount. Furthermore, projected profit is the amount obtained by subtracting the total budget from the sales amount.

[0028] Furthermore, the budget detail data 106e shown in Figure 7 is data created by the requesting department. In the budget detail data 106e in Figure 7, the Project No. is a number used to manage projects handled by the requesting department, and corresponds to the Project No. in the contract information data 106c and budget data 106d created by the requesting department. The budget registration date is the date the budget is registered or revised, and corresponds to the budget registration date in the budget data 106d created by the requesting department, or the date entered in the budget registration date field on the budget input screen P (see Figure 14) when the budget is revised by the requesting department. The number of budget changes is the number of times the budget amount of the requesting department has been changed, and corresponds to the number of budget changes in the budget data 106d created by the requesting department. The detail line number is the line number in the budget detail data 106e. The cost account is the expense item that classifies the costs related to the project. Furthermore, the counterparty is the name of the business partner of the requesting department, for example, if the cost item is outsourcing expenses or internal transaction expenses. The budgeted amount is the budgeted amount for each cost item, and is a breakdown of the total budgeted amount in budget data 106d created by the requesting department.

[0029] Furthermore, the budget detail data 106e shown in Figure 10 is data created by the requesting department. In the budget detail data 106e in Figure 10, the Project No. is a number used to manage projects handled by the requesting department at the request of the requesting department, and corresponds to the Project No. in the contract information data 106c and budget data 106d created by the requesting department. The budget registration date is the date the budget is registered or revised, and corresponds to the budget registration date in the budget data 106d created by the requesting department. The number of budget changes is the number of times the budget amount of the requesting department has been changed, and corresponds to the number of budget changes in the budget data 106d created by the requesting department. The detail line number is the line number in the budget detail data 106e. The cost item is the expense item that classifies the costs related to the project. The counterparty is the name of the business partner of the requesting department, for example, if the cost item is outsourcing expenses or internal transaction expenses. Furthermore, the budgeted amount is the budgeted amount for each cost item, and is a breakdown of the total budgeted amount in budget data 106d created by the requesting department.

[0030] Furthermore, the cost detail data 106f shown in Figure 18 is data created by the requesting department. In the cost detail data 106f in Figure 18, the Project No. is a number used to manage projects handled by the requesting department at the request of the requesting department, and it corresponds to the Project No. in the contract information data 106c, budget data 106d, and budget detail data 106e created by the requesting department. The detail line number is the line number in the cost detail data 106f. The cost account is the expense item that classifies the costs related to the project. The counterparty is the name of the business partner of the requesting department, for example, if the cost account is outsourcing expenses or internal transaction expenses. The cost amount is the cost amount for each cost account.

[0031] Furthermore, the sales data 106g shown in Figure 20 is data created by the requesting department. In the sales data 106g in Figure 20, the project number is a number used to manage projects handled by the requesting department at the request of the requesting department, and it corresponds to the project number in the contract information data 106c, budget data 106d, budget detail data 106e, and cost detail data 106f created by the requesting department. The sales date is the date on which the project's sales are recorded, and the sales amount is the sum of the cost amounts in the cost detail data 106f. The budget amount is the sum of the total budget amount in the budget data 106d and the budget detail data 106e created by the requesting department. The variance factor is a number used to identify the classification of multiple pre-defined variance factors.

[0032] Furthermore, the detailed data 106h of the difference factors shown in Figure 20 is string data created by the requesting department.

[0033] Furthermore, the accounting judgment data 106i shown in Figure 22 is string data created by a third-party department (in this embodiment, the accounting department) that is established separately from the requesting department and the receiving department.

[0034] Next, referring again to Figure 1, the control unit 102 will be described. The control unit 102 is a CPU, etc., that comprehensively controls the internal transaction management device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. The control unit 102 comprises a display control unit 102a, a contract amount calculation unit 102b, an update unit 102c, a difference detection unit 102d, a notification unit 102e, a screen switching unit 102f, a generation unit 102g, and an output unit 102h.

[0035] The display control unit 102a displays various screens on the display unit (in this embodiment, the monitor 114) according to the processing performed by the user. Specifically, when a user from the requesting department processes contract information, the display control unit 102a displays a contract information input screen (not shown) on the monitor 114 on the requesting department side. Also, when a user from the receiving department processes contract information, the display control unit 102a displays a contract information input screen (not shown) on the monitor 114 on the receiving department side. Furthermore, when a user from the requesting department processes a budget, the display control unit 102a displays a budget input screen P on the monitor 114 on the requesting department side. Also, when a user from the receiving department processes a budget, the display control unit 102a displays a budget input screen P on the monitor 114 on the receiving department side. Furthermore, when a user from the receiving department processes a WF (workflow) approval process, the display control unit 102a displays a budget approval screen, which is displayed as the WF unapproved list screen Q, on the monitor 114 on the receiving department side. Furthermore, if a user in the requesting department processes sales after approving the budget, the sales input screen R is displayed on the requesting department's monitor 114.

[0036] The contract amount calculation unit 102b calculates the sales amount for the requesting department from the requesting department based on the total budget amount registered by the user on the requesting department side from the budget input screen P and the multiplier referenced from the internal transaction expense master 106a based on the total budget amount. Then, by calculating the sales amount for the requesting department, the contract amount calculation unit 102b calculates the contract amount that will be incurred between the requesting department and the requesting department.

[0037] If the sales amount displayed on the WF Unapproved List screen Q is approved by the user on the client department side, the update unit 102c updates the sales amount value in the contract information data 106c created by the client department to the contract amount value calculated by the contract amount calculation unit 102b (the value approved by the user on the client department side).

[0038] Furthermore, if the sales amount displayed on the WF Unapproved List Screen Q is approved by a user on the requesting department side, the update unit 102c updates the value of the budget amount for the requesting department, which was previously entered by the requesting department, to the value of the budget amount in the budget detail data 106e created by the requesting department, with the value of the contract amount calculated by the contract amount calculation unit 102b.

[0039] Furthermore, the update unit 102c updates the total budget amount and the projected profit in the budget data 106d created by the requesting department based on the updated budget amount. The update unit 102c then increments the number of projected changes in the budget data 106d created by the requesting department by one.

[0040] Furthermore, if the sales amount displayed on the WF Unapproved List screen Q is rejected by a user on the client department side, the update unit 102c adds information on the lost deal category to the contract information data 106c created by the client department, and updates the lost deal category to "lost deal".

[0041] The variance detection unit 102d compares the budget amount registered in advance by the user on the client department side from the budget input screen P with the cost amount registered by the user on the client department side from the cost details input screen, which serves as the sales input screen. The variance detection unit 102d then determines whether the cost amount is within the range of the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master 106b based on the budget amount. The variance detection unit 102d may also be configured to detect whether the cost amount exceeds the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master 106b based on the budget amount. Furthermore, the budget amount here refers to the sum of the budget amounts (total budget amount) if there are multiple budgets registered by the user on the client department side, and the cost amount refers to the sum of the cost amounts (total cost amount) if there are multiple costs registered by the user on the client department side.

[0042] The notification unit 102e notifies the user on the requesting department side if the budget is approved by the requesting department and the contract amount between the requesting department and the requesting department exceeds the budget amount planned by the requesting department. The notification unit 102e also notifies the user on the requesting department side if the budget is rejected by the requesting department. The notification unit 102e also notifies the user on the requesting department side if the difference detection unit 102d detects that the cost amount is outside the acceptable range. The notification unit 102e also notifies the third-party department (the accounting department in this embodiment) if a difference factor is registered by the user on the requesting department side from the sales input screen R.

[0043] The screen switching unit 102f switches the screen of the sales input screen R that the user on the client department side is using, and restricts the items that can be entered on that sales input screen R. Then, the screen switching unit 102f makes the items related to the variance factors into inputable items, so that the user on the client department side can enter the variance factors from the sales input screen R.

[0044] The generation unit 102g generates contract information data 106c, etc., according to the information registered by the user on the requesting department side when the user on the requesting department side processes the input of contract information. In addition, the generation unit 102g generates budget data 106d, budget detail data 106e, etc., according to the information registered by the user on the requesting department side from the budget input screen P when the user on the requesting department side processes the input of budget.

[0045] Furthermore, when a user on the client department side processes contract information, the generation unit 102g generates contract information data 106c, etc., according to the information registered by the user on the client department side. Also, when a user on the client department side processes budget information, the generation unit 102g generates budget data 106d, budget detail data 106e, etc., according to the information registered by the user on the client department side from the budget input screen P. Furthermore, when a user on the client department side processes sales accounting, the generation unit 102g generates cost detail data 106f, etc., according to the information registered by the user on the client department side, and generates sales data 106g, variance factor detail data 106h, etc., according to the information registered by the user on the client department side from the sales input screen R.

[0046] Furthermore, the generation unit 102g generates accounting judgment data 106i, etc., according to the information registered by the accounting department user from the sales input screen R after the user on the requesting department side has completed the sales accounting process.

[0047] The output unit 102h outputs various information contained in the contract information data 106c registered by the user on the requesting department side to the budget input screen P when the user on the requesting department side processes the input of contract information. The output unit 102h also outputs various information contained in the contract information data 106c registered by the user on the requesting department side to the budget input screen P when the user on the requesting department side processes the input of budget. Furthermore, the output unit 102h outputs various information contained in the contract information data 106c and budget data 106d registered by the user on the requesting department side to the WF unapproved list screen Q when the user on the requesting department side processes the approval of budget.

[0048] Furthermore, when a user on the requesting department side performs budget revision processing, the output unit 102h outputs various information contained in the contract information data 106c, budget data 106d, and budget detail data 106e, which have been updated by the update unit 102c, to the budget input screen P.

[0049] Furthermore, when a user on the client department side processes the sales accounting, the output unit 102h outputs the information in the contract information data 106c, budget detail data 106e, and cost detail data 106f registered by the user on the client department side, as well as the information in the contract information data 106c, budget detail data 106e, and cost detail data 106f updated by the update unit 102c, to the sales input screen R. At the same time, the output unit 102h outputs the allowable amount calculated from the initial sales amount registered by the user on the requesting department side (i.e., the budget amount registered by the user on the client department side) and the cost variance rate referenced from the internal transaction cost variance rate master 106b based on that sales amount to the sales input screen R.

[0050] [2. Specific examples of processing] A specific example of the processing performed by the internal transaction management device 100 configured as described above will be explained with reference to Figures 4 to 23. Figure 4 is a diagram showing an example of a WF (workflow) performed by the internal transaction management device 100.

[0051] The internal transaction management device 100 performs steps S1 to S20 described below as a WF system for internal transactions. First, when the requesting department undertakes a construction project from a business partner, the user on the requesting department side performs input processing of contract information and budget. At this time, the display control unit 102a displays the contract information input screen on the monitor 114 on the requesting department side (step S1). The contract information input screen (not shown) includes cells for entering project number, project name, contract date, department, customer, sales amount, construction period, etc., and the display control unit 102a displays the contract information input screen on the monitor 114 on the requesting department side with each cell blank. Then, as shown in Figure 5, the generation unit 102g generates contract information data 106c from the contract information input screen according to the information registered by the user on the requesting department side.

[0052] Then, the display control unit 102a displays the budget input screen P on the monitor 114 on the client department side (step S2). As shown in Figure 6, when a user on the client department side enters the project number "PJ0001" in cell P1 of the budget input screen P, the project name entered by that user on the contract information input screen is displayed next to cell P1. The budget input screen P also includes cells such as P2 where the budget registration date can be entered, P3 where the number of budget changes can be entered, and P4 where the details of the project budget can be entered. The display control unit 102a displays the budget input screen P on the client department's monitor 114 with cells P2 to P4 blank. In addition, the sales amount "¥10,000,000" entered on the contract information input screen is displayed in cell P5 of the budget input screen P. Furthermore, on the budget input screen P, the sum of the seven budget amounts entered in cell P4, "¥7,000,000" (1,000,000 + 500,000 + 1,000,000 + 1,000,000 + 1,000,000 + 2,000,000 + 500,000) is displayed in cell P6 as the total budget amount, and the amount obtained by subtracting the total budget amount displayed in cell P6 from the sales amount displayed in cell P5, "¥3,000,000" (1,000,000 - 7,000,000 = 3,000,000) is displayed in cell P7 as the projected profit. Then, as shown in Figure 7, the generation unit 102g generates budget data 106d and budget detail data 106e from the budget input screen P according to the information registered by the user on the requesting department side.

[0053] Once the requesting department has finished inputting the contract information and budget, it will hand over the details of the construction work to the contracting department.

[0054] Then, when the user on the client department side receives the details of the construction work, they perform the input process for contract information and budget. At this time, the display control unit 102a displays the contract information input screen on the monitor 114 on the client department side (step S3). The contract information input screen (not shown) includes cells for entering project number, project name, department, customer, sales amount, construction period, internal transaction project number, number of internal transaction budget changes, internal transaction detail line number, etc. The display control unit 102a displays the contract information input screen on the monitor 114 on the client department side with each cell blank. Then, as shown in Figure 8, the generation unit 102g generates contract information data 106c from the contract information input screen according to the information registered by the user on the client department side.

[0055] Then, the display control unit 102a displays the budget input screen P on the monitor 114 on the client department's side (step S4). As shown in Figure 9, when a user on the client department's side enters project no. "PJ0002" in cell P1 of the budget input screen P, the project name entered by the user on the contract information input screen is displayed next to cell P1, and the number of internal transaction budget changes "1" entered by the user on the contract information input screen is displayed in cell P3 as the number of budget revisions. The budget input screen P also includes cells such as P2 where the budget registration date can be entered and P4 where the details of the project budget can be entered. The display control unit 102a displays the budget input screen P on the client department's monitor 114 with cells P2 and P4 blank. In addition, the total budget amount entered in cell P4, "¥1,000,000" (300,000 + 500,000 + 200,000), is displayed in cell P6 as the total budget amount on the budget input screen P.

[0056] The contract amount calculation unit 102b then calculates the sales amount of the requesting department to the requesting department, "¥1,100,000" (1,000,000 × 110% = 1,100,000), from the total budget amount "¥1,000,000" displayed in cell P6 and the multiplier "110%" referenced from the internal transaction expense master 106a based on the total budget amount. The budget input screen P then displays the "¥1,100,000" calculated by the contract amount calculation unit 102b as the sales amount in cell P5 in cell P5. Additionally, the budget input screen P displays the amount obtained by subtracting the total budget amount displayed in cell P6, "¥100,000" (1,100,000 - 1,000,000 = 1,000,000), as the projected profit in cell P7. Then, as shown in Figure 10, the generation unit 102g generates budget data 106d and budget detail data 106e according to the information registered by the user on the requesting department side from the budget input screen P.

[0057] Then, once the requesting department has finished inputting the contract information and the budget, the requesting department approves the budget registered through the input process. At this time, the display control unit 102a displays the WF Unapproved List screen Q on the requesting department's monitor 114 (step S5). As shown in Figure 11, on the WF Unapproved List screen Q, the requesting department's approver, "Department Head of Department B," is displayed as the operator in cell Q1, and "Budget" is displayed as the data type in cell Q2. Also, on the WF Unapproved List screen Q, a checkbox for selecting the WF to approve is displayed in cell Q3. Furthermore, on the WF Unapproved List screen Q, the project number "PJ0002" entered by the requesting department's user on the budget input screen P is displayed in cell Q4, the budget registration date "2024 / 7 / 1" is displayed in cell Q5, and the number of internal transaction budget changes "1" is displayed in cell Q6 as the number of budget changes. Then, on the WF Unapproved List screen Q, the sales amount "¥1,100,000" displayed on the budget input screen P is displayed in cell Q7, and the total budget amount "¥1,000,000" is displayed in cell Q8. Then, on the WF Unapproved List screen Q, the department "Department B (Client)" entered by the user on the client department side on the contract information input screen is displayed in cell Q9, the internal transaction project number "PJ0001" is displayed in cell Q10, the number of internal transaction budget changes "1" is displayed in cell Q11, the internal transaction detail line number "4" is displayed in cell Q12, and the customer "Department A (Requesting)" is displayed in cell Q13. Then, on the WF Unapproved List screen Q, the budget amount "¥1,000,000," referenced from budget detail data 106e created by the requesting department, is displayed in cell Q14 as the internal transaction budget amount, based on project no. "PJ0002" and internal transaction detail line number "4." The department head of department B, who is the operator, can then review the various information displayed on the WF Unapproved List screen Q, check the checkbox displayed in cell Q1, and then press the register button displayed in cell Q15 to approve the budget.

[0058] Then, once the budget is approved by the requesting department through its budget approval process, the control unit 102 determines whether the contract amount between the requesting department and the requesting department exceeds the budget amount planned by the requesting department (step S6). The amount referenced as the contract amount is the sales amount in the budget data 106d created by the requesting department (in this embodiment, "¥1,100,000"). The amount referenced as the budget amount is the budget amount in the budget detail data 106e created by the requesting department (in this embodiment, "¥1,000,000").

[0059] Then, if it is determined that the contract amount exceeds the budget amount (Step S6: Yes), the notification unit 102e notifies the user on the requesting department side via email M1 as shown in Figure 12, etc., that the internal transaction with the requesting department has been approved, that the contract amount (the amount of sales from the requesting department to the requesting department, approved by the requesting department) exceeds the budget amount (the amount planned by the requesting department), and that the budget needs to be revised (Step S7).

[0060] Then, when email M1 is sent to the user on the requesting department side, the requesting department side performs budget revision processing. At this time, as shown in Figure 13, the update unit 102c automatically updates the sales amount "¥0" in the contract information data 106c created by the requesting department to the value of the contract amount calculated by the contract amount calculation unit 102b, i.e., the sales amount "¥1,100,000". Then, the update unit 102c automatically updates the budget amount "¥1,000,000" in the budget detail data 106e created by the requesting department to the same value as the value of the contract amount calculated by the contract amount calculation unit 102b, i.e., the sales amount "¥1,100,000". Then, based on the updated budget amount value in the updated budget detail data 106e, the update unit 102c automatically updates the total budget amount "¥7,000,000" in the budget data 106d created by the requesting department to "¥7,100,000" (7,000,000 + (1,100,000 - 1,000,000)), and the planned profit "¥3,000,000" to "¥2,900,000" (3,000,000 + (1,100,000 - 1,000,000)). Then, the update unit 102c automatically updates the number of planned changes in the budget data 106d created by the requesting department from "1" to "2" by incrementing it by one.

[0061] Then, the display control unit 102a displays the budget input screen P on the monitor 114 on the requesting department side (step S8). As shown in Figure 14, the project number "PJ0001" entered by the user on the requesting department side when they perform the budget input process is displayed in cell P1 of the budget input screen P. Furthermore, when the user on the requesting department side changes the budget registration date displayed in cell P2 of the budget input screen P from the date the budget was registered "2024 / 7 / 1" to the date the budget is revised "2024 / 8 / 1", ​​and changes the number of budget revisions displayed in cell P3 of the budget input screen P from "1" to "2", the various information in the budget data 106d and budget detail data 106e shown in Figure 15 is referenced based on the project number "PJ0001" and the number of budget revisions "2", and the various information displayed on the budget input screen P is automatically updated. Specifically, when budget detail data 106e is referenced, the budget amount for Department B displayed in cell P4 of the budget input screen P is automatically updated from "¥1,000,000" to "¥1,100,000". Similarly, when budget data 106d is referenced, the total budget amount displayed in cell P6 of the budget input screen P is automatically updated from "¥7,000,000" to "¥7,100,000", and the projected profit displayed in cell P7 of the budget input screen P is automatically updated from "¥3,000,000" to "¥2,900,000". Note that the total budget amount and projected profit displayed on the budget input screen P may also be automatically calculated based on the budget amount when the user on the requesting department side revises the budget amount. Furthermore, there are no particular limitations on the timing of updates to the various information contained in contract information data 106c, budget data 106d, and budget detail data 106e. For example, the various information contained in contract information data 106c, budget data 106d, and budget detail data 106e may be automatically updated after the user on the requesting department side revises the budget amount.

[0062] On the other hand, if it is determined that the contract amount does not exceed the budget amount (Step S6: No), the control unit 102 determines that a budget revision by the requesting department is not necessary and terminates the WF performed by the internal transaction management device 100 (Step S9).

[0063] Furthermore, if the budget is rejected by the requesting department during the budget approval process, the notification unit 102e notifies the user on the requesting department side via email M2, as shown in Figure 16, that the internal transaction with the requesting department has been rejected and that the contract information data 106c registered by the requesting department will be marked as lost (step S10). Then, as shown in Figure 17, the update unit 102c adds information on the lost transaction category to the contract information data 106c created by the requesting department, automatically updates the lost transaction category to "lost," and then terminates the WF performed by the internal transaction management device 100 (step S11). The requesting department can then review the budget amount for the requesting department and repeat steps S2 and beyond of the WF to conduct an appropriate internal transaction with the requesting department.

[0064] Then, once the budget is approved by the requesting department and the work requested by the requesting department is carried out, the requesting department processes the sales. At this time, the display control unit 102a displays the cost details input screen, which serves as the sales input screen, on the monitor 114 on the requesting department's side (step S12). The cost details input screen (not shown) includes cells for entering the project number, line number, cost account, counterparty, and cost amount, and the display control unit 102a displays the contract information input screen on the monitor 114 on the requesting department's side with each cell blank. Note that the line number, cost account, and counterparty on the cost details input screen may be automatically displayed with values ​​referenced from the budget details data 106e based on the project number entered by the user on the requesting department's side. Then, as shown in Figure 18, the generation unit 102g generates cost detail data 106f according to the information registered by the user on the requesting department side from the cost detail input screen.

[0065] The display control unit 102a then displays a sales input screen R, which is different from the cost detail input screen described above, on the monitor 114 on the client department side. As shown in Figure 19, when a user on the client department side enters the project number "PJ0002" displayed in cell R1 of the sales input screen R, the project name entered by that user on the contract information input screen is displayed next to cell R1. Also, when a user on the client department side enters the date to record the sale, "2024 / 9 / 1", in the sales date displayed in cell R2 of the sales input screen R, and enters "¥1,100,000" in the sales amount displayed in cell R3 of the sales input screen R, the total cost amount "¥1,100,000" (300000+600000+200000), which is referenced from the cost detail data 106f based on the project number, is displayed as the cost amount in cell R4. Additionally, based on the project number, the total budget amount "¥1,000,000" (300,000 + 500,000 + 200,000), referenced from budget detail data 106e created by the requesting department, is displayed as the budget amount in cell R5.

[0066] Then, the control unit 102 calculates the upper limit of the amount that the requesting department can accept from the requesting department, "¥1,050,000" (1,000,000 × 105% = 1,050,000), from the budget amount "¥1,000,000" displayed in cell R5 of the sales input screen R and the upper limit of the cost variance rate "110%" referenced from the internal transaction cost variance rate master 106b based on the budget amount, and calculates the lower limit of the amount that the requesting department can accept from the requesting department, "¥900,000" (1,000,000 × 90% = 900,000), from the lower limit of the cost variance rate "90%" referenced from the internal transaction cost variance rate master 106b based on the budget amount, and calculates the lower limit of the amount that the requesting department can accept from the requesting department, "¥900,000" (1,000,000 × 90% = 900,000). Then, on the sales input screen R, the upper limit of the allowable amount calculated by the control unit 102, "¥1,050,000", is displayed in cell R6, and the lower limit of the allowable amount calculated by the control unit 102, "¥900,000", is displayed in cell R7.

[0067] The variance detection unit 102d then compares the budget amount registered in advance by the user on the requesting department side from the budget input screen P (this is the sum of the budget amounts referenced from the budget detail data 106e created by the requesting department, and is also called the total budget amount) with the cost amount registered by the user on the requesting department side from the cost detail input screen (this is the sum of the cost amounts referenced from the cost detail data 106f created by the requesting department, and is also called the total cost amount). The variance detection unit 102d then determines whether the cost amount is within the range of the allowable amount calculated from the budget amount and the cost variance rate in the internal transaction cost variance rate master 106b (step S13).

[0068] If the control unit 102 determines that the cost amount is within the acceptable range (Step S13: Yes), it determines that there is no need for the requesting department to revise the sales and terminates the WF performed by the internal transaction management device 100 (Step S14).

[0069] On the other hand, if the difference detection unit 102d determines that the cost amount is outside the acceptable range, in other words, if the cost amount exceeds the acceptable amount or falls below the acceptable amount (step S13: No), the notification unit 102e notifies the user by displaying this information on the sales input screen R that the user on the requesting department is using. The screen switching unit 102f then switches the screen of the sales input screen R that the user on the requesting department is using, and makes only cell R8, which can be used to input a number for identifying the classification of a set of multiple difference factors, and cell R9, which can be used to input details of the difference factors, available fields, allowing the user on the requesting department to input the difference factors (step S15). The generation unit 102g then generates sales data 106g and difference factor detail data 106h from the sales input screen R according to the information registered by the user on the requesting department, as shown in Figure 20.

[0070] Then, once the difference is registered by the sales accounting process of the requesting department, the notification unit 102e notifies the user on the accounting department side by email or other means that there is a difference between the amount planned by the requesting department (budget amount) and the amount actually incurred by the requesting department (cost amount) (step S16).

[0071] Then, the user from the accounting department conducts interviews with the requesting department (Step S17) and holds discussions within the accounting department based on the interview content (Step S18). The sales amount of the requesting department to the requesting department is calculated from the actual amount incurred by the requesting department (cost amount) and the markup rate referenced from the internal transaction expense master 106a based on that cost amount, provided that the cost amount of the requesting department is appropriate. In this embodiment, the cost amount "¥1,100,000" and the markup rate "110%" referenced from the internal transaction expense master 106a based on that cost amount are used to determine that "¥1,210,000" (1,100,000 × 110% = 1,210,000) is an appropriate sales amount. Then, as shown in Figure 21, the user from the accounting department enters the results of the discussions within the accounting department as an accounting decision item into cell R10 of the sales input screen R (Step S19). Then, as shown in Figure 22, the generation unit 102g generates accounting judgment data 106i according to the information registered by the accounting department user from the sales input screen R.

[0072] Then, the user in the requesting department revises the sales based on the results of the consultation by the accounting department. At this time, the display control unit 102a displays the sales input screen R on the monitor 114 on the requesting department side (step S20). Then, as shown in Figure 23, the user in the requesting department revises the sales amount displayed in cell R3 of the sales input screen R from "¥1,100,000" to "¥1,210,000" based on the results of the consultation by the accounting department, thereby setting the contract amount between the requesting department and the requesting department to an appropriate amount.

[0073] According to the embodiment described above, the contract amount calculation unit 102b can automatically calculate the contract amount between the requesting department and the requesting department by calculating the sales amount of the requesting department to the requesting department from the total budget amount registered by the user on the requesting department side from the budget input screen P and the multiplier referenced from the internal transaction expense master 106a based on the total budget amount. With this configuration, it is possible to prevent arbitrary setting of contract amounts by the requesting department or the requesting department, which may be difficult for the requesting department to compare external business partners with internal business partners such as the requesting department, or due to power balances between departments within the company. Furthermore, the requesting department and the requesting department can set contract amounts while ensuring fairness and transparency in internal transactions by having the contract amount calculated based on the budget information created by the requesting department and the multiplier set in advance by the internal transaction expense master 106a, while managing the income and expenses arising from internal transactions using the internal transaction management device 100. Therefore, an appropriate contract amount can be set between the requesting department and the receiving department, thereby enabling appropriate internal transactions between the requesting and receiving departments.

[0074] Furthermore, according to this embodiment, the display control unit 102a can further display the budget approval screen (WF unapproved list screen Q in this embodiment) on the display unit (monitor 114 in this embodiment) on the client department side, and the update unit 102c can update the sales amount value pre-entered by the client department to the contract amount value calculated by the contract amount calculation unit 102b when the sales amount displayed on the WF unapproved list screen Q is approved by a user on the client department side. As a result, the sales amount value in the contract information data 106c created by the client department can be automatically updated, thereby enabling appropriate internal transactions between the requesting department and the client department.

[0075] Furthermore, according to this embodiment, the variance detection unit 102d compares the budget amount registered in advance by the user on the client department side from the budget input screen P with the cost amount registered by the user on the client department side from the sales input screen (cost details input screen in this embodiment), and can detect whether the cost amount exceeds the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master 106b based on the budget amount. In addition, the notification unit 102e can notify the user on the client department side if the variance detection unit 102d detects that the cost amount exceeds the allowable amount. Furthermore, the screen switching unit 102f can allow the user on the client department side to input the variance factors from the sales input screen (sales input screen R, which is different from the cost details input screen in this embodiment). With this configuration, the budget amount and cost amount of the client department can be compared when recording internal transactions. Furthermore, when a discrepancy arises between the amount planned by the requesting department (budget amount) and the amount actually incurred by the receiving department (cost amount) due to changes in the scope of work or the content of the request, it is possible to prevent the requesting department and the receiving department from entering into an additional contract, that is, to prevent the contract amount between the requesting department and the receiving department from being reviewed. Therefore, appropriate internal transactions can be conducted between the requesting department and the receiving department. Moreover, by setting up a check by a third department when the difference detected by the discrepancy detection unit 102d exceeds a certain level, it is possible for a third department other than the parties involved to objectively judge whether the contract amount between the requesting department and the receiving department is appropriate. Therefore, it is possible to minimize internal transaction costs and improve the gross profit of each department.

[0076] [3. 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.

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

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

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

[0080] For example, among the processes described in the embodiments described above, 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.

[0081] In addition, 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 the above-mentioned documents and drawings may be changed at will unless otherwise specified.

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

[0083] For example, the processing functions of each device constituting the internal transaction management device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by each device 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.

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

[0085] 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-first 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.

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

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

[0088] Furthermore, the internal transaction management device 100 may be configured as an information processing device such as a known personal computer or workstation, or as an information processing device to which any peripheral devices are connected. Alternatively, the internal transaction management device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the internal transaction management device 100.

[0089] 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]

[0090] This invention is useful, for example, in the construction industry or the IT industry. [Explanation of Symbols]

[0091] 100 Internal Transaction Management System 102 Control Unit 102a Display Control Unit 102b Contract Amount Calculation Section 102c update section 102d Difference detection unit 102e Notification section 102f Screen switching section 102g generation part 102h Output section 104 Communication Interface Section 106 Storage section 106a Internal Transaction Expense Master 106b Internal Transaction Cost Variance Ratio Master 106c Contract Information Data 106d Budget data 106e Budget Details Data 106f Cost breakdown data 106g Sales Data 106h Detailed data on the factors causing the difference 106i Accounting Decision Data 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. An internal transaction management device equipped with a control unit, which ensures fairness and transparency of internal transactions by managing the income and expenses arising from such transactions, It is possible to access an internal transaction cost variance master that associates cost variance rates with each budgeted amount recorded as sales revenue for the requesting department. The control unit, A display control unit that displays the budget input screen and the sales input screen on the display unit, A variance detection unit compares the budget amount registered in advance by the user on the requesting department side from the budget input screen with the cost amount registered by the user from the sales input screen, and detects whether the cost amount exceeds the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount. If the difference detection unit detects that the cost amount exceeds the allowable amount, the notification unit notifies the user, A screen switching unit that allows the user to input the factors causing the discrepancy from the sales input screen, An internal transaction management device characterized by being equipped with the following features.

2. The display control unit performs a display control step in which it causes the budget input screen and the sales input screen to be displayed on the display unit, The variance detection unit compares the budget amount registered in advance by the user on the requesting department side from the budget input screen with the cost amount registered by the user from the sales input screen, and detects whether the cost amount exceeds the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount. The notification unit notifies the user when the difference detection unit detects that the cost amount exceeds the allowable amount, The screen switching unit includes a screen switching step that causes the user to input the difference factors from the sales input screen, An internal transaction management method characterized by including the following.

3. The internal transaction management system, Display control means for displaying the budget input screen and the sales input screen on the display unit. A variance detection means compares the budget amount registered in advance by the user on the requesting department side from the budget input screen with the cost amount registered by the user from the sales input screen, and detects whether the cost amount exceeds the allowable amount calculated from the budget amount and the cost variance rate referenced from the internal transaction cost variance rate master based on the budget amount. If it is detected that the cost amount exceeds the allowable amount, a notification means for notifying the user, A screen switching means that causes the user to input the difference factors from the sales input screen. An internal transaction management program designed to function as such.

Images