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

Abstract

The objective is to provide a sales processing device, a sales processing method, and a sales processing program that can reduce the workload associated with campaign-related tasks. [Solution] The sales processing device according to this embodiment includes a master data set that associates campaigns, the application conditions for the campaigns, and the campaign amounts, and a sales import processing unit 102b that imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and identifies the applicable campaign and its campaign amount by referring to the master data for each invoice number in the sales import data.

Description

Technical Field

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

Background Art

[0002] For example, in a certain industry, there is a business of paying a campaign fee (rebate) to a reseller when the reseller sells a campaign-targeted product to an end user. The payment of the campaign fee is made upon application from the reseller. Conventionally, as a system for paying the campaign fee, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, conventionally, when there is an application for a campaign fee from a reseller, the correctness of whether the application is made for the correct campaign is checked by human judgment, so the checking work is very burdensome, which has been a problem.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a sales processing apparatus, a sales processing method, and a sales processing program capable of reducing the load of operations related to campaigns.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the present invention provides a sales processing device equipped with a control unit, wherein the control unit is configured to access a master in which campaigns, application conditions for the campaigns, and campaign amounts are registered in association with each other, and is equipped with sales import processing means that imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and identifies the applicable campaign and its campaign amount by referring to the master on an invoice number basis of the sales import data.

[0007] Furthermore, according to one aspect of the present invention, the master includes a campaign master in which campaigns and campaign amounts are registered in association, a campaign target variety master in which campaigns, rows, varieties, and campaign standard quantities are registered in association, and a product master in which products, varieties, and campaign standard quantities are registered in association, and the sales import processing means first refers to the product master on a per-transaction number basis of the sales import data to calculate the quantity of the product × campaign standard quantity, for the varieties associated with the product to identify campaigns in which the calculated quantity of the product × campaign standard quantity satisfies the campaign standard quantity, and for the identified campaigns to identify the campaign amount by referring to the campaign master.

[0008] Furthermore, according to one aspect of the present invention, the order data acquisition means may create sales data including the invoice number, sales date, customer, specified campaign, and specified campaign amount, and sales detail data including the invoice number, line, product, quantity, and amount, based on the sales acquisition data, and store them in the storage area.

[0009] Furthermore, according to one aspect of the present invention, the control unit may also include an inquiry means that, in response to an operator's operation on the inquiry screen, refers to the sales data and sales detail data stored in the storage area based on specified extraction conditions and displays rebate information comprising the items of invoice number, sales date, customer, applicable campaign, invoice sales amount, and campaign amount.

[0010] Furthermore, according to one aspect of the present invention, the control unit may further include payment processing means that creates payment data including the year and month, the customer (payee), and the amount, based on the sales data.

[0011] Furthermore, according to one aspect of the present invention, the control unit may further include journal entry creation means for creating journal entry data based on the payment data.

[0012] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides a sales processing method executed by an information processing device equipped with a control unit, wherein the control unit is configured to access a master in which campaigns, application conditions for the campaigns, and campaign amounts are registered in association, and the method includes a sales import processing step in which the control unit imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and refers to the master for each invoice number of the sales import data to identify the applicable campaign and its campaign amount.

[0013] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention is a sales processing program to be executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a master in which campaigns, the application conditions of the campaigns, and the campaign amounts are registered in association, and the sales processing program is characterized in that it causes the control unit to take in sales import data including slip number, customer, order date, line, product, quantity, unit price, and amount, and to refer to the master for each slip number of the sales import data to identify the applicable campaign and its campaign amount. [Effects of the Invention]

[0014] The present invention has the effect of reducing the workload associated with campaign-related tasks. [Brief explanation of the drawing]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of the sales processing apparatus according to the present embodiment. [Figure 2] FIG. 2 is a diagram showing a configuration example of a campaign master. [Figure 3] FIG. 3 is a diagram showing a configuration example of a campaign target item master. [Figure 4] FIG. 4 is a diagram showing a configuration example of an item master. [Figure 5] FIG. 5 is a diagram showing a configuration example of an expense item master. [Figure 6] FIG. 6 is a diagram showing a configuration example of a product master. [Figure 7] FIG. 7 is a diagram showing a configuration example of a journal definition master. [Figure 8] FIG. 8 is a diagram showing a flow for explaining an overview of the overall processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 13A] FIG. 13A is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 13B] FIG. 13B is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 13C] FIG. 13C is a diagram for explaining a specific example of the processing of the control unit of the sales processing apparatus according to the present embodiment. [Figure 13D]Figure 13D is a diagram illustrating a specific example of the processing performed by the control unit of the sales processing device in this embodiment. [Figure 13E] Figure 13E is a diagram illustrating a specific example of the processing performed by the control unit of the sales processing device in this embodiment. [Figure 13F] Figure 13F is a diagram illustrating a specific example of the processing performed by the control unit of the sales processing device in this embodiment. [Modes for carrying out the invention]

[0016] Embodiments of the sales processing apparatus, sales processing method, and sales processing program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

[0017] [1. Overview] The outline of this invention will be explained in the following order: [1-1. Background and Problems], and [1-2. Solution].

[0018] [1-1. Background / Issues] For example, in the gas industry, it is common to promote sales by running various campaigns for external retailers based on product combinations. In this case, there is a business of paying campaign fees (rebates) to external retailers when they sell the campaign-eligible products to end users. The payment of campaign fees is made upon application from the external retailer.

[0019] However, traditionally, when a sales agent applies for campaign funds, the accuracy of the application is checked manually to ensure it's for the correct campaign. This has resulted in a significant workload for the checking process. Consequently, the increasing variety and complexity of campaigns directly contributes to this increased workload and, consequently, to higher costs associated with sales promotion.

[0020] By reducing the workload of campaign operations, the costs associated with sales promotion can be lowered, allowing for a greater allocation of the promotional budget to end-users, which is expected to generate even greater sales promotion effects. Furthermore, the increased market availability of gas appliances is expected to boost gas demand and improve the profitability of the gas sales business, a separate segment. Therefore, promoting the sale of equipment in the energy industry is a very important measure.

[0021] [1-2. Solution] In this invention, the applicable conditions and campaign amount are registered for each campaign in a master database, and the campaign and campaign amount are automatically identified from sales information using this master database, thereby reducing the workload of the person in charge of campaign operations.

[0022] Specifically, the present invention has the following functions: (1) A function to manage the combinations and amounts of products eligible for the campaign in a master file. (2) A function to compare sales information submitted by external distributors (customers) with the master data and set up appropriate campaigns. (3) Function to refer to and output monthly campaign amounts for each external retailer.

[0023] In this specification, "product" shall be read as "product" or "service," and "customer" shall include outside retailers and sales agents. The present invention is widely applicable when applying campaigns to the sale (provision) of "products" or "services," and is widely applicable, for example, in the gas industry, automotive industry, carrier shop industry, insurance industry, etc.

[0024] The following example illustrates a case where a campaign is applied to the sale of gas-related products in the gas industry.

[0025] [3. Structure] The configuration of the sales processing device 100 according to this embodiment will be described with reference to Figure 1, etc. Figure 1 is a block diagram showing an example of the configuration of the sales processing device 100 according to this embodiment.

[0026] The sales processing device 100 is a commercially available desktop personal computer. However, the sales processing device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0027] As shown in Figure 1, the sales processing device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the sales processing device 100 is connected to communicate via any communication path.

[0028] The communication interface unit 104 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 the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the sales processing device 100 with the server 200 and customer (outside sales store) terminals 400, etc., so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106, which will be described later, may be stored in the server 200.

[0029] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 as the keyboard 112 or mouse 112. "Output" includes displaying on the monitor of the output device 114 and printing with the printer of the output device 114. Furthermore, user operations on information displayed on the monitor 114 using the input device 112, etc., may be referred to as "user operation via UI".

[0030] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0031] Furthermore, the storage unit 106 stores the campaign master 106a, the campaign target product master 106b, the product master 106c, the expense item master 106d, the product master 106e, the journal entry definition master 106f, the work table 106g, sales import data, sales data, sales detail data, payment data, journal entry data, etc. Figure 2 shows an example of the configuration of the campaign master 106a. Figure 3 shows an example of the configuration of the campaign target product master 106b. Figure 4 shows an example of the configuration of the product master 106c. Figure 5 shows an example of the configuration of the expense item master 106d. Figure 6 shows an example of the configuration of the product master 106e. Figure 7 shows an example of the configuration of the journal entry definition master 106f. The campaign master 106a, the campaign target product master 106b, and the product master 106e are collectively referred to as "masters" that associate and register campaigns, the application conditions of the campaign, and the campaign amount.

[0032] As shown in Figure 2, the campaign master 106a can consist of tables that associate and register campaigns (campaign code and / or campaign name), application start date, application end date, campaign amount, and expense item code. The campaign master 106a is used when identifying campaigns and campaign amounts in sales import data. In the example shown in the figure, the first row contains the campaign code "CAM001" and the campaign name "Floor heating installation promotion (15m 2 The above is the first line, with the start date being "2024 / 09 / 01", the end date being "2025 / 08 / 31", the campaign amount being "10,000", the expense code being "HMK001", the second line being the campaign code being "CAM002", and the campaign name being "Floor heating (10m 2 The above is a promotional offer for installing a stove set, with an application start date of "2024 / 09 / 01", an application end date of "2025 / 08 / 31", a campaign amount of "25,000", and an expense code of "HMK001".

[0033] The campaign target variety master 106b can consist of a table or the like that associates and registers campaigns (campaign code and / or campaign name), rows, varieties (variety code and / or variety name), and campaign base quantities, as shown in Figure 3. The campaign target variety master 106b is used when identifying campaigns and campaign amounts in sales import data. In the example shown in the figure, the first row is campaign code "CAM001", campaign row "1", variety code "YKD", and campaign base quantity "15", the second row is campaign code "CAM002", campaign row "1", variety code "YKD", and campaign base quantity "10", and the third row is campaign code "CAM002", campaign row "2", variety code "GAS", and campaign base quantity "1".

[0034] As shown in Figure 4, the variety master 106c can be composed of tables that associate and register variety codes and variety names. The variety master 106c is referenced by the control unit 102 when converting between variety codes and variety names. In the example shown in the figure, the first row contains the variety code "YKD" and the variety name "floor heating," and the second row contains the variety code "GAS" and the variety name "gas stove."

[0035] As shown in Figure 5, the expense item master 106d can be composed of a table or the like that registers expense item codes and expense item names in association. The expense item master 106d is referenced by the control unit 102 when converting expense item codes and expense item names. In the example shown in the figure, the first row contains the expense item code "HMK001" and the expense item name "Sales Promotion Expenses".

[0036] As shown in Figure 6, the product master 106e can consist of tables that associate and register products (product code and / or product name), varieties (variety code and / or variety name), and campaign threshold quantities. The product master 106e is used when identifying campaigns and campaign amounts in sales import data. Furthermore, the product master 106e is referenced by the control unit 102 when converting product codes and product names. In the example shown in the figure, the first row contains the product code "YKD001" and the product name "Floor heating 1m 2 The first line is "Panel", the variety code is "YKD", the campaign threshold is "1", and the second line is product code "YKD002", and product name "Floor heating 2m 2 The first line is labeled "Panel," with the product code "YKD," and the campaign threshold "2." The third line is labeled "GAS001," with the product name "Gas Stove," product code "GAS," and the campaign threshold "1."

[0037] As shown in Figure 7, the journal entry definition master 106f can be composed of tables that associate and register data types, debit accounts, and credit accounts. The journal entry definition master 106f is referenced when creating journal entry data. In the example shown in the figure, the data type is "Rebate Journal Entry", the debit account is "HMK001", and the credit account is "HMK101".

[0038] Worktable 106g is used by the control unit 102 as a work area and is for temporarily storing intermediate data. As will be described later, the sales import processing unit 102b uses worktable 106g to execute the applicable campaign determination logic.

[0039] Sales import data may include invoice number, sales date, customer (customer code and / or customer name), line, product (product code and / or product name), quantity, unit price, and amount.

[0040] Sales data may include invoice number, sales date, customer (customer code and / or customer name), applicable campaign code (applicable campaign code and / or applicable campaign name), and campaign amount.

[0041] Sales detail data may include invoice number, line number, product (product code and / or product name), quantity, unit price, and amount. Sales data and sales detail data are linked by invoice number.

[0042] Payment data may include the year and month, payee (payee code and / or payee name), amount, and expense item code.

[0043] Journal entry data may include the date of the transaction, the debit account (debit account code and / or debit account name), the debit amount, the credit account (credit account code and / or credit account name), and the credit amount.

[0044] The control unit 102 is a CPU or similar component that comprehensively controls the sales processing device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0045] The control unit 102 is configured to access the campaign master 106a, campaign target product master 106b, product master 106c, expense item master 106d, product master 106e, journal entry definition master 106f, work table 106g, sales import data, sales data, sales detail data, payment data, journal entry data, etc., which are stored in the storage unit 106. The campaign master 106a, campaign target product master 106b, product master 106c, expense item master 106d, product master 106e, journal entry definition master 106f, work table 106g, sales import data, sales data, sales detail data, payment data, journal entry data, etc. may be stored in another location (for example, server 200), as long as the control unit 102 can access them.

[0046] Functionally, the control unit 102 comprises a master maintenance unit 102a, a sales import processing unit 102b, an inquiry processing unit 102c, a rebate payment processing unit 102d, a rebate journal entry creation processing unit 102e, and a screen display control unit 102f.

[0047] The master maintenance unit 102a performs editing such as data input, addition, modification, and updating on the campaign master 106a, campaign target product master 106b, product master 106c, expense item master 106d, product master 106e, and journal entry definition master 106f, for example, in response to the operator's operations on the master maintenance screen (not shown) displayed on the monitor 114.

[0048] The sales import processing unit 102b imports sales data, including the invoice number, customer, order date, line, product, quantity, unit price, and amount, from the customer's terminal 400, for example. It then refers to the master data for each invoice number in the sales import data to identify the applicable campaign and its campaign amount.

[0049] Specifically, the sales import processing unit 102b first refers to the product master 106e for each transaction number of the sales import data, calculates the quantity of the product × the campaign standard quantity, then refers to the campaign target product master 106b for the product varieties associated with that product, identifies campaigns where the calculated quantity of the product × the campaign standard quantity satisfies the campaign standard quantity, and then refers to the campaign master 106a for the identified campaigns to determine the campaign amount.

[0050] The sales import processing unit 102b creates sales data including the invoice number, sales date, customer, specified campaign, and specified campaign amount, and sales detail data including the invoice number, line, product, quantity, and amount, based on the sales import data, and stores them in the storage unit 106.

[0051] In response to the operator's actions on the rebate result inquiry screen, the inquiry processing unit 102c refers to the sales data and sales detail data stored in the storage unit 106 based on the specified extraction conditions and displays rebate information that includes the following items: invoice number, sales date, customer, applicable campaign, invoice sales amount, and campaign amount.

[0052] The rebate payment processing unit 102d creates payment data, including the year and month, the customer (payee), and the amount, based on the sales data stored in the storage unit 106, and stores it in the storage unit 106.

[0053] The rebate journal entry creation processing unit 102e creates journal entry data based on the payment data stored in the storage unit 106, by referring to the journal entry definition master 106f, and stores it in the storage unit 106.

[0054] The screen display control unit 102f controls the display of various screens (for example, the master maintenance screen, the rebate result inquiry screen, etc.) on the monitor 114 and the acceptance of inputs on the screen.

[0055] [3. Specific Examples] A specific example of the processing performed by the control unit 102 of the sales processing device 100 according to this embodiment will be described with reference to Figures 1 to 13F.

[0056] [3-1. Overall Processing] Figure 8 is a flowchart illustrating the overall processing flow of the control unit 102 of the sales processing device 100. The overall processing flow of the control unit 102 of the sales processing device 100 will be explained with reference to Figure 8.

[0057] In Figure 8, the master maintenance unit 102a performs master maintenance processing (step S1). Specifically, in the master maintenance processing, the master maintenance unit 102a sets data for the campaign master 106a, campaign target product master 106b, product master 106e, etc., in response to the operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0058] The sales import processing unit 102b executes the sales import process (step S2). Specifically, in the sales import process, the sales import processing unit 102b imports sales import data, including the invoice number, customer, order date, line, product, quantity, unit price, and amount, from the customer's terminal 400, for example, and refers to the master for each invoice number of the sales import data to identify the applicable campaign and its campaign amount. More specifically, the sales import processing unit 102b first refers to the product master 106e for each invoice number of the sales import data to calculate the quantity of the product × the campaign base quantity, and for the product varieties associated with that product, refers to the campaign target product variety master 106b to identify campaigns where the calculated quantity of the product × the campaign base quantity satisfies the campaign base quantity, and for the identified campaigns, refers to the campaign master 106a to identify the campaign amount. Furthermore, the sales import processing unit 102b creates sales data including the invoice number, sales date, customer, specified campaign, and specified campaign amount, and sales detail data including the invoice number, line, product, quantity, and amount, based on the sales import data, and stores them in the storage unit 106.

[0059] The inquiry processing unit 102c executes the rebate result inquiry process (step S3). Specifically, in the rebate result inquiry process, the inquiry processing unit 102c, in response to the operator's operation on the rebate result inquiry screen, refers to the sales data and sales detail data stored in the storage unit 106 based on the specified extraction conditions and displays rebate information comprising the items of invoice number, sales date, customer, applicable campaign, invoice sales amount, and campaign amount.

[0060] The rebate payment processing unit 102d executes the rebate payment process (step S4). Specifically, in the rebate payment process, the rebate payment processing unit 102d creates payment data including the year and month, the customer (payee), and the amount, based on the sales data stored in the storage unit 106, and stores it in the storage unit 106.

[0061] The rebate journal entry creation processing unit 102e executes the rebate journal entry creation process (step S5). Specifically, in the rebate journal entry creation process, the rebate journal entry creation processing unit 102e creates journal entry data based on the payment data stored in the storage unit 106, by referring to the journal entry definition master 106f, and stores it in the storage unit 106.

[0062] [3-2. Sample Data] Referring to Figures 9 to 13F, a specific example of the processing performed by the control unit 102 of the sales processing device 100 will be explained. Figures 9 to 13F are diagrams illustrating a specific example of the processing performed by the control unit 102 of the sales processing device 100.

[0063] (S1: Master Maintenance Processing) A specific example of the master maintenance process will be explained with reference to Figure 9. The master maintenance unit 102a sets data for the campaign master 106a, campaign target product master 106b, product master 106e, etc., in response to the operator's operation on the master maintenance screen (not shown) displayed on the monitor 114.

[0064] Figure 9(A) shows an example of the settings for campaign master 106a, and Figure 9(B) shows an example of the settings for campaign target variety master 106b.

[0065] (S2: Sales import process) Referring to Figure 10, a specific example of the sales import process will be explained. The sales import processing unit 102b imports sales import data, including the invoice number, customer, order date, line, product, quantity, unit price, and amount, from the customer's terminal 400, for example. For each invoice number of the sales import data, it first refers to the product master 106e to calculate the quantity of the product × the campaign standard quantity. For the product varieties associated with the product, it refers to the campaign target product variety master 106b to identify campaigns where the calculated quantity of the product × the campaign standard quantity satisfies the campaign standard quantity. For the identified campaigns, it refers to the campaign master 106a to identify the campaign amount. The sales import processing unit 102b also creates sales data including the invoice number, sales date, customer, identified campaign, and identified campaign amount, and sales detail data including the invoice number, line, product, quantity, and amount, based on the sales import data, and stores them in the storage unit 106.

[0066] Figure 10(A) shows an example of sales import data. The sales import data may include invoice number, sales date, customer code, customer name, line, product code, quantity, unit price, and amount. In the example shown in the figure, the first line is: invoice number "URI001", sales date "2024 / 09 / 10", customer code "TOK001", customer name "Customer AAA", line 1, product code "YKD001", quantity "15", unit price "30,000", and amount "450,000".

[0067] For invoice number "URI001", floor heating 15m 2To satisfy the above conditions, we will use campaign code "CAM001". Specifically, for invoice number "URI001", the sales date is "2024 / 09 / 10", the product code is "YKD001", and the quantity is "15". Referring to product master 106e, the product code "YKD001" has a quantity of "15" × campaign base quantity "1" = 15, and the product code is "YKD". Therefore, it satisfies the campaign base quantity of "15" for product code "YKD" with campaign code "CAM001" in campaign target product master 106b, so we will use campaign code "CAM001" and obtain the campaign amount "10,000" from campaign master 106a. Note that the sales date "2024 / 09 / 10" satisfies the application period for campaign code "CAM001" in campaign master 106a.

[0068] Regarding invoice number "URI002", underfloor heating 10m 2 To meet the above conditions plus one gas stove, we will use campaign code "CAM002".

[0069] Regarding invoice number "URI003," although the combination of product varieties is correct, it will be excluded because the area for underfloor heating is insufficient.

[0070] For invoice number "URI004," since it satisfies the conditions of both CAM001 and CAM002, we will use the campaign code "CAM002," which has a higher value.

[0071] Figure 10(B) shows an example of sales data. Sales data may include invoice number, sales date, customer code, customer name, applicable campaign code, and campaign amount. In the example shown in the figure, the first row contains invoice number "URI001", sales date "2024 / 09 / 10", customer code "TOK001", customer name "Customer AAA", applicable campaign code "CAM001", and campaign amount "10,000". Figure 10(C) shows an example of sales detail data. Sales detail data may include invoice number, row, product code, quantity, unit price, and amount. In the example shown in the figure, the first row contains invoice number "URI001", row "1", product code "YKD001", quantity "15", unit price "30,000", and amount "450,000". The logic for determining applicable campaigns will be described later.

[0072] (S3: Rebate result inquiry process) A specific example of the rebate result inquiry process will be explained with reference to Figure 11. In response to the operator's operation on the rebate result inquiry screen, the inquiry processing unit 102c extracts sales data and sales detail data stored in the storage unit 106 that match the specified extraction conditions, and displays rebate information that includes the items of invoice number, sales date, customer, applicable campaign, invoice sales amount, and campaign amount.

[0073] Figure 11 shows an example of the display of the rebate result inquiry screen 500. The rebate result inquiry screen 500 includes a header area 501 for specifying the extraction conditions for the customer and target year and month, a display area 502 for displaying rebate information that matches the extraction conditions, and an "Display" button (not shown) for instructing the display.

[0074] The rebate information includes fields for invoice number, sales date, customer code, customer name, applicable campaign code, invoice sales amount, and campaign amount. When the "Display" button is pressed, the sales data and sales detail data stored in the storage unit 106 that match the extraction criteria are extracted, and the rebate information is displayed. In the example shown in the figure, since the extraction criteria for customer and target year and month are not specified (all specified), all sales data and sales detail data stored in the storage unit 106 are extracted, and the rebate information shown in Figure 11 is displayed in the display area 502. In the display area 502, the applicable campaign code, invoice sales amount, and campaign amount can be viewed at once for each invoice number.

[0075] (S4: Rebate payment processing) Refer to Figure 11 to explain a specific example of rebate payment processing. The rebate payment processing unit 102d creates payment data including the year and month, the customer (payee), and the amount based on sales data and stores it in the storage unit 106. In rebate payment processing, payment data for campaign funds is created for each customer based on sales data.

[0076] Figure 11 shows an example of payment data. The payment data may include the year and month, payee code, payee name, amount, and expense item code. In the example shown in the figure, the first row is "2024 / 09" year and month, payee code "TOK001", payee name "Customer AAA", amount "35,000", and expense item code "HMK001".

[0077] (S5: Rebate journal entry creation process) Refer to Figure 12 to explain a specific example of the rebate journal entry creation process. The rebate journal entry creation processing unit 102e creates journal entry data based on payment data by referring to the journal entry definition master 106f.

[0078] Figure 12 shows an example of journal entry data. Journal entry data may include the date of the transaction, debit account, debit account name, debit amount, credit account, debit account name, and debit amount. In the example shown in the figure, the first row is: transaction date "2024 / 09 / 30", debit account "HMK001", debit account name "Sales Promotion Expenses", debit amount "35,000", credit account "HMK101", debit account name "Accounts Payable", debit amount "35,000".

[0079] (Applicable campaign determination logic) The campaign application determination logic for the sales import process S2 described above will be explained with reference to Figures 13A to 13F. The sales import processing unit 102b uses the work table 106g to execute the following campaign application determination logic.

[0080] (1) Combine the necessary information (product master 106e) with the sales import data from the source. Figure 13A shows the combined information and includes the following fields: invoice number, sales date, customer code, customer name, line, product code, product type code (from product master 106e), quantity, and quantity × campaign base number (from product master 106e).

[0081] (2) Join the campaign target product master 106b with the matching details (if there are multiple matches, rows will be duplicated, but at this point they will be treated as a temporary table). Figure 13B shows the information obtained by combining the campaign target variety master 106b with the details that match the criteria. Rows that do not match the campaign are deleted at this point (e.g., row 1 of URI003).

[0082] (3) Loop through each invoice to determine if it covers all rows in the campaign target product master 106b. For each invoice number, determine whether it covers all rows of the applicable campaign code. Figure 13C shows the results of the assessment of applicability. The second row is deemed unsuitable because there is no row "2" for CAM002 in the campaign target variety master 106b, and the fifth row is deemed unsuitable because there is no row "1" for CAM002.

[0083] (4) Delete records that are not applicable. Figure 13D shows the result of deleting records that are not applicable.

[0084] (5) The total is calculated for each invoice number, and the campaign code with the highest amount is obtained (if multiple campaigns can be obtained for the same amount, the campaign code with the lowest value is used). Figure 13E(B) shows the results of aggregating the data for each invoice number and obtaining the campaign code that yields the highest amount.

[0085] (6) Combine the results so far with the sales data, update the campaign code applied to the sales data, and set the campaign amount. Figure 13F shows the results of applying Figure 13E(B) to the sales data.

[0086] As described above, according to this embodiment, a master data set is provided in which campaigns, the application conditions for the campaigns, and the campaign amounts are registered in association with each other. A sales import processing unit 102b is also provided, which imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and identifies the applicable campaign and its campaign amount by referring to the master data for each invoice number in the sales import data. Therefore, it is possible to reduce the workload related to campaigns.

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

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

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

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

[0091] 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 by known methods.

[0092] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0093] Furthermore, with respect to the sales processing device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0094] For example, the processing functions of the sales processing device 100, particularly those performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the sales processing device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) stores a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to form the control unit.

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

[0096] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0097] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0098] The various databases stored in the memory unit 106 include 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 website provision.

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

[0100] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Explanation of Symbols]

[0101] 100 Sales Processing Equipment 102 Control Unit 102a Master Maintenance Department 102b Sales Import Processing Unit 102c Inquiry Processing Unit 102d Rebate Payment Processing Unit 102e Rebate Journal Entry Creation Processing Unit 102f Screen Display Control Unit 104 Communication Interface Section 106 Storage section 106a Campaign Master 106b Campaign Target Variety Master 106c Variety Master 106d Expense Item Master 106e Product Master 106f Journal Entry Definition Master 106g Work Table 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks 400 devices

Claims

1. A sales processing device equipped with a control unit, The control unit, The system is configured to allow access to a master file that associates campaigns, their terms and conditions, and campaign amounts. A sales processing device characterized by comprising sales import processing means that imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and identifies the applicable campaign and its campaign amount by referring to the master data for each invoice number in the sales import data.

2. The aforementioned master is The campaign master, which is registered by associating the campaign and the campaign amount, A campaign-targeted variety master registered by associating campaigns, rows, varieties, and campaign standard quantities, A product master that associates products, varieties, and campaign thresholds, Includes, The sales import processing means, for each transaction number of the sales import data, first refers to the product master and calculates the quantity of the product × the campaign standard quantity, for the product varieties associated with the product, refers to the campaign target variety master and identifies campaigns where the calculated quantity of the product × the campaign standard quantity satisfies the campaign standard quantity, and for the identified campaigns, refers to the campaign master and identifies the campaign amount, as described in claim 1.

3. The sales processing device according to claim 1 or 2, characterized in that the sales import processing means creates and stores in a storage area sales data including slip number, sales date, customer, specified campaign, and specified campaign amount, and sales detail data including slip number, line, product, quantity, and amount, based on the sales import data.

4. The control unit further, The sales processing device according to claim 3, characterized in that, in response to an operator's operation on the inquiry screen, it refers to sales data and sales detail data stored in the storage area based on specified extraction conditions and displays rebate information comprising the items of invoice number, sales date, customer, applicable campaign, invoice sales amount, and campaign amount.

5. The control unit further, The sales processing apparatus according to claim 3, further comprising payment processing means for creating payment data including the year and month, the customer (payee), and the amount, based on the aforementioned sales data.

6. The control unit further, The sales processing device according to claim 5, further comprising a means for creating journal entries based on the aforementioned payment data.

7. A sales processing method performed by an information processing device equipped with a control unit, The control unit, The system is configured to allow access to a master file that associates campaigns, their terms and conditions, and campaign amounts. In the control unit, A sales processing method characterized by including a sales import processing step that imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and identifies the applicable campaign and its campaign amount by referring to the master data for each invoice number in the sales import data.

8. A sales processing program to be executed by an information processing device equipped with a control unit, The control unit, The system is configured to allow access to a master file that associates campaigns, their terms and conditions, and campaign amounts. The control unit, A sales processing program for executing a sales import processing step that imports sales import data including invoice number, customer, order date, line, product, quantity, unit price, and amount, and then, for each invoice number in the sales import data, refers to the master data to identify the applicable campaign and its campaign amount.

Images