Rebate management device, rebate management method, and rebate management program

The rebate management device automates rebate calculations using rebate and sales data to enhance accuracy and speed in recording rebate amounts, addressing inefficiencies and errors in existing systems.

JP7586791B2Active Publication Date: 2024-11-19OBIC CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021132601
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-08-17
Publication Date
2024-11-19
Estimated Expiration
2041-08-17

AI Technical Summary

Technical Problem

Existing rebate management systems in the food industry face significant challenges in accurately and efficiently calculating rebate amounts due to the need for manual data collection and calculation, leading to time-consuming processes and a high risk of errors.

Method used

A rebate management device and method that automates the calculation of rebate amounts by accessing rebate master data and sales data to determine rebate rates and amounts, allowing for quick and accurate recording of both expected and final rebate values, with features for temporary recording and offsetting of rebate amounts.

Benefits of technology

Enables faster and more accurate recording of rebate amounts, reducing manual errors and improving settlement efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586791000001
    Figure 0007586791000001
  • Figure 0007586791000002
    Figure 0007586791000002
  • Figure 0007586791000003
    Figure 0007586791000003
Patent Text Reader

Abstract

To provide a rebate management apparatus configured to calculate rebate amount more quickly and accurately, a rebate management method, and a rebate management program.SOLUTION: A control unit can access rebate master data with a method of calculating a rebate of a commodity set thereto. The control unit includes: an acquisition unit which acquires sales data including the amount of sales and a unit price of the commodity; a rebate management data generation unit which calculates a first rebate amount based on the sales data and the rebate master data, and generates rebate management data including the first rebate amount; and a red data generation unit which generates, on receipt of rebate bill data including a formal rebate amount from a rebate client, red data including a second rebate data for canceling the first rebate amount on the basis of the rebate management data.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] For example, in the food industry, rebates are recorded as expected amounts. There are many different methods for calculating rebates, and the formula or method of calculating rebates may differ for each customer.

[0003] Patent Document 1 discloses a configuration in which a rebate amount to a billing recipient is calculated based on sales data and unit price master and / or billing recipient master, and the rebate amount is recorded as a debt under the account heading of a deposit. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-109672 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the past, when recording rebate amounts as sales rebates by customer and product, it was necessary to gather sales data for the period and calculate the estimated (planned) amount and the official (confirmed) amount. This took a huge amount of time to calculate and there was a high possibility of operational errors.

[0006] The present invention has been made in consideration of the above problems, and aims to provide a rebate management device, a rebate management method, and a rebate management program that enable rebate amounts to be recorded more quickly and with greater accuracy. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the rebate management device of the present invention is a rebate management device equipped with a control unit, which is capable of accessing rebate master data in which a calculation method for a rebate for a product is set, and which is characterized in that the control unit is equipped with: an acquisition unit that acquires sales data including the sales quantity and unit price of the product; a rebate management data creation unit that calculates a first rebate amount based on the sales data and the rebate master data and creates rebate management data including the first rebate amount; and a red data creation unit that, when rebate claim data including a formal rebate amount is received from a rebate contract partner, creates red data including a second rebate amount that offsets the first rebate amount based on the rebate management data.

[0008] In addition, the rebate management device of the present invention is characterized in that the rebate master data includes a rebate rate determined for each customer and product, the sales data includes sales volume and unit price for each customer and product, and the rebate management data creation unit calculates the sales amount for each customer and product based on the sales data, and calculates the first rebate amount by multiplying the sales amount by the rebate rate.

[0009] In addition, the rebate management device of the present invention is characterized in that the rebate master data includes a rebate price determined for each customer and product, the sales data includes sales figures for each customer and product, and the rebate management data creation unit calculates the first rebate amount by multiplying the sales figures by the rebate price.

[0010] In addition, the rebate management device of the present invention is characterized in that the rebate management data includes a customer, a payee of the first rebate amount, and a rebate date of the first rebate amount, and the red data creation unit calculates a total value of the first rebate amount extracted from the rebate management data based on the customer, the payee, and the rebate date, and calculates the second rebate amount by inverting the sign of the total value.

[0011] In addition, the rebate management device according to the present invention is characterized in that it further includes an accounting unit that provisionally accounts for the first rebate amount under the account item of sales rebate before receiving the rebate claim data.

[0012] In addition, the rebate management device of the present invention is characterized in that, after receiving the rebate claim data, the accounting unit accounts for the second rebate amount and the official rebate amount under the account item of sales rebate, and creates payment schedule data including the official rebate amount.

[0013] In addition, the rebate management method of the present invention is characterized in that it is a rebate management device equipped with a control unit that can access rebate master data in which a calculation method for a product rebate is set, and includes the steps of acquiring sales data including the sales quantity and unit price of the product, calculating a first rebate amount based on the sales data and the rebate master data, and creating rebate management data including the first rebate amount, and when rebate claim data including the official rebate amount is received from a rebate contract partner, creating redemption data including a second rebate amount that offsets the first rebate amount based on the rebate management data.

[0014] In addition, the rebate management program of the present invention is characterized in that it causes a computer having a control unit that can access rebate master data in which a calculation method for a product rebate is set to execute the following steps: acquiring sales data including the sales quantity and unit price of the product; calculating a first rebate amount based on the sales data and the rebate master data and creating rebate management data including the first rebate amount; and, when rebate claim data including the official rebate amount is received from a rebate contract partner, creating redemption data including a second rebate amount that offsets the first rebate amount based on the rebate management data. Effect of the Invention

[0015] According to the present invention, it is possible to record the rebate amount more quickly and with higher accuracy. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 is a block diagram illustrating an example of a configuration of a rebate management device according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the rebate definition master according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of the rebate management master according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of sales data (for March) according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of sales data (for December) according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of rebate management data (projection) (for March) according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of rebate management data (projected) (for December) according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of creating red data of the rebate management data according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of rebate management data (formal) according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of payment schedule data according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0018] [1. Overview] First, an overview of the present invention will be described.

[0019] There are many ways to calculate rebates, but for example, if the period for calculating the rebate with a business partner is not a single month, it is necessary to record the estimated (planned) rebate amount. Specifically, if the rebate calculation is for an annual contract pattern or is not synchronized with the company's accounting month, it is necessary to record the estimated (planned) rebate amount. However, if it is synchronized with the company's accounting month, the official (confirmed) rebate amount will be calculated.

[0020] In the rebate management device of this embodiment, the accounting process for the estimated (planned) rebate amount is performed under the maximum conditions because the conditions differ depending on the achievement of the upper limit of the amount and the target number of items. The reason why it is necessary to account for the estimated (planned) rebate amount is that the accounting of sales would be excessive, so it is necessary to deduct the rebate (rebate) before reporting. After accounting for the estimated (planned) rebate (rebate), at the time of official (confirmed) accounting, it is necessary to reverse the estimated accounting and account for the official (confirmed) amount.

[0021] In this embodiment, the rebate management device makes it possible to calculate the estimated (planned) recorded data and the estimated (planned) red data by system calculation. Since the estimated (planned) recorded data and the estimated (planned) red data are the inversion of the amounts, the rebate management device of this embodiment performs automatic processing by focusing on this part.

[0022] According to the rebate management device of this embodiment described below, for example, it is possible to improve the accuracy of the rebate amount and speed up monthly settlement compared to when the rebate amount is manually calculated at the time of settlement.

[0023] [2. Configuration] An example of the configuration of the rebate management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the rebate management device 100.

[0024] The rebate management device 100 is a commercially available desktop personal computer. The rebate management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0025] The rebate management device 100 includes a storage unit 1, a control unit 2, a communication interface unit 3, and an input / output interface unit 4. Each unit included in the rebate management device 100 is connected to each other so as to be able to communicate with each other via an arbitrary communication path.

[0026] Data such as various databases, tables, and files are stored in the storage unit 1. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 1. 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 as the storage unit 1.

[0027] The storage unit 1 also stores a rebate definition master 1a, a rebate management master 1b, sales data 1c, rebate management data 1d, and payment schedule data 1e. The rebate definition master 1a and the rebate management master 1b will be described in detail. The sales data 1c, the rebate management data 1d, and the payment schedule data 1e will be described in detail later in the explanation of an example of the operation of the control unit 2.

[0028] 2 is a diagram showing an example of the rebate definition master 1a according to the embodiment. The rebate definition master 1a according to the embodiment includes a rebate definition number, a customer, a customer name, a product name, a classification, a calculation method, and a payment destination.

[0029] The rebate definition number is information that identifies the rebate definition. The customer is information that identifies the customer that is the subject of the rebate process. The customer name is the name of the customer that is the subject of the rebate process. The product is information that identifies the product that is the subject of the rebate process. The product name is the name of the product that is the subject of the rebate process. The classification indicates the classification of the rebate process (prospective (planned) or official (confirmed)).

[0030] The calculation method indicates the method for calculating the rebate. Specifically, the calculation method is the rebate rate and the rebate unit price. The rebate rate is a value multiplied by the sales amount for each customer and product. The rebate unit price is a value multiplied by the sales quantity.

[0031] The payee indicates the payee of the rebate amount.

[0032] FIG. 3 is a diagram showing an example of rebate management master 1b of an embodiment. Rebate management master 1b of an embodiment includes a rebate definition number, a rebate definition row number, a start date, an end date, a scheduled payment date, and a rebate. The rebate definition number is information that identifies a rebate definition. The rebate definition row number indicates the row number of the data indicating the rebate definition. The start date indicates the start date of application of the data indicating the rebate definition. The end date indicates the end date of application of the data indicating the rebate definition. The scheduled payment date indicates the scheduled payment date of the rebate amount. Rebate indicates the value of the calculation method of the rebate (the rebate rate in the example of FIG. 3).

[0033] Returning to Fig. 1, the control unit 2 is a CPU or the like that performs overall control of the rebate management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 2 includes a memory control unit 2a, a memory control unit 2b, an acquisition unit 2b, a rebate management data creation unit 2c, a red data creation unit 2d, and an accounting unit 2e.

[0034] The storage control unit 2a controls reading and writing of data stored in the storage unit 1.

[0035] The acquiring unit 2b acquires sales data 1c including the sales quantity and unit price of the product. For example, the acquiring unit 2b acquires the sales data 1c stored in the storage unit 1 via the storage control unit 2a. Also, for example, the acquiring unit 2b acquires the sales data 1c from another device connected to the network 200 via the communication interface unit 3.

[0036] FIG. 4 is a diagram showing an example of sales data 1c-1 (for March) according to an embodiment. Sales data 1c-1 according to an embodiment includes sales number, row, sales date, customer, product, sales quantity, unit price, and net sales amount. Sales number is information that identifies data indicating sales. Row indicates the row of data indicated by the sales number. Sales date indicates the date on which a sale was made. Customer indicates the customer who purchased the product. Product indicates the product for which a sale was made. Sales quantity indicates the number of products for which a sale was made. Unit price indicates the unit price of the product. Net sales amount indicates the sales amount (sales quantity x unit price).

[0037] 5 is a diagram showing an example of sales data 1c-2 (for December) according to an embodiment. The example of sales data 1c-2 (for December) according to an embodiment is similar to the example of sales data 1c-1 (for March) according to an embodiment, so a description thereof will be omitted.

[0038] Returning to Figure 1, the rebate management data creation unit 2c calculates a first rebate amount (estimated (planned) rebate amount) based on the sales data 1c and the rebate master data (rebate definition master 1a and rebate management master 1b), and creates rebate management data 1d including the first rebate amount.

[0039] 6 is a diagram showing an example of rebate management data 1d-1 (for March) according to an embodiment. Rebate management data 1d-1 according to an embodiment includes a rebate number, a row, a rebate category, a rebate date, a scheduled payment date, a payee, a rebate amount, a sales number, a row, and a red data creation category. The rebate number is information that identifies data indicating a rebate. The row indicates the row of data indicated by the rebate number.

[0040] The rebate category indicates the category of data indicating a rebate. The category of data indicating a rebate is set to "Estimated (planned)", "Estimated (planned) red", or "Official (confirmed)". "Estimated (planned)" indicates the estimated rebate amount. "Estimated (planned) red" indicates red data that offsets the estimated rebate amount. "Official (confirmed)" indicates the official rebate amount.

[0041] The rebate date is the date on which the data indicating the rebate specified by the rebate number was created. The scheduled payment date is the scheduled payment date of the rebate amount. The payee indicates the payee of the rebate amount.

[0042] The rebate amount is a rebate amount calculated by the rebate management data creation unit 2c. For example, the rebate management data creation unit 2c calculates the sales amount for each customer and product based on the sales data 1c, and calculates the rebate amount by multiplying the sales amount by the rebate rate. Also, for example, the rebate management data creation unit 2c calculates the rebate amount by multiplying the sales number by the rebate unit price.

[0043] In the example of Fig. 6, the rebate amount of 2,400 specified by rebate number WM0301 is calculated by multiplying the net sales amount of 200,000 specified by sales number UR0301 (see Fig. 4) by the rebate rate of 1.2%. Similarly, the rebate amount of 4,800 specified by rebate number WM0302 is calculated by multiplying the net sales amount of 400,000 specified by sales number UR0302 (see Fig. 4) by the rebate rate of 1.2%.

[0044] The sales number is information that identifies data indicating sales. The row indicates the row of data indicating sales identified by the sales number. The red data creation category indicates whether or not red data has been created. In the example of Figure 6, if red data corresponding to the expected (planned) rebate amount has not been created, the red data creation category is not set (left blank).

[0045] The rebate management data creation unit 2c refers to the rebate management master 1b and executes the rebate calculation process, for example, on a daily basis, so that the expected (planned) rebate amount can be automatically calculated by day, customer, and product, as shown in the example of Figure 6.

[0046] 7 is a diagram showing an example of rebate management data 1d-2 (for December) according to an embodiment. The example of rebate management data 1d-2 (for December) according to an embodiment is similar to the example of rebate management data 1d-1 (for March) according to an embodiment, so a description thereof will be omitted.

[0047] In the monthly settlement, the accounting unit 2e provisionally accounts for the "estimated (planned)" rebate amount, for example, as follows. This allows the accounting entry to be made in the March settlement as an estimated (planned) rebate amount. Example: Accounts receivable 600,000 / Sales 600,000 Sales (rebate) 7,200 / Accounts payable 7,200

[0048] When a rebate occurs after April, the processing of the rebate management data creation unit 2c and the recording unit 2e is the same as that for March.

[0049] Returning to Fig. 1, when the red data creation unit 2d receives rebate request data (rebate invoice) including the official rebate amount from the customer (rebate contract partner), it creates red data including a second rebate amount that offsets the first rebate amount (estimated (planned) rebate amount) based on the rebate management data 1d. Then, at the timing when the "official (confirmed)" rebate amount is determined, the accounting unit 2e accounts for the "estimated (planned) red" rebate amount against the "estimated (planned)" rebate amount that occurred previously.

[0050] 8 is a diagram showing an example of creating red data of the rebate management data 1d-3 of the embodiment. The official rebate amount is determined by receiving the rebate claim data from the rebate contracting party. The red data creating unit 2d creates the estimated (planned) red data at this timing and offsets the estimated (planned) data that was provisionally recorded.

[0051] Since the estimated (planned) red data targets data with "rebate category: estimated (planned)" and "red data creation category: not created", a system is in place to prevent duplicate red data from being created. In addition, it is possible to specify the customer, payee, rebate date, etc. as extraction conditions for creating red data. Specifically, the red data creation unit 2d calculates the total value of the "estimated (planned)" rebate amount extracted from the rebate management data 1d based on the customer, payee, and rebate date, and calculates the "estimated (planned) red" rebate amount by inverting the sign of the total value.

[0052] In the example of Figure 8, the red data creation unit 2d creates red data (rebate management data 1d-3) including a rebate amount that offsets the expected (planned) rebate amount from rebate management data 1d-1 including the expected (planned) rebate amount for March and rebate management data 1d-2 including the expected (planned) rebate amount for December.

[0053] Fig. 9 is a diagram showing an example of rebate management data 1d-4 (official) according to an embodiment. In the example of Fig. 9, when the rebate management data creation unit 2c receives rebate claim data including the official rebate amount (¥25,000), it creates rebate management data 1d-4 including the "official (confirmed)" rebate amount. This allows the official rebate amount along with the upper limit to be registered.

[0054] Next, the accounting unit 2e accounts for the rebate amount that offsets the estimated (planned) rebate amount and the official rebate amount under the account heading of "sales rebate," for example, as follows: Example: Sales (rebate) -24,000 / Accounts payable -24,000 Sales (rebate) 25,000 / Accounts payable -24,000

[0055] In addition, the accounting unit 2e creates payment schedule data (payment schedule slip) including the official rebate amount.

[0056] FIG. 10 is a diagram showing an example of payment schedule data 1e according to an embodiment. The payment schedule data 1e according to an embodiment includes an expense payment schedule number, a row, an accounting date, a scheduled payment date, a payee, and a scheduled payment amount. The expense payment schedule number is information that identifies data indicating expenses to be paid. The row indicates a row of data indicating expenses to be paid. The accounting date indicates the date on which the scheduled payment amount is accounted. The scheduled payment date indicates the scheduled payment date of the scheduled payment amount. The payee indicates the payee of the scheduled payment amount. The scheduled payment amount indicates the amount of the debt to the payee.

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

[0058] An input device 110 and an output device 120 are connected to the input / output interface unit 4. The input device 110 may be a keyboard, a mouse, a microphone, or a monitor (including a touch panel) that cooperates with the mouse to realize a pointing device function. The output device 120 may be a monitor (including a touch panel), or a speaker or a printer. For example, the processing results of the control unit 2 are output to the output device 120.

[0059] As described above, in the rebate management device 100 of the embodiment, the control unit 2 can access rebate master data (rebate definition master 1a and rebate management master 1b in the example of FIG. 1) in which a calculation method for a rebate for a product is set. The acquisition unit 2b acquires sales data 1c including the sales quantity and unit price of the product. The rebate management data creation unit 2c calculates a first rebate amount based on the sales data 1c and the rebate master data, and creates rebate management data 1d including the first rebate amount. Then, when the red data creation unit 2d receives rebate claim data including the official rebate amount from the rebate contracting party, it creates red data including a second rebate amount that offsets the first rebate amount based on the rebate management data 1d.

[0060] As a result, according to the rebate management device 100 of the embodiment, it is possible to record the rebate amount (rebate amount) more quickly and with higher accuracy.

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

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

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

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

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

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

[0067] Moreover, with regard to the rebate management device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0068] For example, the processing functions of the rebate management device 100, particularly the processing functions performed by the control unit 2, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the rebate management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0069] In addition, this computer program may be stored in an application program server connected to the rebate management device 100 via any network, and it is also possible to download all or a part of it as necessary.

[0070] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "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.

[0071] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a configuration that is distributed as a plurality of modules or libraries, and a program 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 this embodiment, as well as the installation procedure after reading, may use well-known configurations and procedures.

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

[0073] The rebate management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The rebate management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0074] 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 functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0075] The present invention is useful in food businesses and the like in which rebate amounts are irregularly calculated. [Explanation of symbols]

[0076] 100 Rebate Management Device 1 Storage section 1a Rebate definition master 1b Rebate Management Master 1c Sales Data 1d Rebate Management Data 1e Payment schedule data 2. Control section 2a Memory control unit 2b Acquisition part 2c Rebate Management Data Creation Department 2d Red Data Creation Department 2e Accounting Department 3. Communication Interface Section 4 Input / Output Interface Section 110 Input Device 120 Output Device 200 Network

Claims

1. A rebate management device including a control unit, The control unit is You have access to rebate master data that defines how rebates are calculated for products, The control unit is An acquisition unit that acquires sales data including the sales quantity and unit price of the product; a rebate management data creation unit that calculates a first rebate amount based on the sales data and the rebate master data and creates rebate management data including the first rebate amount; a red-back data creation unit that creates red-back data including a second rebate amount that offsets the first rebate amount based on the rebate management data when rebate claim data including a formal rebate amount is received from the rebate contracting party; A rebate management device comprising:

2. The rebate master data includes a rebate rate determined for each customer and each product, The sales data includes sales volume and unit price for each of the customers and each of the products, The rebate management device according to claim 1, characterized in that the rebate management data creation unit calculates the sales amount for each customer and product based on the sales data, and calculates the first rebate amount by multiplying the sales amount by the rebate rate.

3. The rebate master data includes a rebate unit price determined for each customer and each product, The sales data includes sales figures for each of the customers and each of the products, 2. The rebate management device according to claim 1, wherein the rebate management data creation unit calculates the first rebate amount by multiplying the sales volume by the rebate unit price.

4. the rebate management data includes a customer, a payee of the first rebate amount, and a rebate date of the first rebate amount; The rebate management device described in any one of claims 1 to 3, characterized in that the red data creation unit calculates the sum of the first rebate amounts extracted from the rebate management data based on the customer, the payee, and the rebate date, and calculates the second rebate amount by inverting the sign of the sum.

5. an accounting unit that provisionally accounts for the first rebate amount under the account heading of sales rebate before receiving the rebate claim data; The rebate management device according to any one of claims 1 to 4, further comprising:

6. The rebate management device of claim 5, characterized in that after receiving the rebate claim data, the accounting unit accounts for the second rebate amount and the official rebate amount under the account heading of sales rebate, and creates payment schedule data including the official rebate amount.

7. A rebate management method comprising a control unit capable of accessing rebate master data in which a calculation method for a rebate of a product is set, acquiring sales data including the sales quantity and unit price of the product; calculating a first rebate amount based on the sales data and the rebate master data, and creating rebate management data including the first rebate amount; A step of creating redemption data including a second rebate amount offsetting the first rebate amount based on the rebate management data when rebate claim data including a formal rebate amount is received from the rebate contracting party; A rebate management method comprising:

8. A computer having a control unit capable of accessing rebate master data in which a calculation method for a rebate of a product is set, acquiring sales data including the sales quantity and unit price of the product; calculating a first rebate amount based on the sales data and the rebate master data, and creating rebate management data including the first rebate amount; A step of creating redemption data including a second rebate amount offsetting the first rebate amount based on the rebate management data when rebate claim data including a formal rebate amount is received from the rebate contracting party; Rebate management program to implement.

Citation Information

Patent Citations

  • Purchase rebate management system and sales rebate management system

    JP2005063378A

  • Method for rearranging and adjusting financial statement in financial accounting system

    JP2005099904A

  • Rebate management system and rebate management program

    JP2005250719A

  • Accounting processing device, accounting processing method, and accounting processing program

    JP2018005519A

  • Rebate management device and rebate management method and rebate management program

    JP2019109672A