Damage claim amount checking device, method, and program

Abstract

To provide a damage claim amount checking device, method, and program that can prompt a user to review a damage claim amount when the damage claim amount is deemed inappropriate.SOLUTION: The damage claim amount checking device includes: a first calculation unit for calculating the inventory valuation unit price of a predetermined product; a second calculation unit for calculating a first damage claim amount for the predetermined product on the basis of the inventory valuation unit price; a storage unit for storing a master in which a second, predetermined damage claim amount for the predetermined product is registered, the amount serving as a reference for evaluating the damage claim amount at the time of the claim; and a control unit that controls whether to output an alert prompting a change to the second damage claim amount registered in the master on the basis of the comparison result between the first damage claim amount and the second damage claim amount.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a damage claim amount checking device, a damage claim amount checking method, and a damage claim amount checking program. [Background technology]

[0002] Patent Document 1 discloses a technique for determining the amount of damage claim, which determines the amount of damage claim depending on the damage situation. [Prior art documents] [Patent documents]

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

[0004] By the way, trading companies and other companies that handle various products may store their product inventory in external warehouses or outsource delivery to shipping companies. In such cases, products may be damaged due to defects of the outsourced party. The amount of damage claim is determined based on the asset value of the damaged product, but to avoid fluctuations in the amount of damage claim to the insurance company for the same product, a fixed amount of damage claim is set for the same product.

[0005] However, when damage claims are made at a fixed amount, there have been cases where the amount claimed for damages is less than the asset value if the purchase price rises. Recently, especially in import purchases, exchange rates have fluctuated dramatically, and purchase prices can fluctuate significantly, so there is an increasing need to regularly review the unit price claimed when making damage claims.

[0006] The present invention has been made in consideration of the above, and aims to provide a damage claim amount checking device, a damage claim amount checking method, and a damage claim amount checking program that can prompt a user to review the damage claim amount if the damage claim amount is inappropriate. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the damage claim amount checking device of the present invention comprises a first calculation unit that calculates the inventory valuation unit price of a specified product, a first calculation unit that calculates a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product, a memory unit that stores a master in which a second damage claim amount predetermined for the specified product, which second damage claim amount is used as a basis for determining the damage claim amount at the time of claiming damage for the specified product, is registered, and a control unit that controls whether to output an alert prompting a change to the second damage claim amount registered in the master depending on the result of comparing the first damage claim amount with the second damage claim amount.

[0008] In addition, the damage claim amount checking method of the present invention is a damage claim amount checking method executed by a computer, and includes: a first calculation step of calculating an inventory valuation unit price of a specified product; a second calculation step of calculating a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product; and a control step of controlling whether to output an alert prompting a change of the second damage claim amount registered in a master in which a second damage claim amount predetermined for the specified product, which second damage claim amount is used as a basis for determining the damage claim amount at the time of a damage claim for the specified product, is compared with the first damage claim amount.

[0009] In addition, the damage claim amount check program of the present invention is a damage claim amount check program that causes a computer to execute a first calculation process that calculates the inventory valuation unit price of a specified product, a second calculation process that calculates a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product, and a control process that controls whether to output an alert prompting a change to the second damage claim amount registered in the master, depending on the result of comparing the second damage claim amount, which is a second damage claim amount that is predetermined for the specified product and is used as a basis for determining the damage claim amount at the time of a damage claim for the specified product, with the first damage claim amount. [Effects of the Invention]

[0010] According to the present invention, it is possible to urge the user to review the amount of the damage claim if the amount is not appropriate. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a damage claim amount check device according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of purchase data according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of inventory data according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of alert consideration data according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the outsourcing company ratio master according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the damage claim unit price master according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of billing unit price alert inquiry data according to the embodiment. [Figure 8] FIG. 8 is a flowchart showing an example of the flow of processing executed by the damage claim amount check device according to the embodiment. [Figure 9] FIG. 9 is a diagram for explaining an example of a process executed by the damage claim amount check device according to the embodiment. [Figure 10] FIG. 10 is a flowchart showing an example of the flow of processing executed by the alert control unit of the damage claim amount check device according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of information output by the output device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of a damage claim amount check device, a damage claim amount check method, and a damage claim amount check program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0013] [1. Configuration of the damage claim amount check device] An example of the configuration of a damage claim amount check device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a damage claim amount check device according to this embodiment.

[0014] The damage claim amount check device 100 shown in FIG. 1 is a commercially available desktop personal computer. The damage claim amount check 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. The damage claim amount check device 100 is installed in a company such as a trading company that imports and sells products such as food. The damage claim amount check device 100 is used by users such as employees working for such a company.

[0015] The damage claim amount check device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the damage claim amount check device 100 is connected to each other so that they can communicate with each other via any communication path.

[0016] The communication interface unit 104 communicatively connects the damage claim amount check device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the damage claim amount check device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may also be stored in the server 200, for example.

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

[0018] The memory unit 106 stores various databases, tables, files, etc. The memory unit 106 stores computer programs that cooperate with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 stores purchase data 106a, inventory data 106b, alert review data 106c, a subcontractor ratio master 106d, a damage claim unit price master 106e, and claim unit price alert inquiry data 106f.

[0019] The purchase data 106a is a table in which data (records) related to purchased products are registered. Here, the purchased products may be, for example, food products. In the following description, an example will be given in which two types of products, tapioca starch and starch, are imported; however, the products are not limited to these. FIG. 2 is a diagram illustrating an example of the purchase data 106a according to an embodiment. The purchase data 106a illustrated in FIG. 2 associates and registers the purchase date, the purchased product (type of product), the quantity of the purchased product, the foreign currency unit price of the purchased product (the price in foreign currency per product), the exchange rate, the Japanese unit price of the purchased product (the price in Japanese currency per product), and the Japanese amount of the purchased product (the total amount of all purchased products). For example, the record in the first row of the purchase data 106a illustrated in FIG. 2 indicates that 10 units of starch were purchased on January 10, 2024. Furthermore, this record indicates that the foreign currency unit price per unit of starch is $10, the exchange rate is $1 = 105 yen, the Japanese currency unit price per unit of starch is 1,050 yen, and the Japanese currency amount for the 10 units of starch purchased is 10,500 yen. The same applies to records from the second line onwards. Records are registered in the purchase data 106a by the purchase data registration unit 102a, which will be described later.

[0020] The inventory data 106b is a table in which inventory valuation unit prices of products are registered for each month. FIG. 3 is a diagram illustrating an example of the inventory data 106b according to the embodiment. The inventory data 106b illustrated in FIG. 3 associates and registers the target year and month (target year and month), products, and inventory valuation unit prices. For example, the first record of the inventory data 106b illustrated in FIG. 3 indicates that the inventory valuation unit price of starch as of January 2024 is 1,050 yen. The same is true for the second record of the inventory data 106b. Here, the third record of the inventory data 106b indicates that the inventory valuation unit price of starch as of February 2024 is 1,200 yen. Thus, even for the same product, "starch," the inventory valuation unit price fluctuates due to fluctuations in the exchange rate. Records are registered in the inventory data 106b by the inventory valuation unit price calculation unit 102b, which will be described later.

[0021] The alert consideration data 106c is data used to consider (determine) whether to issue an alert prompting a change (revision) of the damage claim amount registered in the damage claim unit price master 106e for each combination of product and outsourced company. Specifically, the alert consideration data 106c is a table in which the ideal damage claim unit price (appropriate damage claim amount per product) for each product to be claimed from an insurance company when the product is damaged due to a defect of the outsourced company (consignee) is registered for each month. In the following explanation, two warehouse companies, "○× Warehouse" and "△□ Warehouse," which store product inventory, are used as outsourced companies, but the number of outsourced companies is not limited to two. FIG. 4 is a diagram showing an example of the alert consideration data 106c according to an embodiment. The alert consideration data 106c shown in FIG. 4 associates and registers the target year and month, product, outsourced company, and ideal damage claim unit price. For example, the record in the first line of the alert consideration data 106c shown in Fig. 4 indicates that the damage claim unit price for starch to be claimed from the insurance company in the event that starch is damaged due to a defect at the XX warehouse as of January 2024 is 1,050 yen. The same applies to the records in the second line and thereafter. Records are registered in the alert consideration data 106c by the damage claim amount calculation unit 102c, which will be described later.

[0022] The outsourcing company multiplier master 106d is a master that registers the multiplier used to calculate the appropriate damage claim unit price for each outsourcing company. Such a multiplier is a value based on the fees incurred in dealing with the damage when a product is damaged and damage occurs, and the opportunity loss incurred due to the damage. The multiplier can also be revised. Figure 5 is a diagram showing an example of the outsourcing company multiplier master 106d according to an embodiment. The outsourcing company multiplier master 106d shown in Figure 5 registers the outsourcing company, the year and month when the multiplier was revised (the revision year and month), and the multiplier in association with each other. For example, the record in the first row of the outsourcing company multiplier master 106d shown in Figure 5 is the multiplier when a product is damaged due to a defect at the Ox warehouse, and indicates that the multiplier revised in January 2024 is 1.1. The same applies to the record in the second row.

[0023] The damage claim unit price master 106e is a master in which damage claim unit prices are registered for each product, which serve as a reference for the user when determining the damage claim amount at the time of actual damage claim. FIG. 6 is a diagram showing an example of the damage claim unit price master 106e according to the embodiment. The damage claim unit price master 106e shown in FIG. 6 associates and registers the product, the year and month when the damage claim amount was revised (revision year and month), and the damage claim unit price. The first record of the damage claim unit price master 106e shown in FIG. 6 indicates the damage claim unit price at the time of damage claim in the case of damaged starch, which is 1,200 yen as revised in January 2024. The same applies to the second record. In this way, the damage claim unit price master 106e registers damage claim unit prices that are predetermined for a specific product and serve as a basis for determining the damage claim amount at the time of damage claim for the specific product. Such damage claim unit prices are an example of second damage claim prices. The damage claim unit price registered in the damage claim unit price master 106e is changed by the damage claim unit price changing unit 102e, which will be described later.

[0024] The invoice unit price alert inquiry data 106f is a table in which the results of a determination on a monthly basis as to whether or not to issue an alert prompting a change in the damage claim amount registered in the damage claim unit price master 106e for each combination of product and subcontractor are registered. FIG. 7 is a diagram showing an example of the invoice unit price alert inquiry data 106f according to an embodiment. The invoice unit price alert inquiry data 106f shown in FIG. 7 associates and registers the year and month (target year and month) when it was determined whether or not to issue an alert, the product, the subcontractor, the damage claim unit price, the desired damage claim unit price, the alert target indicating whether or not an alert is to be issued, and the number of consecutive months (number of times (target months)) during which it was determined that an alert is to be issued. The number of months in the invoice unit price alert inquiry data 106f is "0" if it was determined not to issue an alert in the previous month, and "1" if it was determined not to issue an alert in the current month.

[0025] The first record of the claim unit price alert inquiry data 106f shown in Figure 7 indicates that, as of January 2024, the damage claim unit price for starch registered in the damage claim unit price master 106e, which the user refers to when determining the damage claim amount in the event that starch damage occurs due to a defect at the XX warehouse, is 1,200 yen, and indicates the result of a determination that an alert prompting a change to this starch damage claim unit price (1,200 yen) will not be issued (not applicable). The first record also indicates that, as of January 2024, if starch damage occurs due to a defect at the XX warehouse, the appropriate damage claim unit price for starch is 1,050 yen. The first record also indicates that the number of months described above is "0."

[0026] The record on the fifth line of the claim unit price alert inquiry data 106f indicates that, as of February 2024, damage to starch occurs due to a defect at the XX warehouse, and the damage claim unit price for starch registered in the damage claim unit price master 106e, which the user refers to when determining the damage claim amount, is 1,200 yen, and indicates that an alert prompting a change to this starch damage claim unit price (1,200 yen) should be issued (target). The record on the fifth line also indicates that, as of February 2024, if damage to starch occurs due to a defect at the XX warehouse, the appropriate damage claim unit price for starch is 1,320 yen. The record on the fifth line also indicates that the number of months mentioned above is "1."

[0027] Records are registered in the billing unit price alert inquiry data 106f by the alert control unit 102d, which will be described later.

[0028] Returning to Figure 1, the control unit 102 is a CPU (Central Processing Unit) or the like that comprehensively controls the damage claim amount check device 100. The control unit 102 has an internal memory for storing control programs such as an OS (Operating System), programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. The control unit 102 includes a purchase data registration unit 102a, an inventory valuation unit price calculation unit 102b, a damage claim amount calculation unit 102c, an alert control unit 102d, and a damage claim unit price change unit 102e.

[0029] The purchase data registration unit 102a registers data relating to purchased products in purchase data 106a.

[0030] The inventory evaluation unit price calculation unit 102b calculates the inventory evaluation unit price of each commodity using the purchase data 106a.

[0031] The damage claim amount calculation unit 102c uses the inventory data 106b and the consignment company ratio master 106d to calculate the appropriate damage claim unit price for each combination of product and consignment company.

[0032] The alert control unit 102d compares the expected damage claim unit price for each product with the damage claim unit price registered in the damage claim unit price master 106e, and controls whether to output an alert prompting a change in the damage claim amount registered in the damage claim unit price master 106e depending on the comparison result.

[0033] The damage claim unit price change unit 102e changes the damage claim unit price to be changed that is registered in the damage claim unit price master 106e based on a change instruction to change the damage claim unit price input by the user via the input device 112.

[0034] [2. Processing performed by the damage claim amount check device] Next, an example of the processing executed by each unit 102a to 102c of the control unit 102 of the damage claim amount check device 100 will be described with reference to Fig. 8 and Fig. 9. Fig. 8 is a flowchart showing an example of the flow of processing executed by the damage claim amount check device 100 according to the embodiment. Fig. 9 is a diagram for explaining an example of processing executed by the damage claim amount check device 100 according to the embodiment. The processing shown in Fig. 8 is executed, for example, monthly.

[0035] As shown in FIG. 8, the purchase data registration unit 102a performs purchase input (step S101). To explain this using a specific example, the purchase data registration unit 102a accepts data related to purchased products and registers the accepted data in the purchase data 106a. For example, the purchase data registration unit 102a accepts the purchase date, product, quantity, foreign currency unit price, rate, Japanese unit price, and Japanese amount from the user via the input device 112. Then, as shown in FIG. 9, the purchase data registration unit 102a registers one record in the purchase data 106a, in which the accepted purchase date, product, quantity, foreign currency unit price, rate, Japanese unit price, and Japanese amount are associated with each other.

[0036] Then, the inventory valuation unit price calculation unit 102b executes cost calculation processing (step S102). Here, in the cost calculation processing, the inventory valuation unit price calculation unit 102b uses the purchase data 106a to calculate the inventory valuation unit price of each commodity for the current month (target year and month). Specifically, the inventory valuation unit price calculation unit 102b calculates the inventory valuation unit price according to the following formula (1):

[0037] (Inventory amount at the end of the previous month + Inventory amount at the end of the current month) / Inventory quantity at the end of the current month = Inventory valuation unit price (1) Here, " / " is an operator indicating division.

[0038] For example, the inventory valuation unit price calculation unit 102b calculates (10500+21000) / (10+20)=1050 according to formula (1), and calculates the inventory valuation unit price of starch as of January 2024 as 1050 yen, as shown in FIG. 9. Similarly, the inventory valuation unit price calculation unit 102b calculates 4200 / 5=840, and calculates the inventory valuation unit price of tapioca starch as of January 2024 as 840 yen, as shown in FIG. 9. Furthermore, the inventory valuation unit price calculation unit 102b calculates (10500+21000+22500) / (10+20+15)=1200, and calculates the inventory valuation unit price of starch as of February 2024 as "1200 yen," as shown in FIG. 9.

[0039] Then, the inventory valuation unit price calculation unit 102b registers one record in which the target year / month, product, and inventory valuation unit price are associated with each other in the inventory data 106b. For example, as shown in Figure 9, the inventory valuation unit price calculation unit 102b registers a record indicating that the inventory valuation unit price of starch as of February 2024 is 1,200 yen in the inventory data 106b.

[0040] As described above, the inventory valuation unit price calculation unit 102b calculates the inventory valuation unit price of a predetermined product. The inventory valuation unit price calculation unit 102b is, for example, an example of a first calculation unit.

[0041] Then, the damage claim calculation unit 102c executes the monthly closing process (step S103) and terminates the process shown in FIG. 8. Here, in the monthly closing process, the damage claim calculation unit 102c calculates the ideal damage claim unit price using the inventory data 106b and the subcontractor ratio master 106d. Specifically, the damage claim calculation unit 102c calculates the ideal damage claim unit price for each combination of product and subcontractor. More specifically, for each combination of product and subcontractor, the damage claim calculation unit 102c obtains the inventory valuation unit price of the product for the target year and month from the inventory data 106b, and obtains the subcontractor ratio for the target year and month from the subcontractor ratio master 106d. Then, the damage claim calculation unit 102c calculates the ideal damage claim unit price according to the following formula (2):

[0042] Inventory valuation unit price × multiplier = Desired damage claim unit price (2)

[0043] For example, the damage claim calculation unit 102c calculates the ideal damage claim unit price for a combination of the product "starch" and the subcontractor "XX Warehouse" when the target year and month is February 2024. In this case, as shown in FIG. 9, the damage claim calculation unit 102c obtains "1,200 yen" from the inventory data 106b as the inventory valuation unit price of starch for February 2024. Also, as shown in FIG. 9, the damage claim calculation unit 102c obtains "1.1" as the multiplier for "XX Warehouse" for February 2024 from the subcontractor multiplier master 106d. Then, the damage claim calculation unit 102c calculates 1,200 x 1.1 = 1,320, and calculates the ideal damage claim unit price of "1,320 yen." The damage claim calculation unit 102c then registers a record in which the target year and month, product, subcontractor, and ideal damage claim unit price are associated in the alert consideration data 106c. For example, as shown in FIG. 9, the damage claim amount calculation unit 102c registers in the alert consideration data 106c a record indicating that the unit price of the damage claim for starch to be claimed from the insurance company in the event that the starch is damaged due to a defect at the ○× warehouse as of February 2024 is 1,320 yen.

[0044] As described above, the damage claim calculation unit 102c calculates the ideal damage claim unit price for a specified product based on the inventory valuation unit price of the specified product. Specifically, the damage claim calculation unit 102c calculates the ideal damage claim unit price by multiplying the inventory valuation unit price of the specified product by a multiplier corresponding to the outsourcing company to which the specified product is outsourced. Such an ideal damage claim unit price is an example of a first damage claim amount. Furthermore, the damage claim calculation unit 102c is an example of a second calculation unit.

[0045] FIG. 10 is a flowchart showing an example of the flow of processing executed by the alert control unit 102d according to the embodiment. For example, the alert control unit 102d executes the processing shown in FIG. 10 monthly. Furthermore, for example, the alert control unit 102d executes the processing shown in FIG. 10 after the processing shown in FIG. 8 has been executed. As shown in FIG. 10, the alert control unit 102d acquires the ideal damage claim unit price for each combination of product and outsourcing company from the alert consideration data 106c (step S201). For example, as shown in FIG. 9, the alert control unit 102d acquires the ideal damage claim unit price of "1,320 yen" as of February 2024 for the combination of the product "starch" and the outsourcing company "○× Warehouse" from the alert consideration data 106c.

[0046] The alert control unit 102d also acquires the damage claim unit price of each product from the damage claim unit price master 106e (step S202). For example, as shown in Fig. 9, the alert control unit 102d acquires the damage claim unit price of "1200 yen" for the product "starch" from the damage claim unit price master 106e.

[0047] Then, for each combination of product and outsourced company, the alert control unit 102d compares the acquired damage claim unit price with the acquired ideal damage claim unit price, and determines whether the ideal damage claim unit price is greater than the damage claim unit price (step S203). If the damage claim unit price is greater than or equal to the ideal damage claim unit price (step S203: No), it is considered that an appropriate damage claim unit price corresponding to the asset value of the product is registered in the damage claim unit price master 106e. In this case (step S203: No), the alert control unit 102d controls not to output an alert (step S204), and ends the processing shown in FIG. 10.

[0048] The processing of step S204 will be described below using a specific example. For example, assume that the target date is January 2024, the product is "starch," and the contract company is "XX Warehouse," the damage claim unit price is "1,200 yen," and the desired damage claim unit price is "1,050 yen." In this case, the damage claim unit price of "1,200 yen" is equal to or greater than the desired damage claim unit price of "1,050 yen" (step S203: No). In this case, in step S204, the alert control unit 102d registers a record in which the target date is "January 2024," the product is "starch," the contract company is "XX Warehouse," the damage claim unit price is "1,200 yen," the desired damage claim unit price is "1,050 yen," the alert target is "not applicable," and the number of target months is "0" in the claim unit price alert inquiry data 106f, as shown in FIG. 9.

[0049] Then, in step S204, the alert control unit 102d controls the output device 114 so as not to output an alert.

[0050] On the other hand, if the expected damage claim unit price is greater than the damage claim unit price (step S203: Yes), there is a possibility of a loss, and it is considered that an appropriate damage claim unit price corresponding to the asset value of the product has not been registered in the damage claim unit price master 106e. In this case (step S203: Yes), the alert control unit 102d controls the output device 114 to output an alert (step S205), and ends the processing shown in FIG. 10.

[0051] The processing of step S205 will be described below using a specific example. For example, assume that the target date is February 2024, the product is "starch," and the contract company is "XX Warehouse," the damage claim unit price is "1,200 yen," and the ideal damage claim unit price is "1,320 yen." In this case, the ideal damage claim unit price of "1,320 yen" is greater than the damage claim unit price of "1,200 yen" (step S203: Yes). In this case, in step S205, the alert control unit 102d registers a record in which the target date "February 2024," the product is "starch," the contract company is "XX Warehouse," the damage claim unit price of "1,200 yen," the ideal damage claim unit price of "1,320 yen," the alert target is "target," and the number of target months is "1" in the claim unit price alert inquiry data 106f, as shown in FIG. 9 .

[0052] Then, in step S205, the alert control unit 102d controls the output device 114 to output an alert. FIG. 11 is a diagram showing an example of information output by the output device 114 according to the embodiment. For example, when the output device 114 is a monitor, the alert control unit 102d causes the output device 114 to display a message 120, as shown in FIG. 11, to prompt the user to change the damage claim unit price "1200 yen" registered in the damage claim unit price master 106e. The message 120 reads, "The damage claim unit price of 1200 yen for starch registered in the damage claim unit price master is inappropriate and may result in a loss. The appropriate damage claim unit price for starch is 1320 yen. Therefore, please consider changing the damage claim unit price for starch registered in the damage claim unit price master." As a result, the user realizes that the damage claim unit price for starch, "1,200 yen," registered in the damage claim unit price master 106e is inappropriate, and operates the input device 112 to input a change instruction to the control unit 102 to change the damage claim unit price for starch to "1,320 yen."

[0053] The damage claim unit price change unit 102e then accepts the change instruction and, based on the accepted change instruction, changes the damage claim unit price for starch registered in the damage claim unit price master 106e to "1,320 yen" and changes the corresponding revision year and month registered in the damage claim unit price master 106e to the current month. As a result, if the starch is damaged due to a defect of the subcontractor, the user can make a damage claim at an appropriate damage claim amount. As described above, the damage claim unit price change unit 102e accepts the change instruction to change the damage claim unit price registered in the damage claim unit price master 106e and changes the damage claim unit price registered in the damage claim unit price master 106e based on the change instruction. The damage claim unit price change unit 102e is an example of a change unit.

[0054] 11, the alert control unit 102d causes the output device 114 to display the target month number 121 "1" along with the message 120. By displaying the target month number 121, if the value of the target month number 121 is equal to or less than a predetermined value, the user can determine that the alert was merely accidentally output and that there is little need to change the damage claim unit price registered in the damage claim unit price master 106e. Furthermore, if the value of the target month number 121 is greater than a predetermined value, the user can determine that there is a high need to change the damage claim unit price registered in the damage claim unit price master 106e. Therefore, the displayed target month number 121 is useful information for the user when determining whether or not to change the damage claim unit price.

[0055] According to the embodiment described above, the alert control unit 102d compares the appropriate damage claim unit price for each product with the damage claim unit price registered in the damage claim unit price master 106e, and controls whether to output an alert prompting a change to the damage claim amount registered in the damage claim unit price master 106e depending on the comparison result, so that if the damage claim amount is inappropriate, the user can be prompted to review the damage claim amount.

[0056] Furthermore, according to the embodiment, when the desired damage claim unit price is larger than the actual damage claim unit price, the alert control unit 102d controls the output device 114 to output an alert, thereby making it possible to suppress the occurrence of losses.

[0057] Furthermore, according to the embodiment, the damage claim amount calculation unit 102c calculates the ideal damage claim unit price by multiplying the inventory evaluation unit price of a specified product by a multiplier corresponding to the consignment company to which the specified product is consigned. Therefore, for each consignment company, the ideal damage claim unit price can be calculated as the inventory evaluation unit price plus an amount that takes into account commissions, opportunity losses, etc.

[0058] Furthermore, according to the embodiment, the damage claim unit price change unit 102e accepts a change instruction to change the damage claim unit price registered in the damage claim unit price master 106e, and changes the damage claim unit price registered in the damage claim unit price master 106e based on the change instruction, thereby making it possible to claim an appropriate damage claim amount.

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

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

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

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

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

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

[0065] Furthermore, with regard to the damage claim amount check device 100, the components shown in the figures are functional concepts, and the device does not necessarily have to be physically configured as shown in the figures.

[0066] For example, all or any part of the processing functions of the damage claim amount check device 100, particularly the processing functions performed by the control unit, may be realized 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 on a non-transitory computer-readable recording medium containing programmed instructions for causing an information processing device (computer) to execute the processing described in this embodiment, and is mechanically read by the damage claim amount check 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 in cooperation with the CPU to form the control unit.

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

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

[0069] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

[0071] The damage claim amount check device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The damage claim amount check 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.

[0072] 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. [Industrial Applicability]

[0073] The present invention is useful, for example, in industries that import and sell products and consign the products to consignment companies. [Explanation of symbols]

[0074] 100 Damage claim amount check device 102 Control section 102a Purchase Data Registration Section 102b Inventory Valuation Unit Cost Calculation Section 102c Claims Calculation Section 102d Alert control section 102e Damage Claim Unit Price Change Section 104 Communication interface unit 106 Storage section 106a Purchase Data 106b Inventory Data 106c Alert Review Data 106d Commissioned Company Ratio Master 106e Damage claim unit price master 106f Billing unit price alert inquiry data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. a first calculation unit that calculates an inventory valuation unit price of a predetermined commodity; a second calculation unit that calculates a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product; a storage unit that stores a master in which a second damage claim amount, which is a predetermined second damage claim amount for the specified product and is used as a basis for determining the second damage claim amount when a damage claim for the specified product is made; a control unit that controls whether to output an alert prompting a user to change the second damage claim amount registered in the master according to a comparison result between the first damage claim amount and the second damage claim amount; Equipped with Damage claim amount checking device.

2. the control unit controls to output the alert when the first damage claim amount is greater than the second damage claim amount; 2. The damage claim amount checking device according to claim 1.

3. the second calculation unit calculates the first damage claim amount by multiplying the inventory evaluation unit price of the specified product by a multiplying factor corresponding to the consignment company to which the specified product is consigned; 2. The damage claim amount checking device according to claim 1.

4. a change unit that receives a change instruction to change the second damage claim amount and changes the second damage claim amount registered in the master based on the change instruction; 2. The damage claim amount checking device according to claim 1.

5. 1. A computer-implemented method for checking damage claims, comprising: a first calculation step of calculating an inventory valuation unit price of a predetermined commodity; a second calculation step of calculating a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product; a control step of controlling whether to output an alert prompting a change to the second damage claim amount registered in the master in accordance with a result of comparison between the first damage claim amount and a second damage claim amount that is predetermined for the specified product and is used as a basis for determining the damage claim amount at the time of claiming damage for the specified product and that is stored in the master; Including how to check the amount of damage claims.

6. On the computer, a first calculation process for calculating an inventory valuation unit price of a predetermined commodity; a second calculation process for calculating a first damage claim amount for the specified product based on the inventory valuation unit price of the specified product; a control process for controlling whether to output an alert prompting a change to the second damage claim amount registered in the master, depending on a result of comparison between the first damage claim amount and a second damage claim amount stored in a master in which the second damage claim amount is stored, the second damage claim amount being a basis for determining the damage claim amount at the time of claiming damage for the specified product; A damage claim amount check program to execute the above.

Images