Business support device, business support method, and business support program

Abstract

To provide a work supporting device, a method for supporting a work, and a program that can easily make sale data on which various different discount processing are reflected.SOLUTION: In a work supporting device 1, an input processing unit 22 stores and controls a discount amount of an item or a service. A sale data generation unit 23 reads a discount amount determined for a customer who got an item or a service from the discount amount master, and generates sale data including at least the sale amount of the item or the service provided to the customer and the discount amount read from the discount amount master.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a task support device, a task support method, and a task support program. [Background technology]

[0002] Nowadays, when a product is sold, various discount processes such as wholesaler discount, partial refund, or deduction of collection freight, in addition to the normal sales discount, are performed according to an agreement with a customer. As a background technique for such discount processes, Patent Document 1 (JP Patent Publication 2001-175952 A) discloses a product sales data processing device that can perform member preferential discount processing for bulk products. This product sales data processing device is configured to be able to read the normal sales price of the product from the label code attached to the product and to be able to register the product using the read normal sales price. Then, when the normal sales price is read from the label code, this product sales data processing device determines whether the product is a bulk product. If the product is determined to be a bulk product by this determination and the customer is a member, the product weight and the member preferential unit price per unit weight, which is the unit price for member preferential treatment per unit weight, are used to calculate the member preferential sales price of the product. This allows the member preferential discount processing of bulk products. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-175952 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, discount processing includes various discount processing such as wholesale discount, part refund, and deduction of collection freight in addition to normal sales discount, depending on the agreement with the customer. Also, the discount processing that occurs differs depending on whether the customer is a wholesaler or an end user, and a great number of discount processing patterns occur depending on the order contents. For this reason, it was very time-consuming work to create sales data that reflected such a large number of discount processing patterns.

[0005] The present invention has been made in consideration of the above, and has an object to provide a business support device, a business support method, and a business support program that enable easy creation of sales data that reflects various discount processing. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objectives, the business support device of the present invention has an input processing unit that controls the storage of discount amounts agreed upon for products or services for each customer in a discount amount master, and a sales data generation unit that reads out the discount amounts agreed upon with customers to which products or services have been provided from the discount amount master, and generates sales data including at least the sales amount of the products or services provided to the customers and the discount amounts read from the discount amount master. Effect of the Invention

[0007] According to the present invention, it is possible to easily create sales data that reflects various discount processes. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a task support device according to an embodiment. [Diagram 2] FIG. 2 is a flowchart for explaining the flow of an automatic reflection operation of discount processing for each customer on sales data in the business support device according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of customer-specific product unit price data registered in the customer-specific product unit price master. [Figure 4] FIG. 4 is a diagram showing an example of an order input screen displayed on the output device by the display control unit. [Diagram 5] FIG. 5 is a diagram illustrating an example of the order data. [Figure 6] FIG. 6 is a diagram showing an example of the sales lump-sum entry screen. [Figure 7] FIG. 7 is a diagram showing an example of customer-specific product unit price data. [Figure 8] FIG. 8 is a diagram illustrating an example of the order category allocation list data. [Figure 9] FIG. 9 is a diagram for explaining order categories. [Figure 10] FIG. 10 is a diagram for explaining the system transaction division. [Figure 11] FIG. 11 is a diagram illustrating an example of sales data. [Figure 12] FIG. 12 is a diagram illustrating an example of sales performance data by customer of the person in charge. [Figure 13] FIG. 13 is a diagram illustrating an example of sales performance data by product and by person in charge. [Figure 14] FIG. 14 is a diagram showing only the sales journal portion of the journal data in which sales data is reflected. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A task support device according to an embodiment of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that the present invention is not limited to the embodiment.

[0010] In order to solve the above-mentioned problems and achieve the object, the business support device according to the present invention includes an input processing unit that controls the storage of discount amounts agreed upon for each customer for a product or service in a discount amount master, and a sales data generating unit that reads out discount amounts agreed upon with a customer to whom the product or service has been provided from the discount amount master and generates sales data including at least the sales amount of the product or service provided to the customer and the discount amount read out from the discount amount master. The input processing unit controls and stores the discount amount of the type to be applied for each order category of the product or service in the discount amount master.

[0011] An input device 6 and an output device 7 are connected to the input / output interface unit 5. A monitor device (including a home television) can be used as the output device 7. As the input device 6, a keyboard device, a mouse device, a microphone device, and a monitor device that cooperates with a mouse device to realize a pointing device function can be used.

[0012] The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive). The storage unit 2 stores a customer product unit price master 11 (an example of a discount amount master) in which customer-specific product unit price data indicating various discount amounts for each customer and each product is registered. The storage unit 2 also stores a business support program that enables the creation and analysis of sales data that automatically reflects discount processing for each customer. The storage unit 2 also stores a financial accounting system that works in conjunction with the business support program to record and record the sales data.

[0013] The storage unit 2 also stores order data that records the details of orders from customers, sales data for each customer, sales performance data by customer for each person in charge and for each customer, sales performance data by product and by person in charge that is aggregating the sales performance of each product for each person in charge, and journal data that classifies transaction elements into debit and credit and records the account items and amounts. The storage unit 2 also stores order category allocation list data that indicates the unit price acquisition rules when creating discount slips from order data.

[0014] The control unit 3 operates based on the business support program stored in the memory unit 2, and functions as a display control unit 21, an input processing unit 22, a sales accounting unit 23 (an example of a sales data generation unit), a sales performance table reflection processing unit 24, a journal data creation processing unit 25 (an example of a journal data generation unit), and an output control unit 26.

[0015] In this example, the display control unit 21 to the output control unit 26 are described as being realized by software using a business support program, but all or part of these may be realized by hardware such as an IC (Integrated Circuit).

[0016] The business support program may be provided by recording file information in an installable or executable format on a computer-readable recording medium such as a CD-ROM or a flexible disk (FD). The business support program may be provided by recording file information in an installable or executable format on a computer-readable recording medium such as a CD-R, a DVD (Digital Versatile Disk), a Blu-ray (registered trademark) disk, or a semiconductor memory. The business support program may be provided by installing the program via a network such as the Internet. The business support program may be provided by being pre-installed in a ROM or the like within a device.

[0017] [Automatic reflection of discount processing for each customer in sales data] Next, an operation of automatically reflecting discount processing for each customer on sales data in the business support device 1 of the embodiment will be described. Fig. 2 is a flowchart for explaining the flow of an operation of automatically reflecting discount processing for each customer on sales data in the business support device 1 of the embodiment. The control unit 3 of the business support device 1 operates based on a business support program stored in the memory unit 2 to execute each process of the flowchart in Fig. 2.

[0018] (Master registration operation of unit price contract conclusion result) First, in step S1, for example, a business operator inputs the conclusion result of the unit price agreement for each customer via the input device 6. The input processing unit 21 registers the input conclusion result of the unit price agreement for each customer in the customer-specific product unit price master 11.

[0019] Fig. 3 is a schematic diagram of the customer-specific product unit price master 11 in which customer-specific product unit price data is registered. As an example, as shown in the example of Fig. 3, the customer number (customer ID), application start date, application end date, product name, sales price, set discount, discount unit price, and pick-up freight are registered as customer-specific product unit price data.

[0020] The lump-sum discount is the discount amount for a lump sum. This lump-sum discount is incurred based on the amount registered each time a transaction occurs. Note that the lump-sum discount is not the unit price x quantity discount amount, but the registered discount amount is deducted from the sales amount of the product to that customer. The discount unit price is the amount discounted for one product. The amount multiplied by the order or sales quantity is deducted from the sales amount of the product. The pick-up freight is the amount discounted as freight when the customer comes to pick up the product. It is incurred based on the amount registered each time a transaction occurs. The pick-up freight is not incurred based on the unit price x quantity, but the registered pick-up freight amount is deducted from the sales amount generated in one transaction.

[0021] The example in Figure 3 shows an example of selling a product with a product ID of "S01" and a product name of "Product A" for "Customer A" with a customer ID of "0001" for "1,000 yen" with the effective date set as "April 1, 2021." It also shows that an agreement has been made with Customer A regarding a total discount of "-50 yen" for Product A sold for "1,000 yen," a discount unit price of "-75 yen" per product, and a discount of "-500 yen" for the pick-up fee when Customer A comes to pick up the product.

[0022] The example in Figure 3 shows that for "Customer B" with customer ID "0002", a product with product ID "S01" and product name "Product A" will be sold for "1100 yen" with the effective date set as "June 7, 2021". It also shows that an agreement has been made with Customer B regarding a total discount of "-45 yen" for Product A sold for "1100 yen", a discount unit price of "-65 yen" per product, and a discount of "-550 yen" for the pick-up fee when Customer B comes to pick up the product.

[0023] In this manner, the customer-specific product unit price master 11 registers customer-specific product unit price data indicating various discount amounts agreed upon for each customer and each product.

[0024] (Invoice entry operation corresponding to order) Next, in step S2 of the flowchart in Fig. 2, the input processing unit 22 and sales accounting unit 23 control the input of the order information of the ordered product, entered by the business operator via the input device 6, onto the order input screen to form order data (voucher input processing). Fig. 4 is a diagram showing an example of the order input screen displayed on the output device 7 by the display control unit 21. As shown in the example of Fig. 4, the order input screen has display columns for the order date, expected sales date, and customer ID of the customer. The order input screen also has display columns for the order category, product name, order quantity, unit sales price, and sales amount.

[0025] On the order entry screen, the business operator inputs an order date, for example, April 10, 2021, and a planned sales date of the product, for example, April 11, 2021, and selects a customer ID of the customer selling the product, such as 0001. As a result, the input processing unit 22 and the display control unit 21 display the dates input by the business operator in the order date display field and the planned sales date display field on the order entry screen. In addition, the input processing unit 22 and the display control unit 21 display the customer name to which the customer ID selected by the business operator is assigned in the customer name display field on the order entry screen.

[0026] The business operator also inputs the order category, the product ID of the sold product, the order quantity, and the unit sales price on the order input screen. As a result, the input processing unit 22 and the display control unit 21 display the order category ID, for example, "01", and the type of the order category, for example, "normal", in the order category display field on the order input screen, and display the product ID, for example, "XXXXX", and the product name, for example, "Product A", in the product name display field. The input processing unit 22 and the display control unit 21 also display the number of ordered products, for example, "15", in the order quantity display field, and display the unit price of product A, for example, "1000 yen", which is agreed upon with customer A, in the sales price display field. The sales accounting unit 23 also calculates the sales amount by multiplying the order quantity by the sales price. The input processing unit 22 and the display control unit 21 display the sales amount, for example, "15000 yen", in the sales amount display field on the order input screen.

[0027] In addition, the sales accounting unit 23 creates the order data shown in FIG. 5 based on such input information. As an example, the sales accounting unit 23 creates order data including a slip number-line number, customer name, sales date, order category, product name, order quantity, sales price, and sales amount, as shown in FIG. 5. The example in FIG. 5 is an example in which order data is created that includes a slip number-line number of "J00001-1", a customer name of "0001: Customer A", a sales date of "April 11, 2021", an order category of "01: Normal", a product name of "S01: Product A", an order quantity of "15", a sales price of "1000 yen", and a sales amount of "15,000 yen".

[0028] (Sales recording process) Next, in step S3 of the flowchart in FIG. 2, the sales accounting unit 23 records the order data as sales by system processing after the product shipping process is completed. Specifically, when the business operator inputs a sales date of, for example, April 11, 2021, into the sales lump-sum accounting screen shown in FIG. 6, the sales accounting unit 23 acquires the order data described using FIG. 5 from the storage unit 2, and acquires customer-specific product unit price data corresponding to the customer from the customer-specific product unit price master 11, as shown in FIG. 7. Then, the sales accounting unit 23 refers to the order category allocation list data stored in the storage unit 2 and creates sales data for each sales category assigned to the order category.

[0029] FIG. 8 is a diagram showing an example of order category allocation list data. FIG. 9 is a diagram for explaining the order categories shown in FIG. 8. The "normal" order category with order category ID "01" shown in FIG. 8 is an order category for warehouse orders with delivery, as shown in FIG. 9. The "normal / pickup" order category with order category ID "02" shown in FIG. 8 is an order category for warehouse orders where the customer picks up the product, as shown in FIG. 9. The "gift" order category with order category ID "03" shown in FIG. 8 is an order category for free sales of sample products, etc., as shown in FIG. 9.

[0030] The "Pickup" order category with an order category ID of "05" shown in Figure 8 indicates the order category used when pick-up is decided later and a slip with only the pick-up discount is created, as shown in Figure 9. Additionally, the "Returns - Regular" order category with an order category ID of "06" shown in Figure 8 indicates the order category used for return processing for the order category "01: Regular", as shown in Figure 9. The "Returns - Pick-up" order category with an order category ID of "07" shown in Figure 8 indicates the order category used for return processing for the order category "02: Regular - Pick-up", as shown in Figure 9.

[0031] The "Unit Price Correction" order category with an order category ID of "08" shown in Figure 8 indicates the order category used when creating an adjusted sales slip to correct the unit sales price, as shown in Figure 9. Additionally, the "Discount" order category with an order category ID of "09" shown in Figure 8 indicates the order category used when creating a discount slip processed at unit price, as shown in Figure 9. Additionally, the "All-set Discount" order category with an order category ID of "10" shown in Figure 8 indicates the order category used when creating a discount slip processed at a all-set amount, as shown in Figure 9.

[0032] Specifically, as shown in Fig. 8, for the "normal" order category with order category ID "01", the sales price, the package discount, and the discount unit price are reserved, but the pick-up freight is not reserved, as indicated by the "circle" or "cross" in Fig. 8. Therefore, the sales accounting unit 23 creates sales data for normal sales with sales category "01", discounts with sales category "11", and package discounts with sales category "12" as shown in Fig. 8.

[0033] For regular sales with a sales category of "01", the system transaction category is "10", sales data is generated as "order data inheritance", and the customer-specific product unit price master data is adopted as "sales unit price". For discounts with a sales category of "11", the system transaction category is "30", sales data is generated as "automatic creation at time of sale", and the customer-specific product unit price master data is adopted as "discount unit price". For lump-sum discounts with a sales category of "12", the system transaction category is "30", sales data is generated as "automatic creation at time of sale", and the customer-specific product unit price master data is adopted as "lump-sum discount".

[0034] FIG. 10 is a diagram for explaining system transaction categories. As shown in FIG. 10, a system transaction category of "10" indicates regular sales, and is processed in a sales revenue account when journal data is created. A system transaction category of "20" indicates sales returns, and is processed in a sales revenue return account when journal data is created. A system transaction category of "30" indicates sales discounts, and is processed in a sales discount account when journal data is created. A system transaction category of "60" indicates unpaid sales, and no journal data is generated.

[0035] Also, as shown in Fig. 8, for the order category of "normal-pickup" with an order category ID of "02", the sales unit price, package discount, discount unit price and pick-up freight are allocated as indicated by the "circle" in Fig. 8. For this reason, the sales accounting unit 23 creates sales data for normal sales with sales category "01", pick-up freight with sales category "10", discount with sales category "11", and package discount with sales category "12" as shown in Fig. 8. For pick-up freight with sales category "10", the system transaction category is "30", the generation of sales data is "automatic generation at time of sale", and the adoption of the customer-specific product unit price master is "pick-up freight".

[0036] Also, as shown in Figure 8, for the "gift" order category with an order category ID of "03", the sales price, set discount, discount unit price and collection freight are not allocated, as indicated by the "x" in Figure 8. No journal entry data is created for this "gift". Note that for the "gift" sales category of "03", the system transaction category is "60", and both the generation of sales data and the adoption of the product unit price master by customer are set to "order data inheritance".

[0037] Also, as shown in FIG. 8, for the order category with order category ID "04" and "Sales recorded", there is no provision for the unit sales price, package discount, discount unit price, or pick-up freight, as indicated by the "X" in FIG. 8.

[0038] Also, as shown in Fig. 8, for the order category "Pickup" with order category ID "05", the pick-up freight is reserved, as indicated by the "circle" in Fig. 8, but the sales price, package discount, and discount unit price are not reserved. Therefore, the sales accounting unit 23 creates sales data for pick-up with sales category "04" as shown in Fig. 8. For pick-up with sales category "04", the system transaction category is "30", and both the generation of sales data and the adoption of the customer-specific product unit price master are set to "order data inheritance".

[0039] Also, as shown in Fig. 8, for the order category "Returns - Regular" with an order category ID of "06", the sales price, package discount, and discount unit price are allocated, but the pick-up freight is not allocated, as indicated by the "circle" in Fig. 8. For this reason, the sales accounting unit 23 creates sales data for returns with a sales category of "03", discounts with a sales category of "11", and package discounts with a sales category of "12", as shown in Fig. 8. For returns with a sales category of "03", the system transaction category is "20", the generation of sales data is "order data inheritance", and the adoption of the customer-specific product unit price master is "sales price".

[0040] Also, as shown in Fig. 8, for the order category of "returns-pickup" with an order category ID of "07", the sales unit price, the set discount, the discount unit price, and the pick-up freight are allocated as indicated by the "circle" in Fig. 8. Therefore, the sales accounting unit 23 creates sales data for returns with a sales category of "03", pick-up freight with a sales category of "10", the discount with a sales category of "11", and the set discount with a sales category of "12", as shown in Fig. 8.

[0041] Also, as shown in Fig. 8, for the order category of "unit price correction" with order category ID "08", the sales unit price, package discount, discount unit price and collection freight are not allocated, as indicated by the "X" in Fig. 8. In this case, the sales accounting unit 23 creates sales data for unit price correction with sales category "05" as shown in Fig. 8. For unit price correction with sales category "05", the system transaction category is "30", and both the generation of sales data and the adoption of product unit price master by customer are set to "order data inheritance".

[0042] Also, as shown in Fig. 8, for the order category "Discount" with order category ID "09", the sales price, package discount, discount unit price and collection freight are not allocated, as indicated by the "X" in Fig. 8. In this case, the sales accounting unit 23 creates sales data for the discount with sales category "06" as shown in Fig. 8. For the discount with sales category "06", the system transaction category is "30", and both the generation of sales data and the adoption of the product unit price master by customer are set to "order data inheritance".

[0043] Also, as shown in Fig. 8, for the order category of "package discount" with order category ID "10", the sales price, package discount, discount unit price and collection freight are not allocated, as indicated by the "X" in Fig. 8. In this case, the sales accounting unit 23 creates sales data for the package discount with sales category "07" as shown in Fig. 8. The package discount with sales category "07" has a system transaction category of "30", and both the generation of sales data and the adoption of the product unit price master by customer are set to "order data inheritance".

[0044] In this way, when the sales accounting unit 23 accounts for sales of the order data inputted as an order, the sales data is automatically created by the customer master × customer product unit price master × order category. FIG. 11 is a diagram showing an example of sales data. The example in FIG. 11 shows the order data created corresponding to the order category "normal". As described above, in the case of the order category "normal", the sales unit price, the set discount, and the discount unit price are reserved. Therefore, as shown in FIG. 11, the sales accounting unit 23 creates sales data of the sales category with the slip number "U00001-1" and the sales category "01: normal", sales data of the sales category with the slip number "U00001-2" and the sales category "11: discount", and sales data of the sales category with the slip number "U00001-3" and the sales category "12: set discount".

[0045] The sales accounting unit 23 creates the sales data of the sales category "11: discount" and the sales data of the sales category "12: package discount" in the form of additional details in the same slip as the sales data of the sales category "01: normal". That is, in the example of FIG. 11, the sales accounting unit 23 first accounts for the sales data of the sales category "01: normal" with the slip number "U00001-1" based on the order data. Next, the sales accounting unit 23 automatically creates and accounts for the sales data of the sales category "11: discount" with the slip number "U00001-2" and the sales category "12: package discount" with the slip number "U00001-3" by the sales lump-sum accounting process. This allows each sales data to be printed on the same delivery note slip.

[0046] (Sales data reflected in the performance table) Next, in step S4 of the flowchart in Fig. 2, the sales performance table reflection processing unit 24 reflects the recorded sales data in the performance table. Fig. 12 is a diagram showing an example of sales performance data by customer and person in charge. As shown in Fig. 12, the sales performance table reflection processing unit 24 reflects the sales data of regular sales, discounts, all-in-one discounts, pick-up freight, returns, gifts, and totals for each person in charge and for each customer in the sales performance data by customer and person in charge. This makes it possible to manage the sales performance of each person in charge for each customer and to analyze sales, etc.

[0047] Fig. 13 is a diagram showing an example of sales performance data by product customer and responsible person. As shown in Fig. 13, the sales performance table reflection processing unit 24 reflects the sales data of regular sales, discounts, discounts for all items, return shipping, gifts, and total sales data for each product customer and each product customer in the sales performance data by product customer and responsible person. This makes it possible to manage the sales performance of each product by each product customer and to analyze sales, etc.

[0048] Next, in step S5 of the flowchart in FIG. 2, the journal data creation processing unit 25 (an example of a journal data generation unit) works in conjunction with a financial accounting system to record the sales data recorded as sales as described above in system processing. FIG. 14 is a diagram illustrating only the sales journal portion of the journal data reflecting the sales data. As shown in FIG. 14, the accounts receivable / sales amount is tallied as the amount in the regular sales category. Furthermore, the accounts receivable / sales discount amount is tallied as the amount in the discount, lump sum discount, and pick-up freight category. Furthermore, the accounts receivable / sales return amount is tallied as the amount in the return category.

[0049] In addition, depending on the settings for journal conversion, it is possible to set either aggregation by system transaction category or aggregation by sales category. Also, if aggregation by sales category is set, it becomes possible to grasp and analyze unit value discounts, lump sum discounts, and freight charges on the financial accounting and accounting side.

[0050] The output control unit 26 outputs and stores such recorded slips in the storage unit 2 or an external storage unit, or controls printing via a printer device, in response to an output operation by the business operator, etc. Alternatively, the output control unit 26 transfers such recorded slip data to an accounting server device, etc. via a specified network, in response to an output operation by the business operator, etc., and stores it.

[0051] [Effects of the embodiment] As is clear from the above explanation, the business support device 1 of the embodiment registers customer-specific product unit price data indicating the unit price of the product and various discount amounts agreed upon with the customer in the customer-specific product unit price master 11. Then, when the product is sold, the type of discount to be offered to the customer is automatically determined from the customer-specific product unit price master 11 and reflected in the sales recording of the product. This makes it possible to improve the processing speed of the slip creation work. It also reduces the input load of various input data and prevents input errors.

[0052] In addition, in managing and analyzing sales results, the amount of discount for each product, unit value discount, trends in pick-up shipping charges, etc. can also be analyzed, and this can be used to analyze products with large discounts or customers with large discounts, etc.

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

[0054] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0055] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0056] [Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0057] For example, the above embodiment has been described taking the sale of products as an example, but similar operations and effects can be obtained when providing a specific service by performing the same operations as described above.

[0058] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0059] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0060] Furthermore, with regard to the journal entry input system, the components shown in the figures are merely functional concepts, and the system does not necessarily have to be physically configured as shown in the figures.

[0061] For example, the processing functions of the business support device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium including programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 1 as necessary. 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 HDD. This computer program is executed by being loaded into a RAM, and constitutes the control unit 3 in cooperation with the CPU.

[0062] In addition, this business support program, which is a computer program, may be stored in another server device connected to the business support device 1 via any network, and it is also possible to download all or part of it as needed.

[0063] The business support program for executing the process described in the present embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0064] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a configuration that is distributed as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0065] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

[0066] The business support device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0067] Furthermore, the specific form of distribution and integration of the devices is not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0068] The present invention is useful for creating forms and the like that reflect discount processing for each customer. [Explanation of symbols]

[0069] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 11 Customer-specific product price master 21 Display control unit 22 Input Processing Section 23 Sales Accounting Department 24 Sales performance table reflection processing section 25 Journal entry data creation processing section 26 Output control section

Claims

1. an input processing unit that stores and controls a discount amount agreed upon for each customer for a product or service in a discount amount master; a sales data generating unit that reads out the discount amount agreed upon with the customer to whom the product or service has been provided from the discount amount master, and generates sales data including at least the sales amount of the product or service provided to the customer and the discount amount read out from the discount amount master; The input processing unit controls storage of the discount amount of the type to be applied for each order category of the product or service in the discount amount master. A business support device comprising:

2. The sales data generating unit generates sales data by adding details of the sales data of the discount amount to the slip into which the sales data of the sales amount has been input.

2. The business support device according to claim 1,

3. Further comprising a sales performance table reflection processing unit that creates a sales performance table showing the sales amount for each customer with the discount amount reflected based on the sales data, or creates a sales performance table showing the sales amount for each of the products or services with the discount amount reflected.

3. The business support device according to claim 1 or 2,

4. Further comprising a journal data generation unit that generates journal data based on the sales data.

4. The business support device according to claim 1, wherein:

5. A business support method executed by a business support device having an input processing unit and a sales data generation unit, a storage control step in which the input processing unit stores and controls the discount amount agreed upon for each customer for the product or service in a discount amount master; a sales data generating step in which the sales data generating unit reads out the discount amount agreed with the customer to whom the product or service has been provided from the discount amount master, and generates sales data including at least the sales amount of the product or service provided to the customer and the discount amount read out from the discount amount master; The input processing unit controls storage of the discount amount of the type to be applied for each order category of the product or service in the discount amount master. A business support method comprising:

6. Computer, an input processing unit that stores and controls a discount amount agreed upon for each customer for a product or service in a discount amount master; a sales data generating unit that reads out the discount amount agreed with the customer to whom the product or service has been provided from the discount amount master, and generates sales data including at least the sales amount of the product or service provided to the customer and the discount amount read out from the discount amount master; The input processing unit controls storage of the discount amount of the type to be applied for each order category of the product or service in the discount amount master. A business support program that features:

Images