JP2022084284A - Fee allocation data generation device, fee allocation data generation method and fee allocation data generation program - Google Patents

Abstract

To provide a fee allocation data generation device, a fee allocation data generation method, and a fee allocation data generation program that can allocate fees at the same time as sales registration and purchase registration.SOLUTION: A fee allocation data generation device 100 includes: a sales unit price acquisition unit that acquires a unit price and a fee from product data including a sales unit price, a purchase unit price, and a category that identifies whether or not a fee is incurred; a fee unit price acquisition unit that acquires fee identification data and a fee unit price for fees; a sales data generation unit that generates sales data including the number of products sold and a sales amount acquired by sales unit price acquisition means; a purchase data generation unit that generates purchase data including a purchase amount calculated on the basis of the purchase unit price; and a fee allocation data generation unit that generates fee allocation data including fee identification data acquired by fee unit price acquisition means, the number of products and a fee amount calculated and allocated on the basis of the fee unit price acquired by fee unit price acquisition means.SELECTED DRAWING: Figure 1

Description

The present invention relates to a fee recording data generation device, a fee recording data generation method, and a fee recording data generation program.

Patent Document 1 discloses a distribution information management and operation system for soil generated from construction (see paragraph 0007 of Patent Document 1). In this system, the information manager uses the system from the user in the operation of management information. It is disclosed that an information placement fee is collected depending on the fee or the handling situation of earth and sand (see paragraph 0008 of Patent Document 1).

Japanese Unexamined Patent Publication No. 2008-21130

In the construction / construction industry, etc. as described in Patent Document 1, conventionally, the registration of sales and purchases associated with product transactions and the various fees incurred associated with product transactions are managed separately. Therefore, the work efficiency was very poor.

The present invention has been made in view of the above problems, and is a fee recording data generation device capable of recording fees at the same time as sales registration and purchase registration, a fee recording data generation method, and a fee recording data generation. The purpose is to provide a program.

In order to solve the above-mentioned problems and achieve the object, the fee recording data generation device according to the present invention is a fee recording data generation device including a control unit, and the control unit identifies the site of a business partner. Site identification data for, contract identification data for identifying the contract with the business partner, product identification data for identifying the product to be delivered to the business partner, sales unit price and purchase of the product. It was entered on the sales purchase registration screen, which is a screen for performing sales registration and purchase registration, from product data including a unit price and a category for identifying whether or not the fee is generated, which is set for each fee. The sales unit price acquisition means for acquiring the unit price associated with the site identification data, the contract identification data, the product identification data, and the fee for which the above-mentioned category is set, the site identification data, and the contract. From the fee data including the identification data, the fee identification data for identifying the fee, and the fee unit price which is the unit price of the fee, the input site identification data and the contract identification data are linked and described. The fee identification data for the fee acquired by the sales unit price acquisition means, the fee unit price acquisition means for acquiring the fee unit price, the input site identification data, the input contract identification data, and the input. Sales that generate sales data including product identification data, the number of sales of the product entered on the sales purchase registration screen, and the sales amount calculated based on the sales unit price acquired by the sales unit price acquisition means. The data generation means, the input site identification data, the input contract identification data, the input product identification data, the number of purchases of the product input on the sales purchase registration screen, and the above. The purchase data generation means for generating purchase data including the purchase amount calculated based on the purchase unit price acquired by the sales unit price acquisition means, the input site identification data, and the input. Calculated and recorded based on the contract identification data, the fee identification data acquired by the fee unit price acquisition means, the number of the input products, and the fee unit price acquired by the fee unit price acquisition means. It is characterized by comprising a fee recording data generation means for generating a fee recording data including a fee amount.

In addition, the fee recording data generation device according to the present invention also collects the fee recording data at the timing of the determination, even for the fee that was not recorded because the fee unit price was determined after the sales registration and the purchase registration. The input site identification data and the input are triggered by the instruction from the screen for instructing the accrual of the unaccounted fee by the fee accrual data generation means. Calculated based on the contract identification data, the fee identification data acquired by the fee unit price acquisition means, the input number of the products, and the fee unit price after the determination set in the fee data. It is characterized in that the fee recording data including the fee amount recorded in the above is generated.

Further, the fee recording data generation method according to the present invention is a fee recording data generation method executed by an information processing apparatus including a control unit, and is executed by the control unit to identify a business partner's site. Site identification data, contract identification data for identifying contracts with the business partner, product identification data for identifying products to be delivered to the business partner, and sales unit price and purchase unit price of the product. , The site identification entered on the sales purchase registration screen, which is a screen for performing sales registration and purchase registration, from the product data including the classification for identifying whether or not the fee is generated, which is set for each fee. The unit price associated with data, contract identification data, product identification data, and the sales unit price acquisition step for acquiring the fee for which the above-mentioned category is set, the site identification data, and the contract identification data. The fee data including the fee identification data for identifying the fee and the fee unit price which is the unit price of the fee is linked to the input site identification data and the contract identification data, and the sales unit price. The fee identification data for the fee acquired in the acquisition step, the fee unit price acquisition step for acquiring the fee unit price, the input site identification data, the input contract identification data, and the input product identification. Sales data generation that generates sales data including data, the number of sales of the product entered on the sales purchase registration screen, and the sales amount calculated based on the sales unit price acquired in the sales unit price acquisition step. The step, the input site identification data, the input contract identification data, the input product identification data, the purchase number of the product and the sales unit price input on the sales purchase registration screen. The purchase data generation step that generates the purchase data including the purchase amount calculated based on the purchase unit price acquired in the acquisition step, the input site identification data, and the input contract identification. The fee amount calculated and recorded based on the data, the fee identification data acquired in the fee unit price acquisition step, the number of the input products, and the fee unit price acquired in the fee unit price acquisition step. It is characterized by including, and, a fee recording data generation step for generating fee recording data including.

Further, the fee recording data generation program according to the present invention is a fee recording data generation program for being executed by an information processing apparatus provided with a control unit, and identifies the site of a business partner to be executed by the control unit. Site identification data for, contract identification data for identifying the contract with the business partner, product identification data for identifying the product to be delivered to the business partner, sales unit price and purchase of the product. It was entered on the sales purchase registration screen, which is a screen for performing sales registration and purchase registration, from product data including a unit price and a category for identifying whether or not the fee is generated, which is set for each fee. The sales unit price acquisition step for acquiring the unit price associated with the site identification data, the contract identification data, and the product identification data, and the fee for which the above-mentioned category of occurrence is set, the site identification data, and the contract. From the fee data including the identification data, the fee identification data for identifying the fee, and the fee unit price which is the unit price of the fee, the input site identification data and the contract identification data are linked and described. The fee identification data for the fee acquired in the sales unit price acquisition step, the fee unit price acquisition step for acquiring the fee unit price, the input site identification data, the input contract identification data, and the input. Sales that generate sales data including product identification data, the number of sales of the product entered on the sales purchase registration screen, and the sales amount calculated based on the sales unit price acquired in the sales unit price acquisition step. The data generation step, the input site identification data, the input contract identification data, the input product identification data, the number of purchases of the product input on the sales purchase registration screen, and the above. The purchase data generation step for generating purchase data including the purchase amount calculated based on the purchase unit price acquired in the sales unit price acquisition step, the input site identification data, and the input. Calculated and recorded based on the contract identification data, the fee identification data acquired in the fee unit price acquisition step, the number of the input products, and the fee unit price acquired in the fee unit price acquisition step. It is characterized by including a fee amount and a fee recording data generation step for generating fee recording data including.

According to the present invention, there is an effect that a fee can be recorded at the same time as sales registration and purchase registration.

FIG. 1 is a block diagram showing an example of the configuration of a fee recording data generation device. FIG. 2 is a diagram showing an example of a commercial flow in ready-mixed concrete transactions. FIG. 3 is a diagram showing an example of a tree structure showing the relationship between each data. FIG. 4 is a diagram showing an example of a data list generated by the process according to the present embodiment. FIG. 5 is a diagram showing an example of site data, contract data, and product data. FIG. 6 is a diagram showing an example of receiving fee data and payment fee data. FIG. 7 is a diagram showing an example of the sales purchase registration processing screen. FIG. 8 is a diagram showing an example of sales data, purchase data, receipt fee recording data, and payment fee recording data. FIG. 9 is a diagram showing an example of receiving fee data in which the undecided unit price is determined and the unit price after the determination is set. FIG. 10 is a diagram showing an example of a fee automatic recording processing screen. FIG. 11 is a diagram showing an example of the receipt fee recording data to which the details newly generated based on the determined unit price are added.

Hereinafter, embodiments of the fee recording data generation device, the fee recording data generation method, and the fee recording data generation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. Overview]
In industries that trade ready-mixed concrete and cement, it is necessary to manage not only sales transactions with sites (sales destinations) and suppliers that use ready-mixed concrete and cement, but also fees with cooperatives and ready-mixed concrete factories (plants). Become. FIG. 2 shows an example of commercial distribution in ready-mixed concrete transactions.

(1) Here, in the past, it was necessary to manage and input the direct sales transaction of the site (sales destination) and the supplier and each commission separately. For example, each fee with a business partner was managed separately by a handwritten ledger or the like. However, with this operation, the work was complicated and there was an omission of input of each fee. For this reason, there has been a demand for a function that can simultaneously manage each fee incurred for a plurality of business partners at the time of one shipment.

Therefore, in the present embodiment, for example, in a transaction contract for each site, it is possible to simultaneously manage the business partners of various fees (sales fees, cooperation fees, fare, etc.), the fees incurred, and the unit price of fees incurred when shipping the products. I made it. Specifically, sales purchase registration is performed based on the shipment record of ready-mixed concrete and cement, but when the sales purchase registration is performed, the commission can be automatically recorded at the same time. If the unit fee is undecided, the fee will not be recorded.

(2) In addition, in the past, for those whose fee unit price has not been decided due to reasons such as it took time to negotiate the fee unit price, after the fee unit price is decided, the shipped data for the unrecorded fee is searched. , I had to enter it manually. However, with this operation, the work was complicated and there was an omission of input of each fee. For this reason, there has been a demand for a function that can separately record only the fee after it is decided by negotiation of the fee unit price.

Therefore, in the present embodiment, for example, after the fee unit price is determined, the fee is automatically recorded so that the unrecorded fee can be recorded.

As described above, (1) and (2) have made it possible to improve the efficiency of office work and prevent omission of commissions. In the present embodiment, it is possible to offset the occurrence of receivables / debts with respect to the same business partner. Hereinafter, a specific configuration and operation will be described.

[2. Constitution]
An example of the configuration of the fee recording data generation device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the fee recording data generation device 100.

The fee recording data generation device 100 is a commercially available desktop personal computer. The fee recording data generation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is not limited to a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, a tablet personal computer, or the like. It may be a portable information processing device.

The fee recording data generation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the fee recording data generation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the fee accounting data generation device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the fee accounting data generation device 100 and the server 200 so as to be communicable with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like. The data of various masters and the like described later may be stored in the server 200, for example.

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 or a printer can be used in addition to a monitor (including a home television). In addition to the keyboard, mouse, and microphone, the input device 112 can use a monitor that realizes a pointing device function in cooperation with the mouse. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) / ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

The storage unit 106 may record, for example, on-site data 106a, contract data 106b, product data 106c, receipt fee data 106d as fee data, payment fee data 106e, sales data 106f, purchase data 106g, and fee recording. It includes data for recording receipt fees 106h and data for recording payment fees 106i as data.

Each data has a tree structure relationship shown in FIG. The details are as follows [3. Specific example of processing], the site data 106a, the contract data 106b, the product data 106c, the receipt fee data 106d and the payment fee data 106e are generated by the contract registration process, and the sales data 106f, the purchase data 106g, and the receipt are received. The fee recording data 106h and the payment fee recording data 106i are generated by the sales purchase registration process, and the receipt fee recording data 106h and the payment fee recording data 106i are updated by the fee automatic recording process.

The site data 106a is data for managing a site code, a site name, a site address, a site telephone number, a construction period, a cooperative, and the like. As shown in FIG. 5, the site data 106a includes, for example, site identification data (site code and site name) for identifying the site of a business partner, a site address, a site telephone number, a construction period, and a cooperative. , Etc. are included.

The contract data 106b is data for managing product business partners (customers, suppliers, etc.), settlement conditions (closing date, site, settlement method, etc.), and the like. As shown in FIG. 5, the contract data 106b identifies, for example, the site identification data (site code), contract identification data for identifying a contract with the business partner (contract branch number), and a customer. Customer identification data (customer code and customer name) for identification, supplier identification data (supplier code and supplier name) for identifying a supplier, collection deadline, collection month, and so on. , Collection date, collection method, payment closing date, payment month, payment date, payment method, and the like.

The product data 106c is data for managing the product code, product name, number of contracts, sales unit price, purchase unit price, commission generation, and the like. As shown in FIG. 5, the product data 106c is, for example, a product for identifying the site identification data (site code), the contract identification data (contract branch number), and a product to be delivered to the business partner. Identification data (product line No., product code and product name), the number of contracts, the sales unit price of the product, the purchase unit price of the product, and the presence / absence of the fee set for each fee. Includes classification (1 recipient to 10 supporters) and so on.

The fee may be any fee as long as it is a fee generated in a series of commercial distributions from the supplier to the purchase of the product and the delivery of the product to the business partner. For example, the product is shipped. It is a fee that is incurred at the same time when it is (sold). Specifically, examples of the above-mentioned fees include sales commissions received, sales business cooperation fees, sales commissions paid, and freight charges. The fee may be either the amount paid by the company or the amount received by the company.

The categories include the category with occurrence (“○” in the square from the occurrence of receiver 1 to the occurrence of support 10 in the product data 106c in FIG. 5) or the category without occurrence (receiver in the product data 106c in FIG. 5). Blanks in the squares from 1 occurrence to 10 occurrences of support). For example, in the example of the product data 106c of FIG. 5, for the product “ready-made concrete” of the product line No. 1 of the contract branch number 1 of the site code GB0001, the receiving fee 1 “receipt sales fee” and the receiving fee 2 “sales business” It is set that "cooperation fee" and payment fee 1 "payment sales fee" will be incurred. In addition, it is set that the receipt fee 1 "receipt sales commission" and the payment fee 1 "payment sales commission" will be incurred for the product "ready-made concrete" in the product line No. 1 of the contract branch number 2 of the site code GB0001. There is.

The received fee data 106d is data for managing the received fee business partner (customer), settlement conditions (closing date, site, settlement method, etc.), fee unit price, and the like. The supplier of the commission includes a customer of the product, a trading company, a cooperative, and the like. As shown in FIG. 6, the received fee data 106d is, for example, the site identification data (site code), the contract identification data (contract branch number), and the fee identification data (receipt fee line) for identifying the fee. No, fee code and fee name), the customer identification data (customer code and customer name), the fee unit price (sales unit price), which is the unit price of the fee, the collection deadline, the collection month, and the collection. Includes date, collection method, fee start date, etc.

The payment fee data 106e is data for managing payment fee business partners (suppliers), settlement conditions (closing date, site, settlement method, etc.), fee unit price, and the like. The supplier of the fee includes a supplier of goods, a ready-mixed concrete factory, a cooperative, a shipping company, and the like. As shown in FIG. 6, the payment fee data 106e includes, for example, the site identification data (site code), the contract identification data (contract branch number), and the fee identification data (payment fee line No., fee code, and fee). Name), the supplier identification data (supplier code and supplier name), the fee unit price (purchase unit price), the payment closing date, the payment month, the payment date, and the payment method. Including the fee start date and so on.

In the receipt fee data 106d and the payment fee data 106e, the fee unit price may be determined after the transaction of the product by negotiation with the business partner. For example, in the example of the commission data 106d in FIG. 6, the commission unit price and the commission start for the commission receipt line No. 2 “sales business cooperation fee” of the contract branch number 1 of the site code GB0001 are initially undecided. The year / month column is set blank. On the other hand, in the example of the commission data 106d in FIG. 9, since the commission unit price is determined for the commission line No. 2 “sales business cooperation fee” of the contract branch number 1 of the site code GB0001, the sales unit price and the commission start date column. As shown by the hatching, 300 yen and 2020/9 are set for each.

As shown in FIG. 8, the sales data 106f includes, for example, a transaction number, a sales number, the site identification data (site code), the contract identification data (contract branch number), and the product identification data (product line). No, product code and product name), sales date, customer identification data (customer code and customer name), scheduled collection date, collection method, number of sales of the product, and sales of the product. Includes the unit price, the sales amount of the product, and the like.

As shown in FIG. 8, the purchase data 106g includes, for example, the transaction number, the purchase number, the site identification data (site code), the contract identification data (contract branch number), and the product identification data. (Product line No., product code and product name), supplier date, supplier identification data (supplier code and supplier name), scheduled payment date, collection method, and supplier of the product. Includes the number of pieces, the purchase unit price of the goods, the purchase price of the goods, and the like.

As shown in FIG. 8, the receipt fee recording data 106h includes, for example, the transaction number, the receipt fee number, the site identification data (site code), the contract identification data (contract branch number), and the fee identification. Data (commission line No., fee code and fee name), recording date, customer identification data (customer code and customer name), scheduled collection date, collection method, number of sales, and so on. The commission unit price (sales unit price), the commission amount (sales amount), and the like are included.

As shown in FIG. 8, the payment fee recording data 106i includes, for example, the transaction number, the payment fee number, the site identification data (site code), the contract identification data (contract branch number), and the fee identification. Data (payment fee line No., fee code and fee name), recording date, the supplier identification data (supplier code and supplier name), scheduled payment date, collection method, and the purchase. The number, the fee unit price (purchase unit price), the fee amount (purchase amount), and the like are included.

The control unit 102 is a CPU or the like that collectively controls the fee recording data generation device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

The control unit 102 functionally conceptually, for example, (1) site identification data for identifying the site of a business partner, contract identification data for identifying a contract with the business partner, and the business partner. From the product data including the product identification data for identifying the product to be delivered, the sales unit price and the purchase unit price of the product, and the classification for identifying whether or not the fee is generated, which is set for each fee. The unit price associated with the site identification data, contract identification data, and product identification data entered on the sales purchase registration screen, which is the screen for performing sales registration and purchase registration, and the above-mentioned classification of the fee, which is incurred, are set. The sales unit price acquisition unit 102a as a means for acquiring the sales unit price, etc., (2) the site identification data, the contract identification data, the fee identification data for identifying the fee, and the above. From the fee data including the fee unit price, which is the unit price of the fee, the fee identification data and the fee for the fee linked to the input site identification data and the contract identification data and acquired by the sales unit price acquisition means. The fee unit price acquisition unit 102b as a means for acquiring the unit price, etc., (3) the input site identification data, the input contract identification data, the input product identification data, and the above. Sales as a sales data generation means for generating sales data including the number of sales of the product entered on the sales purchase registration screen and the sales amount calculated based on the sales unit price acquired by the sales unit price acquisition means. The data generation unit 102c, (4) the input site identification data, the input contract identification data, the input product identification data, and the product of the product input on the sales purchase registration screen. The purchase data generation unit 102d as a purchase data generation means for generating purchase data including the number of purchases and the purchase amount calculated based on the purchase unit price acquired by the sales unit price acquisition means, and ( 5) Acquisition of the input site identification data, the input contract identification data, the fee identification data acquired by the fee unit price acquisition means, the number of the input products, the fee unit price, etc. It includes a fee amount calculated and recorded based on the fee unit price acquired by the means, and a fee recording data generation unit 102e as a fee recording data generation means for generating fee recording data including the fee recording data.

The sales unit price acquisition unit 102a includes the site identification data (site code), the contract identification data (contract branch number), the product identification data (product code), the sales unit price, the purchase unit price, and the above. From the product data 106c including the classification, it is linked with the site identification data (site code), contract identification data (contract branch number) and product identification data (product code) entered on the sales purchase registration screen (see FIG. 7). Acquire the unit price and the fee for which the above-mentioned category (“〇”) is set.

The fee unit price acquisition unit 102b uses the site identification data (site code), the contract identification data (contract branch number), the fee identification data for identifying the fee (commission code), and the unit price of the fee. From the fee data (receipt fee data 106d and payment fee data 106e) including a certain fee unit price, the sales are linked to the input site identification data (site code) and contract identification data (contract branch number). The fee identification data (commission code) and the fee unit price for the fee acquired by the unit price acquisition unit 102a are acquired.

The sales data generation unit 102c includes the input site identification data (site code), the input contract identification data (contract branch number), the input product identification data (product code), and the sales unit. The sales data 106f including the number of sales of the product input on the entry registration screen and the sales amount calculated based on the sales unit price acquired by the sales unit price acquisition unit 102a is generated.

The purchase data generation unit 102d includes the input site identification data (site code), the input contract identification data (contract branch number), the input product identification data (product code), and the sales. Generates purchase data 106 g including the purchase number calculated on the purchase registration screen and the purchase amount calculated based on the purchase unit price acquired by the sales unit price acquisition unit 102a.

The fee recording data generation unit 102e includes the input site identification data (site code), the input contract identification data (contract branch number), and the fee identification data (commission) acquired by the fee unit price acquisition unit 102b. The fee recording data (receipt fee recording data 106h) including the code) and the fee amount calculated and recorded based on the fee unit price acquired by the number of the input products and the fee unit price acquisition unit 102b. And the payment fee recording data 106i) is generated.

The fee recording data generation unit 102e may generate the fee recording data at the timing of the determination even for the fee that was not recorded because the fee unit price was determined after the sales registration and the purchase registration. can. In this case, the fee recording data generation unit 102e has the input site identification data (site code), the input contract identification data (contract branch number), and the fee identification acquired by the fee unit price acquisition unit 102b. Calculated and recorded based on the data (fee code), the number of the input products, and the fee unit price after the determination set in the fee data (receipt fee data 106d and payment fee data 106e). The fee recording data (receipt fee recording data 106h and payment fee recording data 106i) including the fee amount is generated.

[3. Specific example of processing]
In this item, a specific example of the process according to this embodiment will be described.

[3-1. Contract registration process]
First, when a contract for buying and selling product information is made with a business partner, the contract information is registered by the contract registration process as shown in FIGS. 5 and 6. That is, the site data 106a, the contract data 106b, and the product data 106c are registered with the contents shown in FIG. Further, the received fee data 106d and the payment fee data 106e are registered with the contents shown in FIG.

[3-2. Sales purchase registration process]
Subsequently, the sales data 106f and the purchase data 106g are generated by registering the sales and the purchase on the sales purchase registration processing screen of FIG. 7. At this time, the receipt fee recording data 106h and the payment fee recording data 106i are also generated at the same time. Hereinafter, a specific description will be given.

First, on the sales purchase registration processing screen shown in FIG. 7, "2020/9/10" is entered as the recording date, "GB0001" is entered as the site code, "1" is entered as the contract branch number, and the product line is entered. "400" is input as the number of sales and purchases of 1 (product: ready-made concrete), and "200" is input as the number of sales and purchases of product line 2 (product: bag cement), and then the screen is displayed. The "Register" button at the bottom right is pressed. When the pressing is performed, the following processes (1) to (5) are executed.

(1) Sales unit price acquisition process The sales unit price acquisition unit 102a receives the input site code "GB0001", contract branch number "1" and product line 1 (product: ready-made concrete) from the product data 106c in FIG. Acquire 1,800 yen and 1,900 yen, respectively, as the sales unit price and the purchase unit price associated with. Further, the unit sales price acquisition unit 102a is charged as the commission associated with the input site code "GB0001", contract branch number "1" and product line 1 (product: ready-made concrete) from the product data 106c in FIG. , Acquire the fees marked with "○", that is, the receiving fee 1, the receiving fee 2, and the payment fee 1.

Similarly, the sales unit price acquisition unit 102a is associated with the input site code “GB0001”, contract branch number “1”, and product line 2 (product: bag cement) from the product data 106c in FIG. And as the purchase unit price, 900 yen and 950 yen will be acquired, respectively. On the other hand, referring to the product data 106c in FIG. 5, there is no fee with "○" in the line of the site code "GB0001", the contract branch number "1" and the product line 2 (product: bag cement). Therefore, the unit sales price acquisition unit 102a does not acquire commissions for the site code "GB0001", the contract branch number "1", and the product line 2 (product: bag cement).

(2) Fee unit price acquisition process Next, the fee unit price acquisition unit 102b obtains the input site code “GB0001” and contract branch number “1” from the received fee data 106d or the payment fee data 106e in FIG. Acquire the commission name and commission unit price for the commission acquired by the sales unit price acquisition unit 102a in (1).

Specifically, the fee unit price acquisition unit 102b is associated with the input site code "GB0001" and the contract branch number "1" from the received fee data 106d in FIG. 6, and is acquired in (1). Acquire the commission name "receipt sales commission" and the receipt commission unit price "500 yen" for the receipt fee 1 (corresponding to the receipt fee line No. 1). On the other hand, referring to the receipt fee data 106d in FIG. 6, the receipt fee 1 (receipt fee line No. 2) linked to the input site code “GB0001” and the contract branch number “1” and acquired in (1). Since the commission unit price associated with (corresponding to) is blank (that is, the unit price is undecided), the commission unit price acquisition unit 102b acquires the commission name "sales business cooperation fee", but the commission unit price received No acquisition is done.

Similarly, the fee unit price acquisition unit 102b is associated with the input site code “GB0001” and the contract branch number “1” from the payment fee data 106e in FIG. 6, and the payment fee acquired in (1). Acquire the fee name "payment sales fee" and the payment fee unit price "400 yen" for 1 (corresponding to the payment fee line No. 1).

(3) Sales data generation process Next, the sales data generation unit 102c includes sales detail data for product row 1 (product: ready-mixed concrete) and sales detail data for product row 2 (product: bag cement). The sales data 106f of the above is generated. As shown in FIG. 8, the sales details data for the product line 1 (product: ready-made concrete) are the input site code "GB0001", the input contract branch number "1", and the input. It includes a product line 1 (product: ready-made concrete), a sales amount of "720,000 yen" calculated based on the input sales number of 400 and a sales unit price of 1,800 yen acquired in (1), and the like. Further, as shown in FIG. 8, the sales detail data for the product line 2 (product: bag cement) includes the input site code "GB0001", the input contract branch number "1", and the input. It includes the product line 2 (product: bag cement), the sales amount "180,000 yen" calculated based on the input sales number 200 and the sales unit price of 900 yen acquired in (1), and the like.

(4) Purchase data generation process Similarly, the purchase data generation unit 102d has purchase detail data for product line 1 (product: ready-made concrete) and purchase detail data for product line 2 (product: bag cement). The purchase data 106 g of FIG. 8 including the above is generated. As shown in FIG. 8, the purchase details data for the product line 1 (product: ready-made concrete) are the input site code "GB0001", the input contract branch number "1", and the input. The purchase amount "760,000 yen" calculated based on the product line 1 (product: ready-made concrete) and the purchase unit price of 1,900 yen acquired in the input number of purchases of 400 and (1). Etc. are included. Further, as shown in FIG. 8, the purchase details data for the product line 2 (product: bag cement) include the input site code “GB0001”, the input contract branch number “1”, and the above. The input product line 2 (product: bag cement) and the purchase amount "190,000 yen" calculated based on the input number of purchases of 200 and the purchase unit price of 950 yen acquired in (1). Etc. are included.

(5) Fee recording data generation process Finally, the fee recording data generation unit 102e generates the receiving fee recording data 106h and the payment fee recording data 106i. Here, as described in (3) and (4), the sales data 106f and the purchase data 106g are generated for both the product line 1 (commodity: ready-mixed concrete) and the product line 2 (commodity: bag cement). rice field. On the other hand, as explained in (1), the fee for product line 2 (commodity: bag cement) has not been acquired (that is, the fee for bag cement is not incurred in the first place), so the fee accrual data. The 106h and the payment fee recording data 106i are generated only for the product line 1 (commodity: ready-mixed concrete). Hereinafter, a specific description will be given.

The fee recording data generation unit 102e has the input site code "GB0001", the input contract branch number "1", and the fee name acquired in (2) for the product line 1 (product: ready-made concrete). Recording of the receipt fee in FIG. 8 including the "sales commission received", the sales amount "200,000 yen" calculated based on the input sales number 400 and the receipt commission unit price of 500 yen acquired in (2), and the like. Generate data 106h.

As described in (2), regarding the commission received 2 (sales business cooperation fee), the commission unit price in the commission data 106d received in FIG. 6 is blank (that is, the unit price is undecided). Therefore, for the receipt fee 2 (sales business cooperation money) of the product line 1 (commodity: ready-mixed concrete), the receipt fee recording data 106h is not generated at this point.

The fee recording data generation unit 102e has the input site code "GB0001", the input contract branch number "1", and the fee name acquired in (2) for the product line 1 (product: ready-made concrete). Payment in FIG. 8 including "payment and sales commission", purchase amount "160,000 yen" calculated based on the input number of purchases of 400 and the payment commission unit price of 400 yen acquired in (2), and the like. Generate fee recording data 106i.

The data generated in this item [3-2] can be summarized as follows. That is, data was generated for the site code "GB0001" and the contract branch number "1". Sales data 106f and purchase data 106g were generated for both product row 1 (commodity: ready-mixed concrete) and commodity row 2 (commodity: bag cement). On the other hand, since no fee is incurred for the product line 2 (product: bag cement), the receipt fee recording data 106h and the payment fee recording data 106i are generated only for the product line 1 (product: ready-mixed concrete). .. The commissions incurred for the product line 1 (commodity: ready-made concrete) are the receipt commission 1 (receipt sales commission) and the payment commission 1 (payment sales commission). The commission received 2 (sales business cooperation fee) does not occur at this point because the unit price is undecided. Therefore, the receipt fee recording data 106h including the receipt fee 1 (receipt sales fee) for the product line 1 (product: ready-made concrete) and the payment fee 1 (payment sales fee) for the product line 1 (product: ready-made concrete) are charged. Payment fee recording data 106i including is generated.

[3-3. Contract registration process]
Subsequently, when the commission unit price for the undecided receipt fee 2 (sales business cooperation fee) is determined, the determined commission unit price of 300 yen and the commission start date 2020/9 are shown in Figure 9 by the contract registration process again. As shown in the above, it is registered in the receipt fee data 106d.

[3-4. Automatic fee recording process]
Finally, the fee automatic recording process generates the received fee recording data 106h for the received fee 2 (sales business cooperation fee), which is the unrecorded fee.

Specifically, on the fee automatic accounting processing screen shown in FIG. 10, when the accounting date and, if necessary, the site code are input and the "execute" button at the lower right of the screen is pressed, the following The fee recording data generation process is executed.

The fee recording data generation unit 102e has the input site code "GB0001", the input contract branch number "1", and the fee name acquired in (2) for the product line 1 (product: ready-made concrete). Details including the "sales business cooperation fee", the sales amount "120,000 yen" calculated based on the input sales number 400 and the commission unit price of 300 yen determined in [3-3], and the like (FIG. 11). (Details marked with ★) are added to the receipt fee recording data 106h.

[4. Summary of this embodiment]
As described above, according to the fee recording data generation device 100 according to the present embodiment, the fee can be recorded at the same time as the sales registration and the purchase registration. Further, according to the fee recording data generation device 100 according to the present embodiment, after the fee unit price is determined, the unrecorded fee can be recorded by automatically recording the fee.

[5. 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, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part can be automatically performed by a known method.

In addition, 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 this specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the fee recording data generation device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the fee recording data generation device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the fee recording data is recorded as necessary. It is read mechanically by the generator 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the fee accounting data generation device 100 via an arbitrary network, and all or a part thereof may be downloaded as needed. It is possible.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disc), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium and the installation procedure after reading in each device shown in the embodiment.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the fee accounting data generation 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 fee recording data generation device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

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

The present invention is useful in all industries and industries in which fees are incurred in connection with transactions, but is particularly useful in the wholesale and trading industry that handles ready-mixed concrete and cement.

100 Fee recording data generator 102 Control unit
102a Sales unit price acquisition department
102b Fee unit price acquisition department
102c Sales data generation unit
102d Purchasing data generator
102e Fee recording data generation unit 104 Communication interface unit 106 Storage unit
106a Field data
106b Contract data
106c Product data
106d Receiving fee data
106e Payment fee data
106f Sales data
106g Purchase data
106h Receipt fee recording data
106i Payment fee accounting data 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (4)

It is a fee recording data generation device equipped with a control unit.
The control unit
Site identification data for identifying the site of a business partner, contract identification data for identifying a contract with the business partner, product identification data for identifying a product to be delivered to the business partner, and the above. It is a screen for performing sales registration and purchase registration from product data including a product sales unit price and a purchase unit price, and a category for identifying whether or not the fee is generated, which is set for each fee. A means for acquiring the unit price associated with the site identification data, the contract identification data, the product identification data, and the fee, which has the above-mentioned category of occurrence, and the sales unit price, etc., which are input on the registration screen.
The input site identification data and contract identification from the fee data including the site identification data, the contract identification data, the fee identification data for identifying the fee, and the fee unit price which is the unit price of the fee. The commission identification data for the commission acquired by the sales unit price acquisition means and the commission unit price acquisition means for acquiring the commission unit price, which are linked to the data.
With the input site identification data, the input contract identification data, the input product identification data, the number of sales of the product input on the sales purchase registration screen, the sales unit price, and the like. A sales data generation means for generating sales data including a sales amount calculated based on the acquired sales unit price, and a sales data generation means.
The input site identification data, the input contract identification data, the input product identification data, the purchase number of the product input on the sales purchase registration screen, the sales unit price, and the like acquisition means. A purchase data generation means for generating purchase data including the purchase amount calculated based on the purchase unit price acquired in
The input site identification data, the entered contract identification data, the fee identification data acquired by the fee unit price acquisition means, the entered number of the products, and the fee unit price acquisition means. A fee recording data generation means for generating fee recording data including the fee amount calculated and recorded based on the acquired fee unit price, and
To prepare for
A fee recording data generator featuring. It is possible to generate the fee recording data at the timing of the determination even for the fee that was not recorded because the fee unit price was determined after the sales registration and the purchase registration.
The fee accrual data generation means receives the input site identification data and the input contract identification data, triggered by the instruction from the screen for instructing the accrual of the unaccounted fee. , The commission amount calculated and recorded based on the commission identification data acquired by the commission unit price acquisition means, the entered number of the products, and the determined commission unit price set in the commission data. To generate the fee accounting data, including
The fee recording data generation device according to claim 1. It is a fee recording data generation method executed by an information processing device equipped with a control unit.
Executed by the control unit,
Site identification data for identifying the site of a business partner, contract identification data for identifying a contract with the business partner, product identification data for identifying a product to be delivered to the business partner, and the above. It is a screen for performing sales registration and purchase registration from product data including a product sales unit price and a purchase unit price, and a category for identifying whether or not the fee is generated, which is set for each fee. The unit price associated with the site identification data, contract identification data, and product identification data entered on the registration screen, and the sales unit price acquisition step for acquiring the fee for which the above-mentioned category with occurrence is set, and
The input site identification data and contract identification from the fee data including the site identification data, the contract identification data, the fee identification data for identifying the fee, and the fee unit price which is the unit price of the fee. The commission identification data for the commission acquired in the sales unit price acquisition step and the commission unit price acquisition step for acquiring the commission unit price, which are linked to the data, and
In the input site identification data, the input contract identification data, the input product identification data, the number of sales of the product input on the sales purchase registration screen, the sales unit price, etc. acquisition step. A sales data generation step for generating sales data including a sales amount calculated based on the acquired sales unit price, and a sales data generation step.
The input site identification data, the input contract identification data, the input product identification data, the purchase number of the product input on the sales purchase registration screen, the sales unit price, and the like acquisition step. A purchase data generation step for generating purchase data including the purchase amount calculated based on the purchase unit price acquired in
In the input site identification data, the entered contract identification data, the fee identification data acquired in the fee unit price acquisition step, the number of the input products, and the fee unit price acquisition step. A fee recording data generation step for generating fee recording data including a fee amount calculated and recorded based on the acquired fee unit price, and a fee recording data generation step.
To include,
A method for generating fee recording data. It is a fee recording data generation program to be executed by an information processing device equipped with a control unit.
To make the control unit execute
Site identification data for identifying the site of a business partner, contract identification data for identifying a contract with the business partner, product identification data for identifying a product to be delivered to the business partner, and the above. It is a screen for performing sales registration and purchase registration from product data including a product sales unit price and a purchase unit price, and a category for identifying whether or not the fee is generated, which is set for each fee. The unit price associated with the site identification data, contract identification data, and product identification data entered on the registration screen, and the sales unit price acquisition step for acquiring the fee for which the above-mentioned category with occurrence is set, and
The input site identification data and contract identification from the fee data including the site identification data, the contract identification data, the fee identification data for identifying the fee, and the fee unit price which is the unit price of the fee. The commission identification data for the commission acquired in the sales unit price acquisition step and the commission unit price acquisition step for acquiring the commission unit price, which are linked to the data, and
In the input site identification data, the input contract identification data, the input product identification data, the number of sales of the product input on the sales purchase registration screen, the sales unit price, etc. acquisition step. A sales data generation step for generating sales data including a sales amount calculated based on the acquired sales unit price, and a sales data generation step.
The input site identification data, the input contract identification data, the input product identification data, the purchase number of the product input on the sales purchase registration screen, the sales unit price, and the like acquisition step. A purchase data generation step for generating purchase data including the purchase amount calculated based on the purchase unit price acquired in
In the input site identification data, the entered contract identification data, the fee identification data acquired in the fee unit price acquisition step, the number of the input products, and the fee unit price acquisition step. A fee recording data generation step for generating fee recording data including a fee amount calculated and recorded based on the acquired fee unit price, and a fee recording data generation step.
To include,
A fee recording data generation program featuring.

Images