Sales processing device, sales processing method, and sales processing program

Abstract

To prevent hoarding by a certain client by setting the transaction volume of sales at a campaign price, and to reduce the workload and error of preparing an invoice at that time.SOLUTION: A sales processing device of this embodiment is provided with: a master which is registered in association with a trading partner, a product, an application period, a quantity, and a range unit price which is a campaign unit price; and billing closing processing means for executing billing closing processing on a monthly basis with respect to a target trading partner, creates an invoice including a discount amount based on the sales data, and calculates the discount amount=the sum of the sales amounts of the sales data - (the sum of the sales numbers of the sales data × the range unit price of the master) when the quantity of the master ≥ the sum of the sales numbers of the sales data while the billing closing processing means in other cases calculates the discount amount=the sum of the sales amounts of the sales data (however, the sum of the amounts from the oldest sales date to the quantity of the master)-(the quantity of the master × the range unit price of the master).SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] For example, when selling a product, a low campaign price may be set to promote sales. Conventionally, a system for promoting sales by setting a campaign price is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-83802 Summary of the Invention [Problem to be solved by the invention]

[0004] However, for example, when a company wants to sell new or popular products to many customers by setting a campaign price, distribution and sales opportunities may be lost due to a certain customer buying up the product. In addition, the workload of creating invoices at such times may be large, and mistakes may occur.

[0005] The present invention has been made in consideration of the above, and aims to provide a sales processing device, a sales processing method, and a sales processing program that can prevent certain business partners from buying up products by setting the transaction volume for sales at campaign prices, and that can reduce the workload and errors involved in creating invoices. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a sales processing device equipped with a control unit, the control unit being configured to be able to access a range unit price master in which business partners, products, applicable periods, quantities, and range unit prices, which are campaign unit prices, are registered in association with each other, and the device is characterized by comprising: a sales input means for inputting sales data including sales numbers, sales dates, business partners, products, quantities, unit prices, and amounts; and a billing closing processing means for performing billing closing processing on a monthly basis for target business partners, creating invoices including discount amounts based on the sales data, and calculating the discount amount as follows: if the quantity in the range unit price master is greater than or equal to the total number of sales in the sales data, the discount amount = total sales amount of the sales data - (total number of sales in the sales data x range unit price in the range unit price master), and if the quantity in the range unit price master is less than the total number of sales in the sales data, the discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price in the range unit price master).

[0007] According to another aspect of the present invention, the invoice may include the following items for the target business partner: sales date, product, quantity, sales price, sales amount, and a line for a discount slip.

[0008] In addition, according to one aspect of the present invention, if the application period of the range unit price master spans multiple months, the billing closing processing means may calculate the discount amount in one lump sum during the billing closing processing for the month to which the end date of the application period belongs.

[0009] According to another aspect of the present invention, the business partners may include customers and their delivery destinations.

[0010] In order to solve the above-mentioned problems and achieve the object, the present invention provides a sales processing method executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a range unit price master in which a customer, a product, an applicable period, a quantity, and a range unit price which is a campaign unit price are associated and registered, and the control unit executes a sales input process of inputting sales data including a sales number, a sales date, a customer, a product, a quantity, a unit price, and an amount, and a billing process of executing a monthly billing closing process for a target customer, creating an invoice including a discount amount based on the sales data, and and an invoice closing process for calculating the discount amount as follows: if the quantity in the range unit price master is equal to or greater than the total number of sales in the sales data, the discount amount = total sales amount of the sales data - (total number of sales in the sales data x range unit price in the range unit price master), and if the quantity in the range unit price master is less than the total number of sales in the sales data, the discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price in the range unit price master).

[0011] In order to solve the above-mentioned problems and achieve the object, the present invention provides a sales processing program to be executed by an information processing device having a control unit, the control unit being configured to be able to access a range unit price master in which a customer, a product, an applicable period, a quantity, and a range unit price which is a campaign unit price are associated and registered, the program including a sales input process for inputting sales data including a sales number, a sales date, the customer, the product, the quantity, the unit price, and an amount into the control unit, a billing process for executing a monthly billing process for a target customer, creating an invoice including a discount amount based on the sales data, and calculating the discount amount. The sales processing program is characterized by the fact that it executes an invoice closing process that calculates the following when the quantity in the range unit price master is greater than or equal to the total number of sales in the sales data: discount amount = total sales amount of the sales data - (total sales number of the sales data x range unit price in the range unit price master), and when the quantity in the range unit price master is less than the total number of sales in the sales data: discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price in the range unit price master). [Effects of the Invention]

[0012] According to the present invention, by setting the transaction volume for sales at campaign prices, it is possible to prevent certain business partners from buying up all the products, and also to reduce the workload and errors involved in creating invoices. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a sales processing device according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the range unit price master. [Figure 3] FIG. 3 is a diagram illustrating an example of the structure of the price master. [Figure 4] FIG. 4 is a flowchart illustrating an outline of the overall processing of the control unit of the sales processing device according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing performed by the control unit of the sales processing device according to this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of processing by the control unit of the sales processing device in this embodiment. [Figure 7A] FIG. 7A is a diagram for explaining a specific example of processing by the control unit of the sales processing device in this embodiment. [Figure 7B] FIG. 7B is a diagram for explaining a specific example of processing by the control unit of the sales processing device in this embodiment. [Figure 7C] FIG. 7C is a diagram for explaining a specific example of processing by the control unit of the sales processing device in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing performed by the control unit of the sales processing device according to this embodiment. [Figure 9A] FIG. 9A is a diagram for explaining a specific example of processing by the control unit of the sales processing device according to this embodiment. [Figure 9B] FIG. 9B is a diagram for explaining a specific example of the processing performed by the control unit of the sales processing device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0015] [1. Overview] The outline of the present invention will be explained in the following order: [1-1. Problem], [1-2. Solution], [1-3. Effects], and [1-4. Processing Overview].

[0016] [1-1. Issues] The problems to be solved by the present invention will be explained from the viewpoints of 1. sales distribution and 2. billing amount calculation.

[0017] 1. Sales and Distribution For example, you may want to set a campaign price for new products or best-selling products and sell them to many customers, but if a certain customer buys up all the products, distribution and sales opportunities may be lost. Therefore, you may want to set a transaction volume for each customer within a certain period (mainly the billing period), and limit the price and transaction volume, such as charging the campaign price up to the set transaction volume and charging the regular price if the transaction volume exceeds the set transaction volume.

[0018] 2. Billing amount calculation If the transaction volume agreed upon at the time of invoicing is achieved, a discount is applied at the time of invoicing. In a typical business flow, discounts are often agreed upon for each transaction, but in this business flow, discounts are applied only at the time of invoicing, which is expected to have a sales promotion effect on stakeholders for the next transaction. However, because the price and amount based on the transaction volume are not determined until a certain period of time has passed, and because work is done within a tight business schedule until invoice issuance, there are issues such as increased workload and incorrect billing due to human error.

[0019] [1-2. Solution] In the present invention, the above problems are solved by the following method. 1. Set the tradable quantity and campaign price for each trading partner, product, and period (hereinafter referred to as the range unit price). 2. When calculating the invoice amount, the transaction volume is compared with the range unit price, and the difference from the regular price is automatically created as a discount slip.

[0020] [1-3.Effects] 1. According to the present invention, by setting the transaction volume at the campaign price, it is possible to prevent a certain trading partner from buying up all the products. As a result, for new products or best-selling products, the regular price can be set higher than the campaign price, and transactions above the set transaction volume can be restricted. 2. According to the present invention, not only can the workload during bill calculation be reduced and errors prevented through automatic calculation processing, but sales promotion can also be expected by showing discounts on bills.

[0021] [1-4. Processing Overview] 1. In the range unit price master, set the transaction volume and range price (campaign price) according to that transaction volume for each business partner, product, and period, and compare it with the regular price during the billing calculation process based on this master setting. 2. To calculate the invoice amount, a discount slip is generated for the difference between the regular price of each slip and the range unit price based on the transaction volume and range unit price set in the range unit price master during the invoice period.

[0022] The present invention is applicable to companies that wish to limit the amount of transactions when they set a campaign price.

[0023] [2. Configuration] FIG. 1 is a block diagram showing an example of the configuration of a sales processing device 100 according to this embodiment. The sales processing device 100 is, for example, a commercially available desktop personal computer. Note that the sales processing device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. In FIG. 1, the sales processing device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the sales processing device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicatively connects the sales processing device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the sales processing device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0027] The storage unit 106 stores microwave unit price master 106a, price master 106b, sales data, invoices, etc. Fig. 2 is a diagram showing an example of the configuration of microwave unit price master 106a. Fig. 3 is a diagram showing an example of the configuration of price master 106b.

[0028] The range unit price master 106a is a master for setting the applicable period of the campaign unit price for each business partner, and as shown in Figure 2, it can be composed of a table or the like in which business partners (e.g., customers and their delivery destinations), products, applicable periods, quantities, and range unit prices, which are campaign unit prices, are associated and registered.

[0029] The price master 106b is a master for setting a common normal unit price for all business partners, and can be configured as a table in which products and normal unit prices are registered in association with each other, as shown in FIG.

[0030] Sales data may include sales number, sales date, category, business partner (e.g., customer and its delivery destination), delivery destination, product, quantity, unit price, and amount.

[0031] The invoice contains rows for the sales slip and discount slip for the target business partner (destination), with the items (columns) of sales date, product, quantity, sales price, and sales amount.

[0032] The control unit 102 is a CPU or the like that performs overall control of the sales processing device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0033] Control unit 102 is configured to be able to access microwave unit price master 106a, price master 106b, sales data, invoices, etc. stored in storage unit 106. Microwave unit price master 106a, price master 106b, sales data, invoices, etc. may also be stored in other locations (for example, server 200) as long as control unit 102 is able to access them.

[0034] The control unit 102 conceptually includes a sales input unit 102a, an invoice settlement processing unit 102b, a master maintenance unit 102c, and a screen display control unit 102d.

[0035] The sales input unit 102a inputs sales data including the sales number, sales date, customer, product, quantity, unit price, and amount, for example, in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, and stores the data in the memory unit 106.

[0036] The billing processing unit 102b executes billing processing for the target business partner on a monthly basis in response to, for example, an operator's operation on an invoice output screen (not shown) displayed on the monitor 114, creates an invoice including a discount amount based on the sales data registered in the storage unit 106, stores the invoice in the storage unit 106a, and also outputs (displays and prints out) it. Regarding the discount amount, if the quantity in the microwave unit price master 106a is greater than or equal to the total number of sales in the sales data, the discount amount is calculated as follows: Discount amount = total sales amount of the sales data - (total sales number of the sales data x microwave unit price in the microwave unit price master 106a), and if the quantity in the microwave unit price master 106a is less than the total number of sales in the sales data, the discount amount is calculated as follows: Discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the microwave unit price master 106a is reached) - (quantity in the microwave unit price master 106a x microwave unit price in the microwave unit price master 106a).

[0037] Furthermore, if the applicable period of the range unit price master 106a spans multiple months, the discount amount may be created in a lump sum during the billing closing process for the month to which the end date of the applicable period belongs.

[0038] The master maintenance unit 102c performs settings such as inputting, adding, changing, and updating data to the range unit price master 106a and the price master 106b, for example, in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0039] The screen display control unit 102d controls the display of various screens (for example, various screens such as a master maintenance screen, a sales input screen, an invoice issuance screen, etc.) displayed on the monitor 114 and the reception of inputs.

[0040] [3. Specific Examples] 1 to 9B, a specific example of the processing of the sales processing device 100 in this embodiment will be described. Figures 4 to 9B are diagrams for explaining a specific example of the processing of the sales processing device 100 in this embodiment.

[0041] [3-1. Overall processing] 4 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the sales processing device 100 in this embodiment. With reference to FIG. 4, an outline of the overall processing of the control unit 102 of the sales processing device 100 in this embodiment will be described.

[0042] The master maintenance unit 102c executes a microwave unit price registration process (step S1). Specifically, in the microwave unit price registration process, the master maintenance unit 102c sets data in the microwave unit price master 106a in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0043] The sales input unit 102a executes a sales input process (step S2). Specifically, in the sales input process, the sales input unit 102a inputs sales data including a sales number, a sales date, a business partner, a product, a quantity, a unit price, and an amount in response to, for example, an operator's operation on a sales input screen (not shown) displayed on the monitor 114, and stores the data in the storage unit 106.

[0044] The billing processing unit 102b executes billing processing (step S3). Specifically, in the billing processing, the billing processing unit 102b executes billing processing on a monthly basis for the target business partner in response to, for example, an operator's operation on an invoice output screen (not shown) displayed on the monitor 114, and creates an invoice including a discount amount based on the sales data registered in the storage unit 106, stores it in the storage unit 106a, and also outputs (displays and prints out) it. Regarding the discount amount, if the quantity in the range unit price master 106a is greater than or equal to the total number of sales in the sales data, the discount amount is calculated as follows: Discount amount = total sales amount of the sales data - (total sales amount of the sales data x range unit price in the range unit price master 106a); if the quantity in the range unit price master 106a is less than the total number of sales in the sales data, the discount amount is calculated as follows: Discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master 106a is reached) - (quantity in the range unit price master 106a x range unit price in the range unit price master 106a).

[0045] [3-2. Sample Data] 5 to 9B are diagrams showing sample data for explaining a specific example of processing by the control unit 102 of the sales processing device 100 in this embodiment. A specific example of processing by the control unit 102 of the sales processing device 100 in this embodiment will be described with reference to FIGS. 5 to 9B. In the following example, a case will be described in which the master data examples in FIGS. 2 and 3 are used.

[0046] A specific example of S1: Range unit price registration processing will be described with reference to Figure 5. The master maintenance unit 102c sets data in the range unit price master 106a in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114. In the range unit price master 106a, the applicable period and range unit price are set for each customer, delivery destination, and product separately from the regular price master 106b.

[0047] FIG. 5A shows an example of data in the microwave unit price master 106a. The microwave unit price master 106a includes fields for customer, delivery destination, product, period, quantity, and microwave unit price. In the example shown in the figure, the first line contains the customer "XX Co., Ltd.", delivery destination "△△ construction," product "thinner," applicable period "1 / 1 to 1 / 31," quantity "50 cans," and microwave unit price "1,000 yen." The second line contains the customer "XX Co., Ltd.", delivery destination "△△ construction," product "thinner," period "2 / 1 to 2 / 29," quantity "40 cans," and microwave unit price "1,000 yen." XX Co., Ltd. is assumed to be a business partner that bills at the end of the month, and the application period of the microwave unit price master 106a is usually assumed to be set for a period (from the beginning to the end of the month) based on the closing date.

[0048] 5B is a diagram showing an example of data in the price master 106b. The price master 106b has fields for product and regular unit price. In the example shown in the figure, the product is "thinner" and the regular unit price is "1,100 yen."

[0049] In S2: Sales input process, daily sales data is entered, and in S3: Billing closing process, when calculating the billing amount (when creating an invoice, usually at the end of the month), the daily transactions (sales data) are compared with the range unit price master 106a, and for transactions up to the quantity registered in the range unit price master 106a, the difference between the normal price set in the price master 106b is automatically created as a discount slip. The created discount slip is written on the invoice. Figure 6 is a diagram for explaining the method for calculating the discount amount.

[0050] The discount amount is calculated as follows: (1) If the quantity of the range unit price master 106a is greater than or equal to the total sales quantity of the sales data, Discount amount = total sales amount of sales data - (total sales quantity of sales data x range unit price of range unit price master 106a) (2) If the quantity in the range unit price master 106a is less than the total number of sales in the sales data, the discount amount = the total sales amount in the sales data (*) - (the quantity in the range unit price master 106a x the range unit price in the range unit price master 106a) However, (※) the total amount is calculated from the most recent transaction date (starting from the oldest sales date) until the quantity in the range unit price master 106a is reached.

[0051] Below, we will explain S2: Sales input processing and S3: Billing closing processing in the following order: (1) normal pattern where discount occurs, (2) pattern where discount slip is not generated, and (3) pattern where discount occurs and range unit price period and billing period are different.

[0052] (1) Discount occurrence - normal pattern The discount occurrence / normal pattern will be described with reference to FIGS. 7A and 7B.

[0053] (S2: Sales input processing) A specific example of the sales input process will be described with reference to Fig. 7A. The sales input unit 102a inputs sales data including the sales number, sales date, customer, product, quantity, unit price, and amount in response to, for example, an operator's operation on a sales input screen (not shown) displayed on the monitor 114, and stores the data in the storage unit 106.

[0054] 7A(A) shows an example of data in microwave unit price master 106a. In the example shown in the figure, the first line has the customer "XX Co., Ltd.", delivery destination "△△ construction," product "thinner," applicable period "1 / 1 to 1 / 31," quantity "50 cans," and microwave unit price "1,000 yen." The second line has the customer "XX Co., Ltd.", delivery destination "XX residence construction," product "thinner," period "1 / 1 to 1 / 31," quantity "40 cans," and microwave unit price "1,000 yen."

[0055] 7A(B) shows an example of sales data. The sales data includes the following fields: sales number, sales date, category, customer, delivery destination, product, quantity, unit price (the normal unit price in price master 106b), and amount calculated by multiplying unit price by quantity. For ease of explanation, the sales data is marked with a number on the left.

[0056] In the example shown in the figure, the first line contains the sales number "U001," sales date "1 / 1," category "Sales," customer "XX Co., Ltd.", delivery destination "△△ Construction," product "Thinner," quantity "10 cans," unit price "1,100 yen," and amount "11,000 yen."

[0057] (S3: Billing process) A specific example of billing closing processing will be described with reference to Figures 7B and 7C. The billing closing processing unit 102b executes billing closing processing for the target business partner on a monthly basis in response to, for example, an operator's operation on an invoice output screen (not shown) displayed on the monitor 114, and creates an invoice including a discount amount based on the sales data registered in the storage unit 106, stores the invoice in the storage unit 106a, and also outputs (displays and prints). Figure 7B(C) shows an example of creating a discount slip using sales data.

[0058] In Figure 7B(C), the discount amount for January for the customer "XX Co., Ltd.", delivery destination "△△ Construction", and product "Thinner" is as follows:

[0059] For the period "1 / 1 to 1 / 31," the quantity in the microwave unit price master 106a "50 cans" < the total sales amount in the sales data "90 cans," so the discount amount = total sales amount in the sales data (total amount from the new number on the transaction date to the quantity "50 cans" in the microwave unit price master 106a) - (quantity in the microwave unit price master 106a × microwave unit price in the microwave unit price master 106a) = 11,000 + 22,000 + 11,000 + 11,000 - (50 × 1,000 yen)) = 55,000 - (50,000) = 5,000. As shown in No. 15 in Figure 7B(C), the following information is created for this discount slip: sales number "U100," sales date "1 / 31," category "discount," customer "XX Co., Ltd.", delivery destination "△△ Construction," product "thinner," quantity "50 cans," unit price "0 yen," and amount "-5,000 yen."

[0060] In Figure 7B(C), the discount amount for January for the customer "□□ Co., Ltd.", delivery destination "□□ Residence Construction," and product "Thinner" is as follows:

[0061] For the period "1 / 1 to 1 / 31," the quantity "40 cans" in the microwave unit price master 106a is greater than or equal to the total sales quantity in the sales data "30 cans," so the discount amount = total sales amount in the sales data - (total sales quantity in the sales data x microwave unit price in the microwave unit price master 106a) = 11,000 + 22,000 - (30 x 1,000 yen) = 33,000 - (30,000) = 3,000. As shown in No. 16 in Figure 7B(C), the discount slip created for this case contains the sales number "U200," sales date "1 / 31," category "Discount," customer "XX Co., Ltd.", delivery destination "XX Residence Construction," product "Thinner," quantity "30 cans," unit price "0 yen," and amount "-3,000 yen."

[0062] Figure 7C shows an image of the invoice that will be created. Figure 7C(A) shows an example of an invoice for customer "XX Co., Ltd.", and Figure 7C(B) shows an example of an invoice for customer "XX Co., Ltd." For the destination (customer), the invoice lists the items (columns) of sales date, product, quantity, sales price, and sales amount, as well as a sales slip row and a discount slip row (last row).

[0063] (2) Pattern where discount slips are not generated A case in which a discount slip is not generated will be explained with reference to Figure 8. Figure 8(A) is a diagram showing an example of data in the microwave unit price master 106a. In the example shown in the figure, the customer is "XX Co., Ltd.", the delivery destination is "YY Construction," the product is "Thinner," the applicable period is "2 / 1 to 2 / 29," the quantity is "40 cans," and the microwave unit price is "1,000 yen." Figure 8(B) shows an example of sales data.

[0064] In this example, we will explain the discount amount for February (2 / 1 to 2 / 29) for customer "XX Co., Ltd.", delivery destination "XX Construction," and product "thinner." As shown in Figure 8(C), for customer "XX Co., Ltd." and delivery destination "XX Construction," no discount slip is generated because customer "XX Co., Ltd.", delivery destination "XX Construction," and product "thinner" are not registered in microwave oven unit price master 106a shown in Figure 8(A).

[0065] (3) Discount occurrence / range unit price period and billing period are different 9A and 9B, a case where the discount occurrence / range unit price period and the billing period are different will be described. When the applicable period of the range unit price master 106a spans two months, a discount slip is created in the billing closing process for the month to which the end date of the applicable period belongs.

[0066] Figure 9(A) is a diagram showing an example of data in the microwave unit price master 106a. In the example shown in the figure, the customer is "XX Co., Ltd.", the delivery destination is "△△ Construction," the product is "Thinner," the period is "1 / 10 to 2 / 10," the quantity is "70 cans," and the microwave unit price is "900 yen." Figure 9A(B) shows an example of sales data.

[0067] 9B(C) is a diagram showing an example of a discount slip created using sales data. The billing closing process for January and February will be described.

[0068] (1) For the January billing closing process, the billing closing date is "1 / 31". It is checked whether there is a range unit price master 106a with a range unit price end date within the billing period (1 / 1-1 / 31) for the same customer, delivery destination, and product. In the range unit price master 106a in Figure 9(A), the customer "□□ Co., Ltd.", delivery destination "△△ Construction," and product "Thinner" do not exist because the period is "1 / 10-2 / 10," so a discount slip is not created. For the January billing processing range "1 / 1-1 / 31," billing processing is performed using a sales slip (No. 28 / 29 / 30 is the target).

[0069] (2) For the billing closing process for February, the billing closing date will be "2 / 28". Check whether there is a range unit price and period end date range unit price master for the same customer, delivery destination, and product within the billing period (2 / 1-2 / 28). In the range unit price master 106a of Figure 9(A), the customer "□□ Co., Ltd.", delivery destination "△△ Construction", and product "Thinner" are in the period "1 / 10-2 / 10", so a discount voucher is created as there is a value.

[0070] (2-1) For the February invoice processing range "2 / 1~2 / 28", invoice processing will be performed using sales slips (No. 31 / 32 / 33 / 34 will be the target).

[0071] (2-2) Check the sales slips for which discounts are to be calculated within the period "1 / 10~2 / 10" in the range unit price master 106a (No. 28 / 29 / 30 / 31 / 32 are the target). The discount amount is calculated as follows:

[0072] Since the quantity in the microwave unit price master 106a, "70 cans," < the total sales amount in the sales data, "110 cans," the discount amount = total sales amount in the sales data (total amount from the new number on the transaction date to the quantity in the microwave unit price master 106a) - (quantity in the microwave unit price master 106a x microwave unit price in the microwave unit price master 106a) = 11,000 + 22,000 + 11,000 + 11,000 + 22,000 yen + 11,000 - (70 x 900 yen) = 77,000 - (63,000) = 14,000. As shown in No. 35 in Figure 9B(C), the following information is created for this discount slip: sales number "U300," sales date "2 / 28," category "discount," customer "□□ Co., Ltd.", delivery destination "△△ Construction," product "thinner," quantity "70 cans," unit price "0 yen," and amount "-14,000 yen."

[0073] As described above, according to this embodiment, there are provided a range unit price master 106a in which business partners, products, applicable periods, quantities, and range unit prices, which are campaign unit prices, are registered in association with one another, a sales input unit 102a for inputting sales data including sales numbers, sales dates, business partners, products, quantities, unit prices, and amounts, and a billing and settlement process is executed monthly for the target business partners, an invoice including a discount amount is created based on the sales data, and the discount amount is calculated as follows: if the quantity in the range unit price master is equal to or greater than the total number of sales in the sales data, then the discount amount = total sales amount of the sales data - (sales amount of the sales data) and an invoice settlement processing unit 102b that calculates the discount amount = the sum of the sales amounts of the sales data (however, the sum of the amounts from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price in the range unit price master), and by setting the transaction volume for sales at campaign prices, it is possible to prevent certain business partners from buying up all the products and also to reduce the workload and mistakes involved in creating invoices.

[0074] [4. 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 the achievement of SDGs Goals 8 and 9.

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

[0076] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

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

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

[0079] Furthermore, 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 can be changed as desired unless otherwise specified.

[0080] Furthermore, with regard to the sales processing device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0081] For example, all or any part of the processing functions of the sales processing device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the sales processing device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0082] This computer program may also be stored in an application program server connected to the sales processing device 100 via any network, and all or part of it may be downloaded as needed.

[0083] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or 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.

[0084] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. 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, can use well-known configurations and procedures.

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

[0086] Sales processing 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 any peripheral device is connected. Sales processing device 100 may also be realized by installing software (including programs or data) that causes the device to perform the processing described in this embodiment.

[0087] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0088] 100 Sales Processing Device 102 Control section 102a Sales input section 102b Claims Processing Department 102c Master Maintenance Department 102d Screen display control unit 104 Communication interface unit 106 Storage section 106a Range unit price master 106b Price Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network

Claims

1. A sales processing device equipped with a control unit, The control unit It is configured to be accessible to the range unit price master, which associates and registers the range unit price, which is the customer, product, applicable period, quantity, and campaign unit price. a sales input means for inputting sales data including sales number, sales date, customer, product, quantity, unit price, and amount; an invoice closing processing means for executing monthly invoice closing processing for target business partners, creating invoices including discount amounts based on the sales data, and calculating the discount amount as follows: Discount amount = total sales amount of the sales data - (total sales amount of the sales data x range unit price of the range unit price master) if the quantity in the range unit price master is greater than or equal to the total sales number of the sales data, and Discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price of the range unit price master); A sales processing device comprising:

2. 2. The sales processing device according to claim 1, wherein the invoice contains the following items for the target business partner: sales date, product, quantity, sales price, sales amount, and a discount slip line.

3. The sales processing device described in claim 1 or 2, characterized in that when the application period of the range unit price master spans multiple months, the billing closing processing means calculates the discount amount in one billing closing process for the month to which the end date of the application period belongs.

4. 2. The sales processing device according to claim 1, wherein the business partners include customers and their delivery destinations.

5. A sales processing method executed by an information processing device having a control unit, The control unit It is configured to be accessible to the range unit price master, which associates and registers the range unit price, which is the customer, product, applicable period, quantity, and campaign unit price. Executed in the control unit: a sales input process for inputting sales data including sales number, sales date, customer, product, quantity, unit price, and amount; an invoice closing process for executing monthly invoice closing processing for target business partners, creating invoices including discount amounts based on the sales data, and calculating the discount amount as follows: Discount amount = total sales amount of the sales data - (total sales amount of the sales data x range unit price of the range unit price master) if the quantity in the range unit price master is greater than or equal to the total sales number of the sales data, and Discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price of the range unit price master); A sales processing method comprising:

6. A sales processing program to be executed by an information processing device having a control unit, The control unit It is configured to be accessible to the range unit price master, which associates and registers the range unit price, which is the customer, product, applicable period, quantity, and campaign unit price. The control unit a sales input process for inputting sales data including sales number, sales date, customer, product, quantity, unit price, and amount; an invoice closing process for executing monthly invoice closing processing for target business partners, creating invoices including discount amounts based on the sales data, and calculating the discount amount as follows: Discount amount = total sales amount of the sales data - (total sales amount of the sales data x range unit price of the range unit price master) if the quantity in the range unit price master is greater than or equal to the total sales number of the sales data, and Discount amount = total sales amount of the sales data (however, the total amount from the oldest sales date until the quantity in the range unit price master is reached) - (quantity in the range unit price master x range unit price of the range unit price master); A sales processing program to execute the above.

Images