JP2018156132A - Intracompany transaction management apparatus, intracompany transaction management method and intracompany transaction management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an intracompany transaction management apparatus, an intracompany transaction management method and an intracompany transaction management program capable of easily grasping an account balance by sector including a money generated in an internal transaction.SOLUTION: An intracompany transaction management apparatus of the present embodiment includes a storage unit for storing an intracompany transaction database registering intracompany data regarding an intracompany transaction between sections in a company that generates moneys and an intracompany money database registering intracompany money data including information for identifying an amount of money generated by the intracompany transaction and the sections, and an intracompany money data generation unit for generating intracompany money data based on the intracompany transaction data and registering it in the intracompany money database.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an internal transaction management apparatus, an internal transaction management method, and an internal transaction management program.

  Patent Document 1 describes, for each in-house organization, the in-sale amount of intermediate products processed by the in-house organization and delivered to other in-house organizations, and in-house purchase of intermediate products delivered from other in-house organizations to the in-house organization. A business management system that calculates the balance of the in-house organization based on the amount of money is disclosed (see paragraph 0024, etc.).

JP 2014-199489 A

  Here, when a transaction involving the movement of goods between departments in the company is performed, a change (fee) may occur. For this reason, in order to more accurately grasp the balance of payment by department, it has been desired to register a change generated in an internal transaction (internal transaction) in association with a department that has made an internal transaction.

  Previously, the technology used to account for intra-company transactions as virtual sales or purchases was used, but the accounting process becomes complicated to distinguish them from actual sales or purchases related to external transactions. was there.

  The present invention has been made in view of the above, and provides an internal transaction management device, an internal transaction management method, and an internal transaction management program that can more easily grasp the divisional income and expenditure including a change generated in an internal transaction. The purpose is to provide.

  In order to solve the above-described problems and achieve the object, an internal transaction management apparatus according to the present invention includes an internal transaction database in which internal transaction data regarding internal transactions between internal departments in which a change occurs is registered, A storage unit that stores an in-house change database that stores in-house change data including information for identifying the department and the amount of the change made in the company, and generates the in-house change data based on the in-house transaction data And an in-house change data generation unit registered in the in-house change database.

  In the internal transaction management device according to the present invention, the internal transaction database includes transaction identification data for identifying the internal transaction and transaction identification data for identifying the transaction division of the internal transaction. , The customer department identification data for identifying the customer department of the internal transaction, the unit price of the product subject to the internal transaction, the quantity of the product, and the transaction price of the internal transaction are associated with each other. The in-house change data generation unit, the transaction identification data acquired from the in-house transaction database, the transaction source department identification data, the customer department identification data, a preset change rate or unit price, From the monetary amount or unit price calculated from the monetary rate and the transaction price of the internal transaction database and the quantity of the internal transaction database In association with the commission amount of money issued, the, is registered in the in-house commission database as the in-house commission data.

  The in-house transaction management apparatus according to the present invention further includes a journal data generation unit that generates the journal data for the change from the in-company change data generated by the in-house change data generation unit.

  The internal transaction management method according to the present invention is an internal transaction management method executed by an information processing apparatus including a storage unit and a control unit, wherein the storage unit is an internal transaction between internal departments where a change occurs. An in-house transaction database in which in-house transaction data is registered, and an in-house payment database in which in-house payment data including information for identifying the amount of money generated in the internal transaction and the department is registered, and And an in-house change data generating step for generating the in-house change data based on the in-house transaction data and registering the in-house change database, which is executed by the control unit.

  An internal transaction management program according to the present invention is an internal transaction management program for causing an information processing apparatus including a storage unit and a control unit to execute the internal transaction management program. Storing an internal transaction database in which internal transaction data for internal transactions is registered, and an internal payment database in which internal monetary data including information for identifying the amount of the monetary amount generated in the internal transaction and the department is registered. And generating the in-house change data based on the in-house transaction data to be executed by the control unit, and registering it in the in-house change database.

  According to the present invention, there is an effect that it is possible to more easily grasp a divisional balance including a change generated in an in-house transaction.

FIG. 1 is a block diagram showing an example of the configuration of the in-house transaction management apparatus. FIG. 2 is a diagram illustrating an example of the data configuration of movement data, in-house change data, and journal data. FIG. 3 is a diagram illustrating an example of a data configuration of sales data, in-house change data, and journal data. FIG. 4 is a diagram showing an example of the calculation result of the divisional balance of in-house payments by division. FIG. 5 is a flowchart illustrating an example of the flow of the internal transaction management process associated with the movement of the product. FIG. 6 is a flowchart illustrating an example of a flow of in-house change data generation processing corresponding to movement data.

  Embodiments of an in-house transaction management apparatus, an in-house transaction management method, and an in-house transaction management program according to the present invention will be described below in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
Conventionally, when a transaction involving the movement of a product is performed between departments in a company, a change may occur. For this reason, in order to more accurately grasp the balance of payment by department, it has been desired to register a change generated in an internal transaction (internal transaction) in association with a department that has made an internal transaction. A change (fee) associated with such an internal transaction is called an internal change.

  Therefore, in the present embodiment, for example, an in-house transaction management apparatus, an in-house transaction management method, and an in-house transaction management program are provided that can more easily grasp the divisional balance including a change generated in an in-house transaction. Hereinafter, a specific configuration and operation will be described.

[2. Constitution]
The configuration of the in-house transaction management apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram illustrating an example of the configuration of the in-house transaction management apparatus 100.

  The in-house transaction management apparatus 100 is a commercially available desktop personal computer. The in-house transaction management apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. It may be a type information processing apparatus.

  As shown in FIG. 1, the in-house transaction management apparatus 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the in-house transaction management apparatus 100 is connected to be communicable via an arbitrary communication path.

  The communication interface unit 104 connects the in-house transaction management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the in-house transaction management apparatus 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). Note that data stored in the storage unit 106 to be described later may be stored in the server 200.

  An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker (including a home television), a speaker, and a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following description, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

  As shown in FIG. 1, the storage unit 106 stores a movement database (DB) 106a, a sales database (DB) 106b, an in-house change database (DB) 106c, and a journal database (DB) 106d.

  The movement database 106a stores movement data. The movement data is data that records the movement of the product. The movement of goods in the present embodiment includes movement between storage locations in the warehouse, in addition to loading and unloading between warehouses managed by different departments in the company. The data structure of the movement database 106a is the same as the structure of movement data described later.

  The sales database 106b stores sales data. The sales data is data indicating the sales of the recorded product. The data structure of the sales database 106b is the same as the structure of sales data described later. The movement database 106a and the sales database 106b are examples of an in-house transaction database in the present embodiment.

  The in-house change database 106c stores in-house change data generated by in-house transactions. The in-house change data is data including the amount of in-house change generated in the internal transaction and information for identifying the department related to the internal transaction. The data structure of the in-house change database 106c is the same as the structure of in-house change data to be described later.

  The journal database 106d stores journal data generated in association with the movement of goods, sales, purchase, in-house change registration, and the like. The data structure of the journal database 106d is the same as that of journal data described later.

  The control unit 102 is a CPU or the like that controls the in-house transaction management apparatus 100 in an integrated manner. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and necessary data, and performs various information processing based on these stored programs. Run.

  As shown in FIG. 1, the control unit 102 includes a display control unit 102a, a reception unit 102b, a movement data generation unit 102c, a sales data generation unit 102d, an in-company change data generation unit 102e, and a journal data generation unit 102f. And a departmental balance calculation unit 102g.

  The display control unit 102a controls the monitor 114 to display a slip input screen. The slip input screen is a screen for inputting slip information such as a movement slip for registering the movement of goods and a sales slip for recording sales. The slip input screen for inputting slip slip slip information and the slip input screen for entering sales slip slip information may be separate screens. Further, the display control unit 102a controls the monitor 114 to display the calculation result of the divisional balance by the divisional balance calculation unit 102g.

  The accepting unit 102b accepts slip information input by the user on the slip input screen. The reception unit 102b sends the input slip information to the movement data generation unit 102c or the sales data generation unit 102d and the in-house change data generation unit 102e.

  The movement data generation unit 102 c generates movement data from the slip information input from the slip input screen and registers it in the movement database 106 a of the storage unit 106. Specifically, the movement data generation unit 102c acquires a value input as a parameter on the slip input screen, registers the value of each item in association with the movement database 106a as movement data.

  FIG. 2 is a diagram illustrating an example of the data configuration of movement data, in-house change data, and journal data. As shown in FIG. 2, the movement data includes, for example, a movement slip number, a data classification, a slip line number, a issuing department, a receiving department, a product, a moving unit price, a moving number, and a moving amount. Including.

  The value of each item shown in FIG. 2 is an example of movement data registered when the product C is moved from the sales department A to the sales department B. The movement of the product C from the sales department A to the sales department B is an example of an internal transaction between internal departments where a change occurs in the present embodiment. The in-house transaction is also an in-house purchase / sale of the product C from the sales department A to the sales department B. The movement data related to the movement of products between departments in the company is an example of in-house transaction data in the present embodiment.

Hereafter, each item of movement data is demonstrated using FIG.
“Movement slip number” is a slip number for identifying the movement processing of a product. For example, the user gives one movement slip number per movement process. Further, the movement data generation unit 102c may number the movement slip number.

  “Data classification” is a classification for classifying data types. For example, the data classification of movement data is “100”, the data classification of sales data is “30”, the data classification of purchase data is “40”, and the like. The value of each data section is an example and is not limited to this.

  The “slip line number” is a number for identifying details associated with one moving slip number. For example, when a plurality of types of products are moved in one movement process, the user assigns a slip line number for each product. Alternatively, the movement data generation unit 102c may number slip line numbers. The slip line number may be a serial number within one moving slip number, or may be a product code of a product to be moved.

  Further, the value of each item of the movement data is specified by the movement slip number, the data classification, and the slip line number. In other words, each item of movement data is associated with a movement slip number, a data classification, and a slip line number. The movement slip number, data classification, and slip row number are an example of transaction identification data for identifying in-house transactions in the present embodiment.

  The “delivery department” is the department from which the product is moved. In the example shown in FIG. 2, the sales department A owns the product C before the movement. The issue department is also a product sales department in the internal transaction. The issuing department is an example of transaction department identification data in the present embodiment. In addition, each department in the present embodiment is, for example, an organizational unit corresponding to an organizational unit that records expenses and revenues in management accounting, but is not limited thereto.

  The “warehousing department” is a department to which the product is moved. In the example shown in FIG. 2, the product C is owned by the sales department B by the movement process. The warehousing department is also a purchasing department for products in the internal transaction. The warehousing department is an example of customer department identification data in the present embodiment.

  "Product" is a product to be moved. In the item, for example, a product code or a product name that can identify the product is registered.

  “Movement unit price” is a unit price per unit quantity applied in the movement between departments of the product to be moved.

  “Number of movements” is the quantity of products moved in the movement process. The unit of the number of movements corresponds to the unit quantity of the goods to be moved. For example, when the unit quantity of the product is “1”, the movement number “5” indicates “5 products”. When the unit quantity of the product is “1 kg”, the movement number “5” indicates “product 5 kg”.

  “Moving amount” is the total value of the price of each product moved in the moving process. For example, in the example shown in FIG. 2, “¥ 500” obtained by multiplying the transfer unit price “¥ 100” by the number of transfers “5” is the transfer amount. The transfer amount is an example of a transaction price in the present embodiment.

  The data structure and values of the movement data shown in FIG. 2 are examples, and the present invention is not limited to these. The in-house change data and journal data shown in FIG. 2 will be described later.

  Returning to FIG. 1, the sales data generation unit 102 d generates sales data from the slip information input from the slip input screen, and registers the sales data in the sales database 106 b of the storage unit 106. Specifically, the sales data generation unit 102d acquires the value input to the parameter on the slip input screen for each item, registers the value of each item in association with the sales data generation unit 102d as sales data. The above-described movement data generation unit 102c and sales data generation unit 102d are each an example of an in-house transaction data generation unit in the present embodiment.

  FIG. 3 is a diagram illustrating an example of a data configuration of sales data, in-house change data, and journal data. As shown in FIG. 3, the sales data includes, for example, a sales slip number, a data classification, a slip line number, a processing department, a recording department, a product, a sales unit price, a sales number, and a sales amount. Including.

  The value of each item shown in FIG. 3 is an example of sales data registered when the purchasing department sends out the product D to the customer and registers the sales slip instead of the sales department A. . As an external transaction, the transaction is sales from the sales department A to the customer. On the other hand, as an in-house transaction, the transaction is an in-house sale of the product D from the purchase department to the sales department A. The internal trading of the product D from the purchasing department to the sales department A is an example of an internal transaction between internal departments in which a change occurs in the present embodiment. The sales data related to the internal transaction is an example of internal transaction data in the present embodiment.

Hereinafter, each item of the movement data will be described with reference to FIG.
“Sales slip number” is a slip number for identifying the sales recording process. For example, the user assigns one sales slip number for one sales counting process. In addition, the sales data generation unit 102d may number the sales slip number.

  The “data classification” is the same as the data classification of the item of movement data described in FIG.

  The “slip line number” is a number for identifying details associated with one sales slip number. For example, when a plurality of types of products are sold in one sale, the user assigns a slip line number for each product. Further, the sales data generation unit 102d may number the slip line number. The slip line number may be a serial number within one sales slip number, or may be a product code of a product to be moved.

  The value of each item of sales data is specified by the sales slip number, data classification, and slip line number. In other words, each item of sales data is associated with a sales slip number, a data classification, and a slip line number. The sales slip number, data classification, and slip row number are examples of transaction identification data for identifying in-house transactions in the present embodiment.

  The “processing department” is a department that performs processing related to the sales. The processing department is the department that owns the product related to the sales. The processing department is also a sales department for products in the internal transaction. The processing department is an example of transaction department identification data in the present embodiment.

  “Recording department” is a department in which the sales amount is recorded. The accounting department is also the purchasing department for products in the internal transaction. The accounting department is an example of customer department identification data in the present embodiment.

  “Product” is a product sold to a customer. In the item, for example, a product code or a product name that can identify the product is registered.

  “Unit sales price” is the unit sales price per unit quantity of products sold from the processing department to the customer.

  “Number of sales” is the quantity of products sold to the customer from the processing department. The unit of sales number corresponds to the unit quantity of the sold products.

  “Sales amount” is a total value of prices for each product sold from the processing department to the customer. For example, in the example shown in FIG. 3, “¥ 450” obtained by multiplying the sales unit price “¥ 150” by the number of sales “3” is the sales amount. The sales amount is an example of a transaction price in the present embodiment.

  The data structure and values of the sales data shown in FIG. 3 are examples, and the present invention is not limited to these. For example, the sales data may further include a customer code or the like that identifies a customer who sells the product. The in-house change data and journal data shown in FIG. 3 will be described later.

  Returning to FIG. 1, the in-house change data generation unit 102 e generates in-house change data for the change generated in the internal transaction based on the movement data or the sales data, and registers it in the in-house change database 106 c of the storage unit 106. Specifically, the in-house change data generation unit 102e acquires movement data or sales data from the movement database 106a or the sales database 106b. Then, the in-house change data generation unit 102e sets a value acquired from the item of movement data or sales data as the item of in-house change data. Further, the in-house change data generation unit 102e calculates an in-house change amount from the transfer unit price, the sales unit price, the number of transfers, the number of sales, the transfer amount, the sales amount, etc. of the product of the transfer data or the sales data.

  As shown in FIGS. 2 and 3, the in-house change data includes, for example, a slip number, a data classification, a slip line number, a sales department, a buying department, an internal change rate, an internal change unit price, and an internal change amount. Including.

  The “slip number” is a slip number of an in-house transaction in which an in-house change has occurred. For example, as the slip number, a moving slip number or a sales slip number is set.

  The “data category” is a data category of an internal transaction in which an in-house change has occurred. The “slip line number” is a slip line number assigned to the details of the slip number of the in-house transaction in which the in-house change has occurred.

  The value of each item of in-house change data is specified by the slip number, data classification, and slip line number. In other words, each item of in-house change data is associated with a slip number, a data classification, and a slip line number. Further, the in-house transaction in which the in-house change has occurred is specified by the slip number, the data classification, and the slip line number. In other words, the in-house change data is associated with in-house transaction data such as movement data and sales data by the slip number, data classification, and slip line number. For this reason, the in-house transaction management apparatus 100 according to the present embodiment can associate the transfer data or sales data with the in-house change data without adding an item about in-company change to the transfer data or sales data.

  “Sales department” is a sales department in an internal transaction in which an in-house change has occurred. In the example shown in FIG. 2, the sales department A, which is the department that issues moving data, is the sales department for in-house change data. In the example shown in FIG. 3, the purchasing department, which is the sales data processing department, is the sales department for in-house change data.

  The “buying department” is a buying department in an internal transaction in which an internal change has occurred. In the example shown in FIG. 2, the sales department B, which is the movement data warehousing department, is the in-house change data buying department. Further, in the example shown in FIG. 3, the sales department A, which is the sales data recording department, is the in-house change data buying department.

  The “internal change rate” and “internal change unit price” are items in which values for the internal change data generation unit 102e to calculate the internal change amount are set. In the example shown in FIGS. 2 and 3, both the in-company change rate and the in-company change unit price are set for one item of the in-house transaction, but only one of them may be set. For example, the value of the in-company change rate or the in-company change unit price may be determined in advance according to a buying department, a selling department, a product, etc., and stored in the storage unit 106. Alternatively, the same in-company rate or in-unit unit price may be used for all in-house transactions. Alternatively, the user may input either the in-house change rate or the in-house change unit price from the slip input screen.

  The “internal payment amount” is the amount of internal payment paid by the buying department to the selling department in the internal transaction. The in-house payment amount is a value calculated by the in-house change data generation unit 102e based on the in-company change rate or the in-house change unit price. Alternatively, a configuration in which a value input by the user on the slip input screen is preferentially set as the in-house payment amount may be adopted. In the present embodiment, the in-house payment amount is an integer, but may be a decimal number depending on the currency used.

  Specifically, the “internal change rate” is a value indicating the ratio of the internal change amount to the transaction price. In FIGS. 2 and 3, as an example, a percentage is displayed. However, the format of the in-house change rate is not limited to this. The in-house change data generation unit 102e calculates an in-house change amount from the transaction price of the in-house transaction data and the in-house change rate.

  In the example shown in FIG. 2, the in-house change rate is “10%” with respect to the transfer amount “¥ 500”, so the in-house change amount is “¥ 50”. Further, in the example shown in FIG. 3, the in-house change rate is “3%” for the sales amount “¥ 450”. In this case, the in-house change data generation unit 102e performs fraction processing and sets the in-house change amount to “¥ 14”. The rounding method used by the in-house change data generation unit 102e may be “rounding to the nearest even number” or other rounding method.

  The “internal unit price” is the amount of internal unit per unit quantity of products sold and sold in an internal transaction. In the example shown in FIG. 2, when the number of movements “5” of the movement data is multiplied by the in-company change unit price “¥ 10”, the in-house change amount becomes “¥ 50”. Further, in the example shown in FIG. 3, when the number of sales “3” is multiplied by the in-house unit price “¥ 4.5”, the in-house amount of money is “¥ 14”.

  In this embodiment, the in-house change data generation unit 102e calculates the in-house change amount from the in-company change rate or in-company change unit price, and the transfer amount or sales amount. It is not necessary to do.

  The data structure and values of the in-house change data shown in FIGS. 2 and 3 are examples, and the present invention is not limited thereto.

  In this embodiment, the in-house change data generation unit 102e generates the in-house change data after the transfer data or sales data is registered in the transfer database 106a or the sales database 106b. It is not limited to this. For example, the in-house change data generation unit 102e may generate in-house change data at the same time as generation of movement data or sales data. In addition, when movement data or sales data is generated, in-house change data does not necessarily have to be generated. For example, when the sales department A sells a product owned by its own department to a customer, there is no transfer of goods between departments in the company, and no in-house change is generated. When no in-house change occurs in this way, the in-company change data generation unit 102e does not have to generate in-house change data.

  Returning to FIG. 1, the journal data generation unit 102 f generates journal data for in-house change from the in-company change data generated by the in-company change data generation unit 102 e. The journal data generation unit 102f registers the generated journal data in the journal database 106d. The journal data generation unit 102f may generate not only in-house change journal data but also transfer data and sales data journal data, and register them in the journal database 106d.

  For example, the journal data includes a debit item, a debit account item, and a debit amount as debit items. The journal data includes a credit department, a credit account item, and a credit amount as credit items.

  The debit department is a department in which a debit account item and a debit amount are associated with each other in the departmental balance. Further, the credit department is a department in which the credit account item and the credit amount are associated with each departmental balance. Further, the journal data generation unit 102f may acquire an account item from a not-illustrated account item master, and set a debit account item and a credit account item that match an in-house transaction to be journalized. Further, the journal data generation unit 102f may determine the account item according to the data classification such as movement data or sales data when setting the account item.

  As illustrated in FIG. 2, the journal data generation unit 102 f generates journal data from the movement data and in-house change data. In the example illustrated in FIG. 2, the journal data generation unit 102 f sets “sales department B”, which is a moving data receiving department, to the debit department, and “sales department A”, which is the moving data issuing department, to the credit department. . Since the in-house transaction is a movement of a product, the journal data generation unit 102f sets “product” to the debit account item and the credit account item. Further, the journal data generation unit 102f sets the value “¥ 500” of the movement amount of the movement data to the debit amount and the credit amount.

  Further, in the example shown in FIG. 2, the journal data generation unit 102f has a “development department B” for purchasing in-house change data in the debit department for in-company change journal data, and a sales department for in-house change data in the credit department. “Sales department A” is set. Since the journal data is journal data for in-house change, the journal data generation unit 102f sets “in-house change” for the debit account item and the credit account item. Further, the journal data generation unit 102f sets the value “¥ 50” of the in-house monetary amount for the debit amount and the credit amount.

  Further, as shown in FIG. 3, the journal data generation unit 102f generates journal data from sales data and in-house change data. In the example illustrated in FIG. 3, the journal data generation unit 102f sets “sales department A”, which is a sales data recording department, to the debit department. Since the in-house transaction is sales of the product, the journal data generation unit 102f sets “Accounts receivable” as the debit account item and “Sales” as the credit account item. Further, the journal data generation unit 102f sets the sales amount value “¥ 450” of the sales data in the debit amount and the credit amount.

  Further, in the example shown in FIG. 3, the journal data generation unit 102f has a “development department for in-house change data” as the debit department for the in-company change journal data, and a sales department for in-house change data for the credit department. A certain “purchasing department” is set. Since the journal data is journal data for in-house change, the journal data generation unit 102f sets “in-house change” for the debit account item and the credit account item. Further, the journal data generation unit 102f sets the value “¥ 14” of the in-house monetary amount for the debit amount and the credit amount.

  The data structure and values of the journal data shown in FIGS. 2 and 3 are examples, and are not limited thereto. For example, in the examples of FIGS. 2 and 3, the in-house change of the debit account item is expense, and the in-house change of the credit account item is income, so a name for distinguishing these may be used. Further, the journal data generation unit 102f may set account items such as in-house purchase, in-house sales, in-house accounts receivable, in-house accounts payable as the debit account item and the credit account item of the transfer data journal data. Further, the data structure of the journal data is not limited to the structure in which items are divided into debits and credits, and a structure in which journals are identified by the account item code or the sign of the amount of money may be adopted.

  The journal data generation unit 102f may generate the journal data after each data is registered in the transfer database 106a, the sales database 106b, and the in-house change database 106c, or the generation of transfer data, sales data, and in-company change data. At the same time.

  Returning to FIG. 1, the departmental balance calculation unit 102g calculates the departmental balance including in-house change. Further, the departmental balance calculation unit 102g sends the calculated result to the display control unit 102a.

  FIG. 4 is a diagram showing an example of the calculation result of the divisional balance of in-house payments by division. 4 is a result of the departmental balance calculation unit 102g extracting a transition of payment and receipt of departmental in-house money from the in-house money database 106c. In the trading transition table 900, the in-house change amount of the selling department in the in-house change data is displayed as a positive value, and the in-house change amount of the buying department is displayed as a negative number. This is because in-house changes are revenue for the selling department and expenses for the buying department. Further, as shown in the sales transition table 900, it is possible to identify the reason for the in-house change by classifying by slip number or data classification.

  Also, the departmental balance table 901 shown in FIG. 4 is a result of the departmental balance calculation unit 102g summarizing the trading transition table 900 and calculating the total value of the in-house amount of money for each department. By summing up the values of in-house payments by transaction, the user can more easily grasp the in-house payment amounts by department.

  FIG. 4 shows the result of extracting the departmental balance of the in-house payment amount, but the departmental balance calculated by the departmental balance calculation unit 102g is not limited to this. For example, the departmental balance calculation unit 102g may extract in-house payments and accounts receivable and accounts payable associated with each department from the journal database 106d, and calculate the departmental balance including in-house payments.

  The timing at which the departmental balance calculation unit 102g calculates the departmental balance including in-house change may be when a departmental balance inquiry operation is received from the user, or at regular timings such as every accounting period.

[3. Process flow]
Next, the in-house transaction management process of the present embodiment configured as described above will be described. FIG. 5 is a flowchart illustrating an example of the flow of the internal transaction management process associated with the movement of the product.

  The accepting unit 102b accepts slip information input from the slip input screen by the user (S1). The receiving unit 102b sends the input slip information to the movement data generation unit 102c and the in-house change data generation unit 102e.

  The movement data generation unit 102c generates movement data from the slip information input from the slip input screen and registers it in the movement database 106a of the storage unit 106 (S2). For example, the movement data generation unit 102c acquires the value input in the parameter on the slip input screen for each item, and sets each item in the movement slip number, the data classification, and the slip line number as shown in FIG. Corresponding movement data is generated and registered in the movement database 106a.

  Further, the in-house change data generation unit 102e executes an in-house change data generation process (S3). Details of the in-house change data generation processing are shown in FIG. FIG. 6 is a flowchart illustrating an example of a flow of in-house change data generation processing corresponding to movement data.

  The in-house change data generation unit 102e acquires movement data from the movement database 106a. Further, the in-house change data generation unit 102e acquires a predetermined in-house change rate or in-house change unit price (S31). Alternatively, the in-house change data generation unit 102e may acquire the movement data from the slip information input from the slip input screen. Further, the in-house change data generation unit 102e may acquire the in-company change rate or the in-house change unit price input from the slip input screen.

  Then, the in-house change data generation unit 102e calculates an in-house change amount (S32). Specifically, the in-house change data generation unit 102e calculates the in-house change amount from the value of the transfer amount set in the acquired transfer data and the in-house change rate. Alternatively, the in-house change data generation unit 102e calculates the in-house change amount from the value of the number of moves set in the acquired transfer data and the in-house change unit price.

  The in-house change data generation unit 102e associates the movement data, the in-company change rate or the in-house change unit price, and the in-house change amount and registers them in the in-house change database 106c (S33). As shown in FIG. 2, the in-house change data generation unit 102e sets the transfer slip number, the data category, the slip line number, the issue department, and the receipt department for the transfer data, respectively, as the slip of the in-house change data. The number, data classification, slip line number, selling department, and buying department are registered in the in-house change database 106c.

  Returning to FIG. 5, after the in-house change data generation process, the journal data generation unit 102f generates journal data corresponding to the movement data and the in-house change data as shown in FIG. 2, and registers it in the journal database 106d. (S4).

  In addition, in the internal transaction management process associated with the sales recording, sales data, in-house payment data, and journal data are generated in the same flow as the internal transaction management process associated with the movement of the product described with reference to FIGS. Is done. Specifically, the reception unit 102b, the sales data generation unit 102d, the in-house change data generation unit 102e, and the journal data generation unit 102f generate sales data, in-company change data, and journal data. The reception unit 102b, the sales data generation unit 102d, the in-company change data generation unit 102e, and the journal data generation unit 102f register the generated data in the sales database 106b, the in-company change database 106c, and the journal database 106d. To do.

  As described above, in the in-house transaction management apparatus 100 according to the present embodiment, the storage unit 106 includes the transfer database 106a and the sales database 106b in which transfer data or sales data regarding in-house transactions between internal departments where a change occurs is registered. An in-house change database 106c in which in-house change data including information for identifying the amount of money generated in the internal transaction and the department is registered is stored. Further, the in-house change data generation unit 102e generates in-house change data based on the movement data or the sales data and registers it in the in-house change database 106c. For this reason, according to the in-house transaction management apparatus 100 of the present embodiment, it is possible to more easily grasp the divisional balance including the change generated in the in-house transaction based on the in-house change data registered in the in-house change database 106c. In addition, according to the in-house transaction management apparatus 100 of the present embodiment, in-house change data is generated separately from movement data or sales data, and therefore sales or purchases related to actual outside transactions are confused with in-house change. This can be reduced.

  Furthermore, in the in-house transaction management apparatus 100 of the present embodiment, the movement database 106a and the sales database 106b include transaction identification data (movement slip number, sales slip number, slip line number, data classification) for identifying the in-house transaction. Source department identification data (issuing department, processing department), customer department identification data (receiving department, accounting department), unit price of products subject to internal transactions, quantity of products, and transaction price of internal transactions Are associated. Further, the in-house change data generation unit 102e has transaction identification data acquired from the movement database 106a or the sales database 106b, transaction source department identification data, customer department identification data, a preset change rate or unit price, The monetary amount calculated from the monetary rate and the transaction price or the monetary amount calculated from the monetary unit price and the quantity are associated with each other and registered in the in-house change database 106c as in-house change data. For this reason, according to the in-house transaction management apparatus 100 of the present embodiment, movement data or sales data and in-house payment data are associated with each other by the transaction identification data, and it is easy to determine which in-house transaction caused the in-house change. Can be identified. Further, according to the in-house transaction management apparatus 100 of the present embodiment, since the amount of money is calculated from movement data or sales data without the user inputting the amount of money in the in-house transaction, the user's workload is reduced. Can do.

  Further, in the in-house transaction management apparatus 100 of the present embodiment, the journal data generation unit 102f generates in-company change journal data from the in-company change data generated by the in-company change data generation unit 102e. For this reason, according to the in-house transaction management apparatus 100 of the present embodiment, it is possible to manage the inter-departmental balance including in-house change.

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

  For example, in the above-described embodiment, the internal transaction associated with the movement or sales of the product has been described as an example. However, the internal transaction is not limited thereto. For example, when an internal transaction involving in-house change occurs in connection with purchase of a product from outside, the in-house change data generation unit 102e generates in-house change data corresponding to the internal transaction.

  Further, in the above-described embodiment, the in-house transaction for the product has been described as an example. However, the object of the in-house transaction may be an intermediate product, a raw material, or the like.

  Further, the movement data generation unit 102c, the sales data generation unit 102d, and the in-house change data generation unit 102e are not limited to the slip information input from the slip input screen, but the transfer data from the slip information data input by a data file or the like. Sales data, in-house change data, etc. may be generated.

  Further, for example, among the processes described in the embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed All or a part of the above can be automatically performed by a known method.

  In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in the present specification and drawings, unless otherwise specified. Can be changed arbitrarily.

  Further, regarding the in-house transaction management apparatus 100, the illustrated components are functionally conceptual and do not necessarily need to be physically configured as illustrated.

  For example, the processing functions provided in the in-house transaction management apparatus 100, particularly the processing functions performed by the control unit 102, are realized entirely or arbitrarily by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be realized as hardware by wired logic. The program is recorded on a non-transitory computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment. It is mechanically read by the device 100. In other words, in a storage unit such as a ROM or a HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  Further, this computer program may be stored in an application program server connected to the in-house transaction management apparatus 100 via an arbitrary network, and may be downloaded in whole or in part as necessary. It is.

  In addition, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registration). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Digital, Trademark) Any “portable physical media It is intended to include. Therefore, a recording medium storing a program for executing the processing or processing method described in this specification also constitutes the present invention.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. In addition, a well-known structure and procedure can be used about the specific structure and reading procedure for reading a recording medium in each apparatus shown to embodiment, the installation procedure after reading, etc.

  Various databases and the like stored in the storage unit 106 are storage devices such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Programs, tables, databases, web page files, and the like.

  Further, the in-house transaction management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which an arbitrary peripheral device is connected. Further, the in-house transaction management apparatus 100 may be realized by installing software (including a program or data) that realizes the processing described in the present embodiment in the apparatus.

  Furthermore, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part of them may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and may be selectively implemented.

  The present invention is useful in various industries, and particularly useful in the wholesale industry that conducts in-house transactions involving the movement of goods.

100 Internal transaction management device
102 Control unit
102a Display control unit
102b reception desk
102c Movement data generation unit
102d Sales data generation unit
102e In-house change data generation unit
102f Journal data generation unit
102g Departmental balance calculation section
104 Communication interface
106 Storage unit
106a Mobile database (DB)
106b Sales database (DB)
106c In-house change database (DB)
106d Journal database (DB)
108 Input / output interface
112 Input device
114 Output device 200 Server 300 Network

Claims (5)

An internal transaction database in which internal transaction data for internal transactions between internal departments that generate monetary charges is registered, as well as internal monetary data that includes information for identifying the department's monetary amounts and the departments. A storage unit for storing the in-house change database,
An internal incentive data generating unit that generates the in-house invoice data based on the in-house transaction data and registers the in-house incentive database;
In-house transaction management device. The internal transaction database includes transaction identification data for identifying the internal transaction, transaction source division identification data for identifying a business division of the internal transaction, and identification of a business division of the internal transaction. The business unit department identification data, the unit price of the product subject to the internal transaction, the quantity of the product, and the transaction price of the internal transaction are associated with each other,
The in-house change data generation unit includes the transaction identification data acquired from the in-house transaction database, the source department identification data, the customer department identification data, a preset change rate or a change unit price, and the change The in-house fee data is calculated by associating the amount of money or the unit price of money calculated from the transaction price of the in-house transaction database and the amount of money of the in-house transaction database with the amount of money in the internal transaction database. Register in the monetary database,
The in-house transaction management device according to claim 1. A journal data generation unit that generates journal data of the change from the company cash data generated by the company cash data generation unit;
The in-house transaction management device according to claim 1 or 2. An internal transaction management method executed by an information processing apparatus including a storage unit and a control unit,
The storage unit includes an internal transaction database in which internal transaction data regarding internal transactions between internal departments in which a change occurs is generated, an internal amount including the amount of the change generated in the internal transaction and information for identifying the department Store in-house change database where change data is registered,
Executed by the control unit,
An in-house transaction management method including an in-house change data generation step of generating the in-house change data based on the in-house change data and registering the in-company change database. An internal transaction management program for causing an information processing device including a storage unit and a control unit to execute the program,
The storage unit includes an internal transaction database in which internal transaction data regarding internal transactions between internal departments in which a change occurs is generated, an internal amount including the amount of the change generated in the internal transaction and information for identifying the department Store in-house change database where change data is registered,
For causing the control unit to execute,
An in-house transaction management program including an in-house change data generation step for generating the in-house change data based on the in-house change data and registering the in-company change database.

Images