Storage fee management apparatus, storage fee management method, and storage fee management program

Abstract

To provide a storage fee management apparatus capable of accurately calculating a warehouse storage fee when a collection deadline has passed with a low workload.SOLUTION: A storage fee management apparatus according to an embodiment comprises: contract input means for accepting input of contract data that includes a contract number, a customer, a collection deadline, a storage fee calculation method, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount; and sales input means for accepting input of sales data that includes a storage fee surcharge unit price, a sales unit price, and a sales amount, wherein the storage fee surcharge unit price is calculated, based on the contract data, using a sales number, the contract number, the customer, a delivery date, the product, and sales quantity, and the storage fee unit price×the amount of storage period exceeded (provided that the amount of storage period exceeded is calculated based on the collection deadline and the delivery date), wherein the sales unit price is calculated by the contract unit price+the storage fee surcharge unit price, wherein the sales amount is calculated by the sales quantity×the sales unit price.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] For example, there is a case where products to be delivered to a customer are stored in a consignment warehouse. Conventionally, a system for calculating warehouse storage fees is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-101278 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the past, warehouse storage fees when the collection deadline was exceeded had to be calculated manually by the person in charge, which resulted in a heavy workload and the risk of calculation errors.

[0005] The present invention has been made in consideration of the above, and aims to provide a storage fee management device, a storage fee management method, and a storage fee management program that can accurately calculate warehouse storage fees when the collection deadline has passed with low workload. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a storage fee management device equipped with a control unit for managing storage fees when storing products to be delivered to customers in a warehouse, wherein the control unit includes a contract input means for inputting contract data including a contract number, a customer, a collection deadline, a storage fee calculation period, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount, and a storage fee calculation means for calculating, based on the contract data, the order number, the contract number, the customer, a scheduled delivery date, a product, an order quantity, the storage fee unit price, and the storage fee unit price multiplied by the storage period overrun (where the storage period overrun is calculated based on the collection deadline and the scheduled delivery date). The system is characterized by comprising an order input means for creating order data including the insurance premium surcharge unit price, the order unit price calculated by the contract unit price + the storage fee surcharge unit price, and the order amount calculated by the order quantity x the order unit price; and a sales input means for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, the storage fee surcharge unit price calculated by the storage fee surcharge unit price x the amount over the storage period (however, the amount over the storage period is calculated based on the collection deadline and delivery date), the sales unit price calculated by the contract unit price + the storage fee surcharge unit price, and the sales amount calculated by the sales quantity x the sales unit price.

[0007] According to one aspect of the present invention, the contract data includes a storage fee calculation period classification, and the storage period exceeding the storage period is the number of excess periods. The scheduled delivery date and the delivery date are set as the standard delivery date, and an excess check is performed in the month in which delivery ends. If the standard delivery date is greater than the collection deadline for the contract data, the number of excess periods is calculated. The number of excess periods for a month or more is calculated by multiplying the storage fee calculation period classification of the contract data by (the month before the standard delivery date - the month of the collection deadline for the contract data) by the storage fee calculation period classification of the contract data. The number of excess periods for a month or less is calculated based on the standard delivery date in accordance with the storage fee calculation period classification of the contract data, and the number of excess periods is calculated by adding the number of excess periods for a month or more to the number of excess periods for a month or less.

[0008] Furthermore, according to one aspect of the present invention, the number of excess periods of less than one month may be set to "1" if the storage fee calculation period classification of the contract data is a one-period system; if the storage fee calculation period classification of the contract data is a two-period system, the number of excess periods may be set to "1" if the standard delivery date is "1 to 15," and "2" if the standard delivery date is "other than 1 to 15"; if the storage fee calculation period classification of the contract data is a three-period system, the number of excess periods may be set to "1" if the standard delivery date is "1 to 10," the number of excess periods may be set to "2" if the standard delivery date is "11 to 20," and "3" if the standard delivery date is other than "1 to 20."

[0009] According to another aspect of the present invention, the warehouse may include a consignment warehouse.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention provides a storage fee management method executed by an information processing device having a control unit, the method including a contract input process executed by the control unit to input contract data including a contract number, a customer, a collection deadline, a storage fee calculation period, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount; and an insurance premium to be paid calculated based on the contract data using the order number, the contract number, the customer, a scheduled delivery date, the product, the order quantity, the storage fee unit price to be paid x the storage period overrun (where the storage period overrun is calculated based on the collection deadline and the scheduled delivery date). The method is characterized by including an order input process for creating order data including the additional unit price, the order unit price calculated by the contract unit price + the surcharge unit price for storage charges, and the order amount calculated by the order quantity x the order unit price; and a sales input process for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, the surcharge unit price for storage charges calculated by the surcharge unit price for storage charges x the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and delivery date), the sales unit price calculated by the contract unit price + the surcharge unit price for storage charges, and the sales amount calculated by the sales quantity x the sales unit price.

[0011] In order to solve the above-mentioned problems and achieve the object, the present invention provides a storage fee management program to be executed by an information processing device having a control unit, the program comprising: a contract input step of inputting into the control unit contract data including a contract number, a customer, a collection deadline, a storage fee calculation period, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount; and a contract input step of inputting into the control unit contract data including an order number, a contract number, a customer, a scheduled delivery date, a product, an order quantity, a storage fee unit price to be paid multiplied by the storage period overrun amount (where the storage period overrun amount is calculated based on the collection deadline and the scheduled delivery date), a storage fee surcharge unit price to be paid, and a contract unit price to be paid based on the contract data. and a sales input process for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, the surcharge unit price calculated by the surcharge unit price x the storage period (however, the surcharge unit price is calculated based on the collection deadline and delivery date), the sales unit price calculated by the contract unit price + the surcharge unit price, and the sales amount calculated by the sales quantity x the sales unit price. [Effects of the Invention]

[0012] According to the present invention, it is possible to accurately calculate warehouse storage fees when the collection deadline has passed, with a low workload. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram for explaining the processing image of the present invention. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the storage fee management device according to this embodiment. [Figure 3] FIG. 3 is a diagram showing a flow for explaining an outline of the overall operation of the control unit of the storage fee management device according to this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the storage fee management device according to the present embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the storage fee management device according to the present embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the storage fee management device according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the storage fee management device according to the present 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 this embodiment.

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

[0016] [1-1. Issues / Background] In the food industry, it is rare for a company to have its own warehouse, and it is common for goods to be stored in a consignment warehouse. In such cases, storage fees are incurred depending on the storage period. Generally, delivery within the collection deadline is the company's responsibility, but in many cases, contracts with customers (business partners) stipulate that the customer will be responsible for the storage fees at the consignment warehouse when the collection deadline is exceeded. Storage fees when the collection deadline is exceeded are calculated using a formula stipulated in the contract. This storage fee when the collection deadline is exceeded is a deemed amount that is separate from the actual storage fee that is incurred.

[0017] However, in the past, warehouse storage fees when the collection deadline was exceeded had to be calculated manually by the person in charge, which resulted in a heavy workload and the risk of calculation errors.

[0018] [1-2. Solution] In order to solve the above problem, the present invention provides a mechanism for calculating the storage fee (unit price) to be paid by the customer based on the contract details and the actual delivery date at the time of sales processing, and adding this to the unit price at the time of contract.

[0019] [1-3.Effects] According to the present invention, it is possible to (1) improve operational efficiency and (2) accurately charge the amount of storage fees when the collection deadline is exceeded.

[0020] (1) Business efficiency In the past, there were cases where the delivery date for one contract was divided into multiple times, or the delivery date changed, and manual calculations had to be made each time. In contrast, this invention has a system that calculates the customer's storage fees when calculation elements (such as delivery date) are newly entered or modified during system processing, thereby reducing the workload of the sales department.

[0021] (2) Claiming the exact amount In the past, it was necessary to calculate the storage fee to be paid by the customer based on multiple calculation elements such as the contract details and the actual delivery date. In contrast, this invention has a rule-based calculation system that makes it possible to bill the customer for the correct amount.

[0022] [1-4. Processing image] FIG. 1 is a diagram for explaining the processing image of the present invention. The company to which the storage fee management device of the present invention is applied is assumed to be the company itself. In FIG. 1, the company stores products to be delivered to customers in a consignment warehouse. The company sets a collection deadline in the contract with the customer (for example, collection deadline: end of January). If the customer's collection date (delivery date) (for example, February 6th) exceeds the collection deadline, the company will charge an amount that takes into account the excess storage fee in accordance with the contract with the customer.

[0023] In this invention, if the storage fee exceeds the contract that a company has concluded with a customer at the time of sale, the consignment warehouse will charge the excess storage fee. Previously, a company would add the storage fee charged by the consignment warehouse to the sales amount and charge the customer, but because the excess storage fee was calculated manually, calculation errors and invoice omissions led to inaccurate invoices. In this invention, the sales amount is automatically calculated, taking into account the storage fee amount based on the delivery date and the number of days beyond the collection deadline specified in the contract. Because the excess storage fee to be charged is calculated by the system, the amount can be calculated correctly based on the number of days of excess storage.

[0024] The present invention can be suitably applied to, for example, trading companies that use consignment warehouses.

[0025] [2. Configuration] An example of the configuration of the storage fee management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the storage fee management device 100. The storage fee management device 100 can be suitably used, for example, in a company that sells merchandise stored in a consignment warehouse to customers.

[0026] The storage fee management device 100 is a commercially available desktop personal computer. Note that the storage fee management 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.

[0027] The storage fee management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit included in the storage fee management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

[0028] The communication interface unit 104 communicatively connects the storage fee management 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 communicatively connecting the storage fee management device 100 and the server 200, and is, for example, the Internet or a LAN (Local Area Network).

[0029] 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 touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Furthermore, "output" refers to outputting by the output device 114, and includes, for example, display output to the monitor 114, print output by the printer 114, and sending data to the outside.

[0030] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes. 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, or an optical disk. The storage unit 106 also stores contract data, order data, sales data, etc.

[0031] The contract data is an agreement between a customer and the warehouse on how to handle goods that are stored in the warehouse after the deadline for collection, and may include the contract number, customer, collection deadline, storage fee calculation period, storage fee unit price, product, contract quantity, contract unit price, and contract amount.

[0032] The order data may include an order number, a contract number, a customer, a scheduled delivery date, a product, an order quantity, a burden unit price surcharge unit price, an order unit price, and an order amount.

[0033] The sales data may include sales number, contract number, customer, delivery date, product, sales quantity, burden unit price surcharge unit price, sales unit price, and sales amount.

[0034] The control unit 102 is a CPU or the like that comprehensively controls the storage fee 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, required data, etc., and executes various information processing based on these stored programs.

[0035] The control unit 102 stores contract data, order data, sales data, etc. in the storage unit 106. The contract data, order data, sales data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 can access them.

[0036] The control unit 102 conceptually includes a contract input unit 102a, an order input unit 102b, a sales input unit 102c, a screen display control unit 102e, and a billing processing unit (not shown).

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

[0038] For example, in response to an operator's operation on an order input screen (not shown) displayed on the monitor 114, the order input unit 102b inputs order data based on the contract data registered in the memory unit 106, including the order number, contract number, customer, scheduled delivery date, product, order quantity, insurance premium surcharge unit price calculated by multiplying the storage fee unit price by the excess storage period (however, the excess storage period is calculated based on the collection deadline and the scheduled delivery date), the order unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and the order amount calculated by multiplying the order quantity by the order unit price, and stores the data in the memory unit 106.

[0039] For example, in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, the sales input unit 102c inputs sales data based on the contract data registered in the storage unit 106, including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee additional unit price calculated by multiplying the storage period by the storage fee unit price (however, the storage period excess is calculated based on the collection deadline and delivery date), sales unit price calculated by adding the contract unit price to the storage fee additional unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price, and stores the data in the storage unit 106. The billing processing unit creates billing data based on the sales data and sends it to the customer.

[0040] In this case, the contract data may further include a storage fee calculation period classification, and the storage period exceeding the period may be counted as the number of excess periods, with the scheduled delivery date and delivery date being used as the standard delivery date, an excess check being performed in the month in which delivery is completed, and the number of excess periods being calculated if the standard delivery date is greater than the collection deadline for the contract data, with the number of excess periods of one month or more being calculated as (the month before the standard delivery date - the month of the collection deadline for the contract data) x the storage fee calculation period classification for the contract data, and the number of excess periods of less than one month being calculated based on the standard delivery date in accordance with the storage fee calculation period classification for the contract data, and the number of excess periods being calculated as the number of excess periods of one month or more + the number of excess periods of less than one month.

[0041] In addition, the number of excess periods of less than one month may be set as follows: if the contract data storage fee calculation period classification = 1 period, the number of excess periods may be "1", if the contract data storage fee calculation period classification = 2 periods, the number of excess periods may be "1" if the standard delivery date is "1 to 15", and "2" if the standard delivery date is "other than 1 to 15", and if the contract data storage fee calculation period classification = 3 periods, the number of excess periods may be "1" if the standard delivery date is "1 to 10", the number of excess periods may be "2" if the standard delivery date is "11 to 20", and "3" if the standard delivery date is other than "1 to 20".

[0042] The screen display control unit 102d controls the display of various screens (for example, a contract input screen, an order input screen, a sales input screen, etc.) displayed on the monitor 114 and the input thereto.

[0043] [3. Specific Examples] 1 to 7, a specific example of the processing of the control unit 102 of the storage fee management device 100 in this embodiment will be described. Fig. 3 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the storage fee management device 100 in this embodiment.

[0044] [3-1. Overall processing] With reference to FIG. 3, an outline of the overall processing of the control unit 102 of the storage fee management device 100 in this embodiment will be described.

[0045] The contract input unit 102a executes a contract input process (step S1). Specifically, in the contract input process, the contract input unit 102a inputs contract data including a contract number, a customer, a collection deadline, a storage fee unit price to be borne, a product, a contract quantity, a contract unit price, and a contract amount in response to an operator's operation on a contract input screen (not shown) displayed on the monitor 114, and stores the data in the storage unit 106.

[0046] The order input unit 102b executes order input processing (step S2). Specifically, in the order input processing, the order input unit 102b inputs order data including the order number, contract number, customer, scheduled delivery date, product, order quantity, insurance premium surcharge unit price calculated by multiplying the storage fee unit price by the excess amount of the storage period (however, the excess amount of the storage period is calculated based on the collection deadline and the scheduled delivery date), the order unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and the order amount calculated by multiplying the order quantity by the order unit price, based on the contract data registered in the storage unit 106, in response to, for example, an operation by the operator on an order input screen (not shown) displayed on the monitor 114, and stores the input data in the storage unit 106.

[0047] The sales input unit 102c executes a sales input process (step S3). Specifically, in the sales input process, the sales input unit 102c inputs sales data including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee additional unit price calculated by multiplying the storage fee unit price by the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and the delivery date), sales unit price calculated by adding the contract unit price to the storage fee additional unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price, 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.

[0048] The amount of storage time that exceeds the order entry processing and sales entry processing may be counted as the number of excess periods, with the scheduled delivery date and delivery date being used as the standard delivery date, an excess check being performed in the month in which delivery is completed, and the number of excess periods being calculated if the standard delivery date is greater than the deadline for collection of the contract data, with the number of excess periods of one month or more being calculated as (the month before the standard delivery date - the month of the deadline for collection of the contract data) x the storage fee calculation period classification of the contract data, and the number of excess periods of less than one month being calculated based on the date of the standard delivery date in accordance with the storage fee calculation period classification of the contract data, and the number of excess periods being calculated as the number of excess periods of one month or more + the number of excess periods of less than one month.

[0049] In addition, the number of excess periods of less than one month may be set as follows: if the contract data storage fee calculation period classification = 1 period, the number of excess periods may be "1", if the contract data storage fee calculation period classification = 2 periods, the number of excess periods may be "1" if the standard delivery date is "1 to 15", and "2" if the standard delivery date is "other than 1 to 15", and if the contract data storage fee calculation period classification = 3 periods, the number of excess periods may be "1" if the standard delivery date is "1 to 10", the number of excess periods may be "2" if the standard delivery date is "11 to 20", and "3" if the standard delivery date is other than "1 to 20".

[0050] [3-2. Sample data] 4 to 7 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the storage fee management device 100 in this embodiment. A specific example of the processing by the control unit 102 of the storage fee management device 100 in this embodiment will be explained with reference to FIGS. 4 to 7.

[0051] (S1: Contract input processing) A specific example of the contract input process will be described with reference to Fig. 4. The contract input unit 102a inputs contract data including the contract number, customer, collection deadline, storage fee unit price, product, contract quantity, contract unit price, and contract amount in response to an operator's operation on a contract input screen (not shown) displayed on the monitor 114, and stores the data in the storage unit 106.

[0052] Figure 4 is a diagram showing an example of contract data. The contract data has fields for the contract number, customer, collection deadline, storage fee calculation period, storage fee unit price, product, contract quantity, contract unit price, and contract amount. On the contract input screen, the contract number is automatically assigned, while the customer, collection deadline, storage fee calculation period, storage fee unit price, product, contract quantity, contract unit price, and contract amount are manually entered by the operator.

[0053] The "Pickup deadline," "storage fee," and "storage fee unit price" are determined in each contract with the customer. The "Pickup deadline" can only be registered at the end of the month.

[0054] The "storage fee calculation period system" is divided into periods as follows: 1:1 period system → 1st period is from the 1st to the last day 2: Two-term system → 1st term is from the 1st to the 15th, 2nd term is from the 16th to the last day 3: 3-term system → 1st term is from the 1st to the 10th, 2nd term is from the 11th to the 20th, 3rd term is from the 21st to the last day

[0055] In the example shown in the figure, the first line has the contract number "MK0001," the customer "XX Trading," the collection deadline "end of January 2024," the storage fee calculation period system "1:1 period system," the storage fee unit price "30 yen," the product "mustard," the contract quantity "1,000 bottles," the contract unit price "250 yen," and the contract amount "250,000 yen." The second line has the contract number "MK0002," the customer "□△ Foods," the collection deadline "end of January 2024," the storage fee calculation period system "3:3 period system," the storage fee unit price "12 yen," the product "black pepper," the contract quantity "4,000 bags," the contract unit price "100 yen," and the contract amount "400,000 yen."

[0056] (S2: Order entry processing) A specific example of order input processing will be described with reference to Fig. 5. For example, in response to an operator's operation on an order input screen (not shown) displayed on the monitor 114, the order input unit 102b inputs order data including the order number, contract number, customer, expected delivery date, product, order quantity, insurance premium surcharge unit price calculated by borne storage fee unit price x excess number of periods, order unit price calculated by contract unit price + borne storage fee surcharge unit price, and order amount calculated by borne order quantity x order unit price based on the contract data registered in the storage unit 106, and stores the data in the storage unit 106.

[0057] Figure 5 is a diagram showing an example of order data. The order data has the following fields: order number, contract number, customer, expected delivery date, product, order quantity, additional cost unit price, order unit price, and order amount. On the order input screen, the order number is automatically assigned, the customer and product are obtained from the contract data using the contract number specified by the operator as a key, the expected delivery date and order quantity are manually entered by the operator, and the additional cost unit price, order unit price, and order amount are automatically calculated.

[0058] The "storage fee surcharge unit price" is calculated by multiplying the contract data storage fee unit price by the number of excess periods. The "excess period" is calculated based on the contract data collection deadline and the scheduled delivery date of the order data, and details will be provided later. The "order unit price" is calculated by adding the contract unit price of the contract data to the calculated storage fee surcharge unit price.

[0059] In the example shown in the figure, the first line contains the order number "JU0001," contract number "MK0001," customer "X Trading," expected delivery date "2024 / 1 / 16," product "mustard," order quantity "350 bottles," storage fee surcharge unit price "0 yen," order unit price "250 yen," and order amount "87,500 yen." The storage fee surcharge unit price "0 yen" is calculated by multiplying the contract data's storage fee unit price "30" by the number of excess periods "0 periods." The order unit price "250 yen" is calculated by adding the contract data's contract unit price "250" and the storage fee surcharge unit price "0."

[0060] The second line contains the order number "JU0002," contract number "MK0001," customer "XXX Trading," expected delivery date "2 / 6 / 2024," product "mustard," order quantity "200 bottles," surcharge unit price "30 yen," order unit price "280 yen," and order amount "56,000 yen." The surcharge unit price "30 yen" is calculated by multiplying the contract data's surcharge unit price "30 yen" by the number of excess periods "1 period." The order unit price "280 yen" is calculated by adding the contract data's contract unit price "250 yen" and the surcharge unit price "30 yen."

[0061] The third line contains the order number "JU0003," contract number "MK0002," customer "□△ Trading," expected delivery date "3 / 19 / 2024," product "black pepper," order quantity "150 bags," storage fee surcharge unit price "60 yen," order unit price "160 yen," and order amount "24,000 yen." The storage fee surcharge unit price "60 yen" is calculated by multiplying the contract data's storage fee unit price "12 yen" by the number of excess periods "5 periods." The order unit price "160 yen" is calculated by adding the contract data's contract unit price "100 yen" + storage fee surcharge unit price "60 yen."

[0062] (S3: Sales input processing) A specific example of sales input processing will be described with reference to Fig. 6. For example, in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, the sales input unit 102c inputs sales data including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee additional unit price calculated by multiplying the storage fee unit price by the number of excess periods, sales unit price calculated by adding the contract unit price to the storage fee additional unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price, and stores the data in the storage unit 106.

[0063] In the sales input process, if the actual delivery date differs from the scheduled delivery date, the storage fee surcharge unit price is recalculated.

[0064] Figure 6 is a diagram showing an example of sales data. The sales data includes the following fields: sales number, contract number, customer, delivery date, product, sales quantity, storage fee surcharge unit price, sales price, and sales amount. On the sales input screen, the sales number is automatically generated, the customer and product are obtained from the contract data using the contract number specified by the operator as a key, the delivery date and sales quantity are manually entered by the operator, and the surcharge unit price, sales price, and sales amount are automatically calculated.

[0065] In the example shown in the figure, the third line contains the sales number "UR0003," contract number "MK0002," customer "□△ Foods," delivery date "3 / 21 / 2024," product "black pepper," sales quantity "150 bags," storage fee surcharge unit price "72 yen," sales price "172 yen," and sales amount "25,800 yen." The storage fee surcharge unit price "72 yen" is calculated by multiplying the storage fee surcharge unit price in the contract data "12 yen" by the number of excess periods "6 periods." The sales price "172 yen" is calculated by adding the contract unit price in the contract information data "100 yen" and the storage fee surcharge unit price "72 yen."

[0066] (Details of how excess periods are calculated) The method for calculating the excess period will be described in detail with reference to Figure 7. The "standard delivery date" is set to the scheduled delivery date of the order data and the delivery date of the sales data.

[0067] (T1): Check whether the delivery end month has exceeded the deadline, and if the standard delivery date is greater than the contract data collection deadline, proceed to calculate the number of exceeded periods in (T2). In all other cases, the number of exceeded periods is set to 0.

[0068] (T2): Calculate the number of excess periods.

[0069] (T2)-1: The number of excess periods of one month or more is calculated as follows: The number of periods exceeding one month will be calculated as follows: (the month before the standard delivery date - the month of the [contract data collection deadline]) x [contract data storage fee calculation period classification].

[0070] (T2)-2: The excess period of less than one month is calculated as follows: In the case of a contract data storage fee calculation period classification = 1:1 period system, the number of excess periods shall be "1". Contract data storage fee calculation period classification = 2: In the case of a two-period system, if the standard delivery date (DD section) is "1 to 15", the number of excess periods will be "1", and if the standard delivery date (DD section) is "other than 1 to 15", the number of excess periods will be "2". Contract data storage fee calculation period classification = 3: In the case of a 3-period system, if the standard delivery date (DD section) is "1-10", the number of excess periods will be "1", if the standard delivery date (DD section) is "11-20", the number of excess periods will be "2", and if the standard delivery date (DD section) is other than "1-20", the number of excess periods will be "3".

[0071] (T2)-3: Calculation of excess period The excess period is calculated by adding the result of (T2)-1 to the result of (T2)-2.

[0072] The calculation of the excess period number of the order data in FIG. 5 will be explained in detail.

[0073] For the order number "JU0001", contract number "MK0001", and expected delivery date "2024 / 1 / 16" on the first line, the standard delivery date "2024 / 1 / 16" is not greater than the deadline for collection of the contract data "end of January 2024", so the excess period is "0" (T1).

[0074] For the order number "JU0002", contract number "MK0001", and expected delivery date "2024 / 2 / 6" on the second line, the standard delivery date "2024 / 2 / 6" > contract data collection deadline "end of January 2024" (T1), and since the excess period is less than one month and the contract data storage fee calculation period system classification = 1:1 period system, the excess period is "1" ((T2)-2).

[0075] For the order number "JU0003", contract number "MK0002", and expected delivery date "3 / 19 / 2024" on the third line, the standard delivery date "3 / 19 / 2024" > contract data collection deadline "end of January 2024" (T1), and since this is more than one month overrun, the number of overrun periods of more than one month is (the month before the standard delivery date "2" - the month of the [contract data collection deadline] "1") x [contract data storage fee calculation period classification "3] = "3 periods" ((T2)-1), and since the contract data storage fee calculation period classification = 3: 3-period system and the standard delivery date (DD section) is "19", it is set to "3 periods" ((T2)-2). From the above, the number of overrun periods is (T2)-1 (= "3 periods") + (T2)-2 (= "2 periods") = "5 periods" ((T2)-3).

[0076] The calculation of the number of overrun periods for the sales data in FIG. 6 will now be described in detail.

[0077] For the sales number "JU0003," contract number "MK0002," and delivery date "3 / 21 / 2024" on the third line, the base delivery date "3 / 21 / 2024" > contract data collection deadline "end of January 2024" (T1), and since this is more than one month overrun, the number of overrun periods of more than one month is (the month before the base delivery date "2" - the month of the [contract data collection deadline] "1") x [contract data storage fee calculation period classification "3]" = "3 periods" ((T2)-1), and the number of overrun periods of less than one month is the contract data storage fee calculation period classification = 3: 3-period system, and since the base delivery date (DD section) is "21," it is set to "3 periods" ((T2)-2). From the above, the number of overrun periods is (T2)-1 (= "3 periods") + (T2)-2 (= "3 periods") = "6 periods" ((T2)-3).

[0078] As described above, according to this embodiment, there is provided a contract input unit 102a for inputting contract data including the contract number, customer, collection deadline, storage fee calculation period, storage fee unit price, product, contract quantity, contract unit price, and contract amount, and a contract input unit 102b for inputting, based on the contract data, the order number, contract number, customer, scheduled delivery date, product, order quantity, insurance premium surcharge unit price calculated by the storage fee unit price × the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and the scheduled delivery date), the order unit price calculated by the contract unit price + the storage fee surcharge unit price, and the order amount calculated by the order quantity × the order unit price. and a sales input unit 102c that inputs sales data including the sales number, contract number, customer, delivery date, product, sales quantity, the storage fee surcharge unit price calculated by multiplying the storage period by the storage fee surcharge unit price (however, the storage period surcharge is calculated based on the collection deadline and delivery date), the sales unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and the sales amount calculated by multiplying the sales quantity by the sales unit price, based on the contract data, making it possible to accurately calculate the warehouse storage fee when the collection deadline is exceeded with little workload.

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

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

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

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

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

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

[0085] Furthermore, with regard to the storage fee management 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.

[0086] For example, all or any part of the processing functions of the storage fee management device 100, particularly the processing functions performed by the control unit 102, 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 storage fee management 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 works with the CPU to form the control unit.

[0087] In addition, this computer program may be stored in an application program server connected to the storage fee management device 100 via any network, and all or part of it may be downloaded as needed.

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

[0089] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of 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 this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

[0091] The storage fee management 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. The storage fee management 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.

[0092] 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]

[0093] 100 Storage fee management device 102 Control section 102a Contract input section 102b Order entry section 102c Sales input section 102d Screen display control unit 104 Communication interface unit 106 Storage section 200 servers 300 Network

Claims

1. A storage fee management device that includes a control unit and manages storage fees when storing products to be delivered to customers in a warehouse, The control unit a contract input means for inputting contract data including a contract number, a customer, a collection deadline, a storage fee unit price to be borne, a product, a contract quantity, a contract unit price, and a contract amount; an order input means for creating order data based on the contract data, including an order number, a contract number, a customer, a scheduled delivery date, a product, an order quantity, an insurance premium surcharge calculated by multiplying the storage fee unit price by the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and the scheduled delivery date), an order unit price calculated by adding the contract unit price to the storage fee surcharge, and an order amount calculated by multiplying the order quantity by the order unit price; A storage fee management device characterized by having a sales input means for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee surcharge unit price calculated by multiplying the storage period by the storage fee surcharge unit price (however, the storage period surcharge is calculated based on the collection deadline and delivery date), sales unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price.

2. The contract data includes a storage fee calculation period classification, The excess of the storage period is the number of excess periods, The storage fee management device of claim 1, characterized in that the scheduled delivery date and the delivery date are used as standard delivery dates, an overage check is performed in the month in which delivery is completed, and the number of overage periods is calculated if the standard delivery date is greater than the collection deadline for the contract data, the number of overage periods for periods of one month or more is calculated by (the month before the standard delivery date - the month of the collection deadline for the contract data) x the storage fee calculation period classification of the contract data, and the number of overage periods for periods less than one month is calculated based on the standard delivery date in accordance with the storage fee calculation period classification of the contract data, and the number of overage periods is calculated by the number of overage periods for periods of one month or more + the number of overage periods for periods less than one month.

3. The excess period of less than one month is If the contract data storage fee calculation period classification is 1 period system, the excess period number will be "1", If the contract data storage fee calculation period classification = 2-period system, if the base delivery date is "1 to 15", the number of excess periods will be "1", and if the base delivery date is "other than 1 to 15", the number of excess periods will be "2". A storage fee management device as described in claim 2, characterized in that when the storage fee calculation period classification of the contract data is a three-period system, if the standard delivery date is "1 to 10", the number of excess periods is "1", if the standard delivery date is "11 to 20", the number of excess periods is "2", and if the standard delivery date is other than "1 to 20", the number of excess periods is "3".

4. 4. The storage fee management device according to claim 1, wherein the warehouse includes a consignment warehouse.

5. A storage fee management method executed by an information processing device having a control unit, Executed in the control unit: a contract input process for inputting contract data including a contract number, a customer, a collection deadline, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount; an order input process for creating order data based on the contract data, including the order number, contract number, customer, expected delivery date, product, order quantity, insurance premium surcharge calculated by multiplying the storage fee unit price by the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and the expected delivery date), order unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and order amount calculated by multiplying the order quantity by the order unit price; a sales input process for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee surcharge unit price calculated by multiplying the storage period by the storage fee surcharge unit price (however, the storage period surcharge is calculated based on the collection deadline and delivery date), sales unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price; A storage fee management method comprising:

6. A storage fee management program to be executed by an information processing device having a control unit, The control unit a contract input process for inputting contract data including a contract number, a customer, a collection deadline, a storage fee unit price, a product, a contract quantity, a contract unit price, and a contract amount; an order input process for creating order data based on the contract data, including the order number, contract number, customer, expected delivery date, product, order quantity, insurance premium surcharge calculated by multiplying the storage fee unit price by the amount of storage period exceeded (however, the amount of storage period exceeded is calculated based on the collection deadline and the expected delivery date), order unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and order amount calculated by multiplying the order quantity by the order unit price; a sales input process for inputting sales data based on the contract data, including the sales number, contract number, customer, delivery date, product, sales quantity, storage fee surcharge unit price calculated by multiplying the storage period by the storage fee surcharge unit price (however, the storage period surcharge is calculated based on the collection deadline and delivery date), sales unit price calculated by adding the contract unit price to the storage fee surcharge unit price, and sales amount calculated by multiplying the sales quantity by the sales unit price; Storage fee management program to execute.

Images