Invoice calculation device, invoice calculation method, and invoice calculation program

Abstract

This invention provides a billing amount calculation device, a billing amount calculation method, and a billing amount calculation program that can obtain the necessary information for billing for each billing recipient. [Solution] The billing amount calculation device according to the embodiment acquires store order data including a first quantity and a first amount of goods each time a store places an order for goods with a supplier during a predetermined period, acquires receipt and payment data including a first inventory count at the supplier on the last day of the predetermined period and a second amount based on the second quantity of goods shipped from the supplier to the store during the predetermined period, calculates a first billing amount to the supplier if the first inventory count differs from a third inventory count determined based on the sum of the first quantities included in all store order data acquired during the predetermined period and the second inventory count on the first day, and calculates a second billing amount to the store if the second amount differs from a third amount based on the sum of the first amounts included in all store order data acquired during the predetermined period.

Description

Technical Field

[0001] The present invention relates to a claim amount calculation device, a claim amount calculation method, and a claim amount calculation program.

Background Art

[0002] Patent Document 1 discloses a technique for recording confirmed sales. In this technique, for example, provisional sales for a predetermined month are recorded, and the difference performance for the sales of the predetermined month is input to record the confirmed sales for the predetermined month.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, regarding the sales recording standard of a company (such as a manufacturer) whose customers are stores such as convenience stores with multi-store operations, there is a case where a standard (loading standard) of recording sales at the timing when goods are loaded at the customer store is adopted. In many cases, after passing through the "center (logistics center, central warehouse)" owned or entrusted by the store side, the goods are then delivered to each store. However, for the company, it is difficult to accurately and timely grasp the movement after delivering the goods to the center. Therefore, the company will adjust the sales based on the inventory report from the center at the end of the month. For example, the company bills the store or the operating company of the center for the sales difference at the end of the month.

[0005] However, since the person in charge of the company that makes the above-mentioned claims needs to confirm and distinguish the billing destination, the billing operation is complicated. Therefore, it is desirable to obtain the information necessary for billing for each billing destination.

[0006] The present invention has been made in view of the above, and aims to provide a billing amount calculation device, a billing amount calculation method, and a billing amount calculation program that can obtain the information necessary for billing for each billing party. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the billing amount calculation device according to the present invention includes: a first acquisition unit that acquires store order data including a first quantity of the predetermined goods and a first amount determined based on the first quantity and the unit price of the predetermined goods each time a predetermined store places an order for predetermined goods with a predetermined supplier during a predetermined period including multiple days; and a second acquisition unit that acquires receipt and payment data for the predetermined goods at the predetermined supplier on the last day of the predetermined period, including a first inventory quantity of the predetermined goods on the last day of the predetermined period and a second amount determined based on the second quantity and the unit price of the predetermined goods shipped from the predetermined supplier to the predetermined store during the predetermined period. The system includes: a first calculation unit that calculates a first invoice amount to a predetermined supplier based on the difference between the first and second inventory quantities and the unit price of the predetermined product, if the third inventory quantity of the predetermined product, determined based on the sum of all first quantities included in all store order data acquired during the predetermined period and the second inventory quantity of the predetermined product on the first day of the predetermined period, differs from the first inventory quantity; and a second calculation unit that calculates a second invoice amount to a predetermined store based on the difference between the third and second amounts, if the third amount of the predetermined product, determined based on the sum of all first amounts included in all store order data acquired during the predetermined period, differs from the second amount of the predetermined product.

[0008] Furthermore, the billing amount calculation method according to the present invention is a billing amount calculation method performed by a computer, and includes a first acquisition step of acquiring store order data, which includes a first quantity of the predetermined goods and a first amount determined based on the first quantity and the unit price of the predetermined goods, each time a predetermined store places an order for predetermined goods with a predetermined supplier during a predetermined period including multiple days; and a second acquisition step of acquiring receipt and payment data for the predetermined goods at the predetermined supplier on the last day of the predetermined period, which includes a first inventory quantity of the predetermined goods on the last day of the predetermined period and a second amount determined based on the second quantity and the unit price of the predetermined goods shipped from the predetermined supplier to the predetermined store during the predetermined period. The calculation includes: a first calculation step of calculating a first invoice amount to a predetermined supplier based on the difference between the second inventory quantity and the first inventory quantity and the unit price of the predetermined product, if the third inventory quantity of the predetermined product is determined based on the sum of all the first quantities included in all the store order data acquired during the predetermined period and the second inventory quantity of the predetermined product on the first day of the predetermined period, and the first inventory quantity; and a second calculation step of calculating a second invoice amount to a predetermined store based on the difference between the third amount and the second amount, if the third amount of the predetermined product is determined based on the sum of all the first amounts included in all the store order data acquired during the predetermined period and the second amount of the predetermined product, and the difference between the third amount and the second amount.

[0009] Furthermore, the billing amount calculation program according to the present invention includes a first acquisition process in which a computer acquires store order data including a first quantity of the specified goods and a first amount determined based on the first quantity and the unit price of the specified goods each time a specified store places an order for the specified goods with a specified supplier during a predetermined period including multiple days; a second acquisition process in which the computer acquires receipt and payment data for the specified goods at the specified supplier on the last day of the predetermined period, including a first inventory quantity of the specified goods on the last day of the predetermined period, and a second amount determined based on the second quantity and the unit price of the specified goods shipped from the specified supplier to the specified store during the predetermined period; and during the predetermined period This program is for executing a first calculation process that calculates a first invoice amount to a predetermined supplier based on the difference between the first and second inventory quantities and the unit price of the predetermined product, if the third inventory quantity of the predetermined product, which is determined based on the sum of all the first quantities included in all the store order data obtained, and the second inventory quantity of the predetermined product on the first day of the predetermined period, differs from the first inventory quantity. It also includes a second calculation process that calculates a second invoice amount to a predetermined store based on the difference between the third and second amounts, if the third amount of the predetermined product, which is determined based on the sum of all the first amounts included in all the store order data obtained during the predetermined period, differs from the second amount of the predetermined product. [Effects of the Invention]

[0010] According to the present invention, the necessary information for each claim can be obtained. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram showing an overview of an example of the configuration of the billing amount calculation device according to the embodiment, in block diagram form. [Figure 2] Figure 2 shows an example of a customer master according to the embodiment. [Figure 3] Figure 3 shows an example of a warehouse master according to the embodiment. [Figure 4] Figure 4 shows an example of a product master according to the embodiment. [Figure 5] Figure 5 is a diagram illustrating an example of the process performed by the billing amount calculation device according to this embodiment. [Figure 6] Figure 6 shows an example of inventory data according to the present invention. [Figure 7] Figure 7 shows an example of various data used when moving goods from a company warehouse to a distribution center in an embodiment. [Figure 8] Figure 8 shows an example of store order data and sales data according to the embodiment. [Figure 9] Figure 9 shows an example of receipt and payment data and end-of-month receipt and payment data according to the embodiment. [Figure 10] Figure 10 shows an example of an input screen according to the embodiment. [Figure 11] Figure 11 shows an example of the display of the header screen after the registration button on the details screen according to the embodiment has been pressed. [Figure 12] Figure 12 shows another example of the display of the two input screens (header screen and detail screen) according to the embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the billing amount calculation device, billing amount calculation method, and billing amount calculation program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

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

[0014] The claim amount calculation device 100 shown in FIG. 1 is a commercially available desktop personal computer. Note that the claim amount calculation device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer. The claim amount calculation device 100 is provided, for example, in a company (such as a manufacturer) whose customers are stores such as convenience stores with multiple store deployments. And the claim amount calculation device 100 is used by a user such as an employee working for such a company.

[0015] The claim amount calculation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the claim amount calculation device 100 is communicably connected via an arbitrary communication path.

[0016] The communication interface unit 104 communicably connects the claim amount calculation device 100 to the network 400 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 via another device and a communication line. Here, the network 400 has a function of communicably connecting the claim amount calculation device 100 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 may be stored, for example, in the server 200.

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

[0018] The storage unit 106 stores various databases, tables, and files. The storage unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. For example, the storage unit 106 can be 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 storage unit 106 stores customer master data 106a, warehouse master data 106b, product master data 106c, inventory data 106d, movement instruction data 106e, shipping data 106f, incoming arrival schedule data 106g, moving arrival data 106h, sales data 106i, and end-of-month receipt and payment data 106j.

[0019] Figure 2 shows an example of a customer master 106a according to the embodiment. The customer master 106a is a master in which a customer code, customer name, warehouse operator code, and warehouse operator name are associated and registered for each customer. That is, the customer master 106a has at least one record registered in which a customer code, customer name, warehouse operator code, and warehouse operator name are associated and registered. The customer code is a code for uniquely identifying a store such as a convenience store. The customer name is the name of the store. The warehouse operator code is a code for uniquely identifying the operating company that operates the warehouse or center (logistics center) owned or entrusted by the store indicated by the customer code registered in the record in which the warehouse operator code is registered. The warehouse operator name is the name of the operating company. For example, the first row of the record in the customer master 106a shown in Figure 2 shows that the name of the store identified by the customer code "T300" is "Store X". Furthermore, the first record indicates that the code "T500" is used to uniquely identify the operating company that manages the center owned or outsourced by such stores, and that the name of the operating company uniquely identified by "T500" is "Center Management." The same applies to the second record.

[0020] Figure 3 shows an example of a warehouse master 106b according to the embodiment. The warehouse master 106b is a master in which a warehouse code and warehouse name are associated and registered for each warehouse. That is, the warehouse master 106b has at least one record registered in which a warehouse code and warehouse name are associated. The warehouse code is a code for uniquely identifying a warehouse or center. The warehouse name is the name of the warehouse or center. For example, the first record in the warehouse master 106b shown in Figure 3 indicates that the name of the warehouse identified by the warehouse code "S100" is "Warehouse A". The second record indicates that the name of the warehouse identified by the warehouse code "S200" is "Warehouse B". The third record indicates that the name of the center identified by the warehouse code "S300" is "Chiba Center". The fourth record indicates that the name of the center identified by the warehouse code "S400" is "Saitama Center".

[0021] Figure 4 shows an example of a product master 106c according to the embodiment. The product master 106c is a master in which a product code and product name are associated and registered for each product. That is, the product master 106c has at least one record registered in which a product code and product name are associated. The product code is a code for uniquely identifying a product. The product name is the name of the product. For example, the first record in the product master 106c shown in Figure 4 indicates that the name of the product identified by the product code "SY01" is "Ice".

[0022] The customer master 106a, warehouse master 106b, and product master 106c are referenced by the control unit 102 and the user in various processes described later. The inventory data 106d, transfer instruction data 106e, shipping data 106f, incoming arrival schedule data 106g, transfer arrival data 106h, sales data 106i, and end-of-month receipt and payment data 106j will be described later.

[0023] The control unit 102 is a CPU (Central Processing Unit) that comprehensively controls the billing amount calculation device 100. The control unit 102 has internal memory for storing control programs such as the OS (Operating System), programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 102 includes a movement instruction input execution unit 102a, a movement shipment input execution unit 102b, a movement receipt input execution unit 102c, a sales import execution unit 102d, a receipt and payment input execution unit 102e, and an invoice issuance unit 102f.

[0024] The movement instruction input execution unit 102a executes the movement instruction input. Figure 5 is a diagram illustrating an example of the overview of the processing performed by the billing amount calculation device 100 according to the embodiment. As shown in Figure 5, the movement instruction input is a job to instruct the movement of goods 150 from a warehouse owned by the company (the company itself) to a center owned or entrusted to a store 300 during the month of the accounting year and month. Below, an example of the processing performed by each part of the control unit 102 (movement instruction input execution unit 102a, movement shipment input execution unit 102b, and movement receipt input execution unit 102c) in order to move goods 150 from the company's warehouse to the center will be described.

[0025] Figure 6 shows an example of inventory data 106d according to the embodiment. Inventory data 106d is a table in which data (records) related to the inventory of goods are registered. Each record in inventory data 106d is associated with the warehouse (warehouse name), goods (goods code), goods name, and quantity (quantity of goods). Here, at the beginning of the accounting year and month, inventory data 106d is assumed to register the actual number of goods in stock for each warehouse or center. For example, the first row of the inventory data 106d shown in Figure 6 indicates that at the beginning of the accounting year and month, the actual number of goods in stock at warehouse A, which is identified by goods code "SY01" and whose goods name is "ice," is 1000. The same applies to the other records in inventory data 106d shown in Figure 6.

[0026] The movement instruction input execution unit 102a then receives an instruction (movement instruction) from the user via the input device 112 to move the product 150 from the company's warehouse to the center. The movement instruction input execution unit 102a then registers the data based on the received movement instruction into the movement instruction data 106e.

[0027] A detailed explanation of an example of the processing performed by the movement instruction input execution unit 102a will be provided. Figure 7 shows an example of various data (movement instruction data 106e, shipping data 106f, incoming schedule data 106g, moving incoming data 106h, and updated inventory data 106d) used when moving goods 150 from the company's warehouse to the center in this embodiment. The movement instruction data 106e shown in Figure 7 is a table in which data (records) indicating the movement instruction of goods are registered. The records registered in the movement instruction data 106e are associated with the movement instruction number, row number, movement category, shipping schedule date, incoming schedule date, outgoing warehouse, receiving warehouse, goods (product code), product name, and quantity (quantity of goods to be moved). In other words, the movement instruction input execution unit 102a generates records by associating these multiple data entered by the user via the input device 112, and registers the generated records in the movement instruction data 106e.

[0028] Here, the combination of the movement instruction number and the line number is information for uniquely identifying the record in movement instruction data 106e. Therefore, the combination of the movement instruction number and the line number makes it possible to identify the record in movement instruction data 106e. The first line record of movement instruction data 106e shown in Figure 7 indicates that 500 units of product identified by product code "SY01" and product name "ice" will be moved from warehouse A to Chiba Center. The first line record of movement instruction data 106e shown in Figure 7 also indicates that the scheduled shipping date of the products to be moved from warehouse A is July 1, 2024, and the scheduled arrival date at Chiba Center is July 2, 2024. Furthermore, the combination of movement instruction number "ID001" and line number "1" registered in the first line record of movement instruction data 106e shown in Figure 7 is information for uniquely identifying this first line record. The same applies to the other records of movement instruction data 106e shown in Figure 7.

[0029] Then, the movement and shipment input execution unit 102b executes the movement and shipment input. The movement and shipment input is a job to ship goods 150 from the company's warehouse to the distribution center during the month of the accounting year and month. The movement and shipment input execution unit 102b sends the movement instructions indicated by each record registered in the movement instruction data 106e by the movement instruction input execution unit 102a to the company's warehouse registered as the outgoing warehouse for each record. The company's warehouse then ships the goods based on the movement instructions.

[0030] The shipping data 106f shown in Figure 7 is a table in which data (records) related to shipped goods are registered. When goods are shipped from the company's warehouse, the movement and shipping input execution unit 102b uses the data contained in each record registered in the movement instruction data 106e and the data related to the shipped goods to generate a record related to the shipped goods, and registers the generated record in the shipping data 106f.

[0031] Records registered in shipment data 106f are associated with the following information: shipment number, line number, transfer instruction number, line number, shipment date, outgoing warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved). Of this data, the transfer instruction number, line number, outgoing warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved) are taken from the data contained in each record registered in transfer instruction data 106e. The shipment date is the actual date the product was shipped from the company's warehouse.

[0032] Here, the combination of the shipment number and the line number is information used to uniquely identify the record in shipment data 106f. Therefore, the combination of the shipment number and the line number makes it possible to identify the record in shipment data 106f. The first line record of shipment data 106f shown in Figure 7 indicates that 500 units of product, identified by product code "SY01" and product name "Ice," were actually shipped from warehouse A on July 1, 2024, and received at the Chiba Center. Furthermore, the combination of shipment number "SK001" and line number "1" registered in the first line record of shipment data 106f shown in Figure 7 is information used to uniquely identify this first line record. The same applies to the other records of shipment data 106f shown in Figure 7.

[0033] When a new record is registered in the shipping data 106f, the mobile shipping input execution unit 102b generates a record regarding the expected arrival of goods using the data contained in the newly registered record in the shipping data 106f and the data regarding the arrival of goods, and registers the generated record in the expected arrival data 106g.

[0034] Records registered in the incoming shipment data 106g are associated with the incoming shipment number, line number, shipping number, line number, incoming shipment date, shipping warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved). Of this data, the shipping number, line number, shipping warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved) are taken from the data contained in each record registered in the shipping shipment data 106f. The incoming shipment date is taken from the incoming shipment date contained in each record registered in the transfer instruction data 106e.

[0035] Here, the combination of the incoming shipment number and the row number is information used to uniquely identify the record in incoming shipment data 106g. Therefore, the combination of the incoming shipment number and the row number makes it possible to identify the record in incoming shipment data 106g. The first row record of incoming shipment data 106g shown in Figure 7 indicates that 500 units of product, identified by product code "SY01" and product name "Ice," will be shipped from warehouse A and arrive at Chiba Center on July 2, 2024. Also, the combination of the incoming shipment number "NY001" and row number "1" registered in the first row record of incoming shipment data 106g shown in Figure 7 is information used to uniquely identify this first row record. The same applies to the other records of incoming shipment data 106g shown in Figure 7.

[0036] When a new record is registered in the incoming shipment data 106g, the moving incoming shipment input execution unit 102c executes the moving incoming shipment input. The moving incoming shipment input is a job to receive goods at the center based on the record newly registered in the incoming shipment data 106g during the accounting month. The moving incoming shipment input execution unit 102c sends an incoming shipment instruction for the goods 150 indicated by the newly registered record in the incoming shipment data 106g to the center registered as the receiving warehouse in the record. The center then receives the goods based on the incoming shipment instruction.

[0037] The moving and receiving data 106h shown in Figure 7 is a table in which data (records) related to received goods are registered. When goods arrive at the center, the moving and receiving input execution unit 102c generates a record related to the received goods using the data contained in each record registered in the incoming goods schedule data 106g and the data related to the received goods, and registers the generated record in the moving and receiving data 106h.

[0038] The records registered in the moving inbound data 106h are associated with the following information: moving inbound number, line number, scheduled inbound number, line number, receiving date, outbound warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved). Of this data, the scheduled inbound number, line number, outbound warehouse, receiving warehouse, product (product code), product name, and quantity (quantity of the product being moved) are taken from the data contained in each record registered in the scheduled inbound data 106g. The receiving date is the actual date the product arrived at the center.

[0039] Here, the combination of the moving inbound number and the row number is information used to uniquely identify the record in moving inbound data 106h. Therefore, the combination of the moving inbound number and the row number makes it possible to identify the record in moving inbound data 106h. The first row of the moving inbound data 106h shown in Figure 7 indicates that 500 units of the product, identified by product code "SY01" and product name "Ice," were shipped from warehouse A and actually arrived at the Chiba Center on July 2, 2024. Furthermore, the combination of the moving inbound number "IN001" and the row number "1" registered in the first row of the moving inbound data 106h shown in Figure 7 is information used to uniquely identify this first row of the record. The same applies to the other records in moving inbound data 106h shown in Figure 7.

[0040] When a new record is registered in the moving inbound data 106h, the moving inbound input execution unit 102c updates the inventory data 106d using the data contained in the newly registered record in the moving inbound data 106h.

[0041] For example, the incoming shipment data 106h shown in Figure 7 indicates that 1,100 units of the product identified by product code "SY01" and named "ice cream" arrived at the Chiba Center. Also, the incoming shipment data 106h shown in Figure 7 indicates that 600 units of the product identified by product code "SY01" and named "ice cream" arrived at the Saitama Center. Furthermore, the incoming shipment data 106h shown in Figure 7 indicates that 900 units of the product identified by product code "SY01" and named "ice cream" were shipped from warehouse A. Also, the incoming shipment data 106h shown in Figure 7 indicates that 800 units of the product identified by product code "SY01" and named "ice cream" were shipped from warehouse B.

[0042] Therefore, the moving and receiving input execution unit 102c updates the inventory data 106d shown in Figure 6 by reducing the quantity of goods in warehouse A by 900, reducing the quantity of goods in warehouse B by 800, increasing the quantity of goods in Chiba Center by 1100, and increasing the quantity of goods in Saitama Center by 600. As a result, as shown in Figure 7, the inventory of goods indicated in inventory data 106d is updated during the month. However, the quantity of goods updated during the month is a theoretical value, not the actual number of goods present in the company's warehouses or centers.

[0043] Returning to the explanation in Figure 5, during the month, store 300 places an order for product 150 with the center. Each time store 300 places an order for product 150 with the center, it generates store order data 160 showing the order details and sends the store order data 160 to the company. Therefore, the company can grasp the sales of product 150 from the store order data 160 during the month without waiting until the end of the month. Alternatively, store 300 may generate store order data 160 showing all orders placed during a predetermined period and send the store order data 160 to the company. However, since the sales of product 150 shown in the store order data 160 may differ from the actual sales, the company needs to calculate the difference at the end of the month and bill store 300 for the difference. Also, since the quantity of product 150 at the center obtained based on the store order data 160 may differ from the actual quantity of product 150 at the center, the company needs to bill the center's operating company at the end of the month for the amount based on the difference in quantity.

[0044] Figure 8 shows an example of store order data 160 and sales data 106i according to the embodiment. The store order data 160 is a table in which at least one record is registered, with the following associated information: order number, line number, order date, arrival date, supplier, warehouse, product (product code), product name, quantity (ordered quantity), unit price, and amount. One record corresponds to one order. The first row of the store order data 160 shown in Figure 8 indicates that store 300 ordered 500 units of a product identified by product code "SY01" and product name "ice" from the Chiba Center on July 13, 2024, and the product arrived at the store on July 14, 2024. The first row of the store order data 160 also indicates that the unit price of the product is 20 yen and the amount of the product is 10,000 yen (20 yen x 500 units).

[0045] Furthermore, the second record of the store order data 160 shown in Figure 8 indicates that store 300 ordered 503 units of the product identified by product code "SY01" and named "ice cream" from the Saitama Center on July 13, 2024, and that the products arrived at the store on July 14, 2024. The second record of the store order data 160 also indicates that the unit price of the product is 20.6 yen, and the total price of the product is 10,361 yen (20.6 yen x 503 units). Here, if the unit price of the product is 20.6 yen and the quantity is 503 units, the total price of the product would be 10,361.8 yen, but because a predetermined rounding process is performed to truncate the decimal part when calculating the product price, the total price of the product becomes 10,361 yen. The same applies to the other records of the store order data 160 shown in Figure 8.

[0046] Here, the combination of order number and line number is information used to uniquely identify a record in store order data 160. Therefore, the combination of order number and line number makes it possible to identify a record in store order data 160. The combination of order number "HC001" and line number "1" registered in the first record of store order data 160 shown in Figure 8 is information used to uniquely identify this first record. The same applies to the other records of store order data 160 shown in Figure 8.

[0047] As shown in Figures 5 and 8, the sales import execution unit 102d performs sales import. Sales import is a job to generate sales data 106i for each store 300 based on store order data 160. That is, the sales import execution unit 102d generates sales data 106i for stores 300 based on store order data 160.

[0048] The sales data 106i shown in Figure 8 is a table in which product sales are registered. When the sales import execution unit 102d receives the store order data 160, it uses the data contained in each record registered in the store order data 160 to generate records related to product sales, and registers the generated records in the sales data 106i.

[0049] Records registered in sales data 106i are associated with the following fields: sales number, line number, sales category, sales date, customer, warehouse, product (product code), product name, quantity (quantity of product), unit price, amount, and provisional sales category. Of this data, the warehouse, product (product code), product name, quantity (quantity of product), unit price, and amount are the same as those included in the records registered in store order data 160. In addition, the sales date in sales data 106i corresponds to the store arrival date included in the records in store order data 160. Furthermore, the provisional sales category field in sales data 106i is set to "1: Provisional Sales" during the month.

[0050] The first record in sales data 106i shown in Figure 8 indicates that store X received 500 units of the product identified by product code "SY01" and named "ice cream" from the Chiba Center, with the sales date being July 14, 2024. The first record in sales data 106i also indicates that the unit price of the product is 20 yen, and the total value of the product is 10,000 yen (20 yen x 500 units). The same applies to the other records in sales data 106i shown in Figure 8.

[0051] Here, the combination of sales number and row number is information used to uniquely identify a record in sales data 106i. Therefore, the combination of sales number and row number makes it possible to identify a record in sales data 106i. The combination of sales number "UR001" and row number "1" registered in the first row of sales data 106i shown in Figure 8 is information used to uniquely identify this first row of record. The same applies to the other records in sales data 106i shown in Figure 8.

[0052] Furthermore, the sales import execution unit 102d updates the inventory data 106d based on the store order data 160. For example, the store order data 160 shown in Figure 8 indicates that 500 units of the product identified by product code "SY01" and named "ice cream" were shipped from the Chiba Center. Also, the store order data 160 shown in Figure 8 indicates that 1205 units of the product identified by product code "SY01" and named "ice cream" were shipped from the Saitama Center.

[0053] Therefore, the sales import execution unit 102d updates the inventory data 106d, as shown in Figure 7, by reducing the quantity of products at the Chiba Center by 500 units and the quantity of products at the Saitama Center by 1205 units. As a result, as shown in Figure 8, the inventory of products indicated in the inventory data 106d is updated during the month. However, the updated quantity of products is a theoretical value, not the actual number of products present in the company's warehouse or center.

[0054] Next, an example of the processing performed by the billing amount calculation device 100 at the end of the month will be described. As shown in Figure 5, at the end of the month, the center generates receipt and payment data 161 and sends the receipt and payment data 161 to the company. Figure 9 shows an example of receipt and payment data 161 and end-of-month receipt and payment data 106j according to the embodiment.

[0055] The receipt and payment data 161 is a table in which at least one record is registered, each associated with the accounting year and month, target center, product (product code), end-of-month inventory quantity, and end-of-month amount. Here, the target center is the center subject to accounting. The first row of the receipt and payment data 161 shown in Figure 9 shows that the accounting year and month is July 2024, the target is the Chiba Center, the end-of-month inventory quantity of the product identified by product code "SY01" is 500 units, and the end-of-month amount is 10,000 yen. The end-of-month inventory quantity in receipt and payment data 161 is the actual inventory quantity of the product. The end-of-month amount in receipt and payment data 161 is the actual sales amount of the product for the month. The same applies to the other records in receipt and payment data 161 shown in Figure 9.

[0056] As shown in Figures 5 and 9, the receipt and payment input execution unit 102e performs receipt and payment input. Receipt and payment input is a job to generate end-of-month receipt and payment data 106j based on receipt and payment data 161. That is, the receipt and payment input execution unit 102e generates end-of-month receipt and payment data 106j based on receipt and payment data 161.

[0057] The end-of-month receipt and payment data 106j shown in Figure 9 is a table in which the results of the difference calculation process based on inventory reports are registered. When the receipt and payment input execution unit 102e receives the receipt and payment data 161, it uses the data contained in each record registered in the receipt and payment data 161 to perform a difference calculation process based on inventory reports, generates records related to the difference, and registers the generated records in the end-of-month receipt and payment data 106j.

[0058] The records registered in the end-of-month receipt and payment data 106j include the accounting year and month, target center, product (product code), balance at the end of the previous month, quantity received this month, quantity issued this month, inventory at the end of the current month, actual inventory, quantity error, amount at the end of the current month, actual amount, and amount error.

[0059] An example of a method for generating records to be registered in the end-of-month receipt and payment data 106j will be described. Figure 10 is a diagram showing an example of an input screen according to the embodiment. First, the receipt and payment input execution unit 102e displays the upper input screen (header screen) of the two input screens in Figure 10 on the output device 114, which is a monitor. Items such as line numbers that are hatched in Figure 10 are items that cannot be entered by the user, while items such as accounting year and month that are not hatched are items that can be entered by the user via the input device 112.

[0060] As shown in Figure 10, the user enters the accounting year and month, business location (business location code), customer (customer code), and center (warehouse code). The example in Figure 10 shows the case where the target accounting year and month is "July 2024", the business location to be accounted for (business location code) is "Z100", the corresponding customer (customer code) is "T300", and the corresponding center (warehouse code) is "S300".

[0061] Then, when the user presses the "New Row" button labeled "New Row" as shown in Figure 10, the receipt and payment input execution unit 102e displays the input screen (details screen) shown at the bottom of Figure 10 on the output device 114. On this input screen, the user enters three items: actual inventory quantity, actual amount, and product (product code). The user enters the data contained in the record registered in the receipt and payment data 161 into the input screen. For example, the user enters the product code "SY01" contained in the receipt and payment data 161 into the product (product code) field on the input screen. The user also enters the end-of-month inventory quantity "500" contained in the receipt and payment data 161 into the actual inventory quantity field on the input screen. Furthermore, the user enters the end-of-month amount "10000" contained in the receipt and payment data 161 into the actual amount field on the input screen.

[0062] Once these three items have been entered and the registration button labeled "Register" is pressed, the receipt and payment input execution unit 102e registers various contents in the hatched items on the detail screen, as shown in Figure 10. For example, the receipt and payment input execution unit 102e calculates the end-of-month inventory quantity of "600" by subtracting the number of items shipped out during the month from the number of items received during the month, and registers the calculated value "600" in the end-of-month inventory quantity item. The number of items received during the month is the corresponding quantity in the moving receipt data 106h within the accounting year and month. The number of items shipped during the month is the corresponding quantity in the shipping data 106f within the accounting year and month. The receipt and payment input execution unit 102e also calculates a quantity difference of "-100" by subtracting the end-of-month inventory quantity from the actual inventory quantity, and registers the calculated value "-100" in the quantity difference item. Furthermore, the receipt and payment input execution unit 102e calculates a monetary difference of "0" by subtracting from the end-of-month amount the amount obtained by adding the actual amount to the amount obtained by multiplying the quantity difference by the sales unit price, and registers the calculated value "0" in the monetary difference item.

[0063] As a result, as shown in Figure 10, the corresponding information (value) will be registered for all items on the details screen.

[0064] The receipt and payment input execution unit 102e then calculates the inventory quantity at the end of the previous month, which has not been calculated among all the items on the header screen. The inventory quantity at the end of the previous month is the "inventory quantity at the end of the current month" for the previous month, calculated using the screen shown in Figure 10, and the "inventory quantity at the end of the current month" for the previous month is carried over to the current month to become the "inventory quantity at the end of the previous month". This provides information corresponding to all items on the header screen. Figure 11 shows an example of the display of the header screen after the registration button on the details screen according to the embodiment is pressed. The receipt and payment input execution unit 102e then registers the corresponding information for all items on the header screen, as shown in Figure 11.

[0065] The receipt and payment input execution unit 102e then associates the accounting year and month, target center, product (product code), inventory quantity at the end of the previous month, quantity received in the current month, quantity issued in the current month, inventory quantity at the end of the current month, actual inventory quantity, quantity difference, amount at the end of the current month, actual amount, and amount difference to generate a record to be registered in the end-of-month receipt and payment data 106j. However, the inventory quantity at the end of the previous month corresponds to the balance at the end of the previous month in the end-of-month receipt and payment data 106j. The quantity difference corresponds to the quantity error in the end-of-month receipt and payment data 106j. The amount difference corresponds to the amount error in the end-of-month receipt and payment data 106j.

[0066] Then, the receipt and payment input execution unit 102e determines whether the quantity error is zero for each record in the end-of-month receipt and payment data 106j. If the quantity error is not zero, the receipt and payment input execution unit 102e records the sales to the center's operating company.

[0067] For example, the receipt and payment input execution unit 102e calculates the amount to be billed to the center's operating company by multiplying the quantity error by the unit price of the goods. The receipt and payment input execution unit 102e then generates a record showing the amount to be billed to the center's operating company (see the record in the 4th row of the sales data 106i shown in Figure 9) and registers the generated record in the sales data 106i. At the end of the month, "2: Confirmed Sales" is registered in the provisional sales category field of the sales data 106i.

[0068] Then, the receipt and payment input execution unit 102e calculates the monetary difference again. Specifically, the receipt and payment input execution unit 102e calculates the amount obtained by multiplying the quantity difference by the sales unit price again, and subtracts the amount obtained by adding the actual amount to the amount obtained from the amount at the end of the month to recalculate the monetary difference. Then, the receipt and payment input execution unit 102e determines whether the monetary difference is 0 or not. If the monetary difference is not 0, the receipt and payment input execution unit 102e records the sale to store 300. Figure 12 is a diagram showing another example of the display of the two input screens (header screen and detail screen) according to the embodiment. In the case of the display shown in Figure 12, the receipt and payment input execution unit 102e records the sale to store Y.

[0069] For example, the payment and receipt input execution unit 102e sets the amount difference of "1" yen as the amount to be billed to store Y. Then, the payment and receipt input execution unit 102e generates a record showing the billing amount to store Y (see the record in the 5th row of sales data 106i shown in Figure 9) and registers the generated record in sales data 106i.

[0070] Therefore, according to the billing amount calculation device 100 of this embodiment, it is possible to obtain the information necessary for billing for each billing recipient.

[0071] Returning to the explanation of Figure 5, the invoice issuing unit 102f issues an invoice 170 to the center's operating company to request payment for the amount due to the center's operating company. The invoice issuing unit 102f also issues an invoice 171 to store Y to request payment for the amount due to store Y. The invoice issuing unit 102f is an example of an issuing unit.

[0072] The billing amount calculation device 100 according to this embodiment has been described above. As described above, the sales import execution unit 102d acquires store order data 160 each time a predetermined store 300 places an order for a predetermined product with a center (predetermined supplier) during a predetermined accounting period which includes multiple days, including the quantity of the predetermined product (first quantity) and the amount of the product (first amount) determined based on the first quantity and the unit price of the predetermined product. The sales import execution unit 102d is, for example, an example of a first acquisition unit.

[0073] Furthermore, the receipt and payment input execution unit 102e has a first function of acquiring receipt and payment data 161 relating to a predetermined product on the last day of the accounting month at the center, which includes the inventory quantity of the predetermined product on the last day of the accounting month (first inventory quantity), the quantity of the predetermined product shipped from the center to a predetermined store 300 during the accounting month (second quantity), and the amount of the predetermined product determined based on the unit price of the predetermined product (second amount). The receipt and payment input execution unit 102e having the first function is, for example, an example of a second acquisition unit.

[0074] Furthermore, the receipt and payment input execution unit 102e has a second function that calculates the amount billed to the center (the center's operating company) (the first billed amount) based on the difference between the first inventory quantity and the first inventory quantity, and the unit price of the predetermined product, if the third inventory quantity (determined based on the sum of all first quantities included in all store order data 160 acquired in the accounting year and month, and the inventory quantity of a predetermined product (second inventory quantity) on the first day of the accounting year and month, differs from the first inventory quantity. The receipt and payment input execution unit 102e having the second function is, for example, an example of the first calculation unit.

[0075] Furthermore, the receipt and payment input execution unit 102e has a third function that, if the amount of a predetermined product (third amount), which is determined based on the sum of all first amounts included in all store order data 160 acquired in the accounting year and month, differs from the second amount, calculates the amount billed to a predetermined store 300 (second billing amount) based on the difference between the third amount and the second amount. The receipt and payment input execution unit 102e having the third function is, for example, an example of the second calculation unit.

[0076] Therefore, according to the billing amount calculation device 100 of this embodiment, it is possible to obtain the information necessary for billing for each billing recipient.

[0077] Furthermore, in the above-described embodiment, the third amount and the second amount differ because the first amount is obtained by multiplying the unit price of a predetermined product by the first quantity and then applying a predetermined rounding method to the fourth amount, and the second amount is obtained by multiplying the unit price of a predetermined product by the second quantity and then applying a predetermined rounding method to the fifth amount.

[0078] [2. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

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

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

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

[0082] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

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

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

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

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

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

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

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

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

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

[0092] This invention is useful, for example, in industries that have stores such as convenience stores with multiple locations as their customers. [Explanation of symbols]

[0093] 100 Billing Amount Calculation Device 102 Control Unit 102e Receipt and Payment Input Execution Unit 102f Invoice Issuance Department

Claims

1. A first acquisition unit acquires store order data that includes a first quantity of the specified product and a first amount determined based on the first quantity and the unit price of the specified product, each time a specified store places an order for a specified product with a specified supplier over a predetermined period of time including multiple days. A second acquisition unit acquires receipt and payment data relating to the specified goods on the last day of the specified period at the specified supplier, which includes the first inventory quantity of the specified goods on the last day of the specified period, and the second amount of the specified goods determined based on the second quantity of the specified goods shipped from the specified supplier to the specified store during the specified period and the unit price of the specified goods. If the sum of all the first quantities included in all the store order data acquired during the predetermined period and the third inventory quantity of the predetermined product determined based on the second inventory quantity of the predetermined product on the first day of the predetermined period differs from the first inventory quantity, the first calculation unit calculates the first invoice amount to the predetermined supplier based on the difference between the second inventory quantity and the first inventory quantity and the unit price of the predetermined product, If the third amount for the specified product, which is determined based on the sum of all the first amounts included in all the store order data acquired during the predetermined period, differs from the second amount for the specified product, a second calculation unit calculates a second billing amount to the specified store based on the difference between the third amount and the second amount. A billing amount calculation device equipped with the following features.

2. The first amount is obtained by multiplying the unit price by the first quantity and applying a predetermined rounding method to the fourth amount, and the second amount is obtained by multiplying the unit price by the second quantity and applying the predetermined rounding method to the fifth amount, and as a result, the third amount and the second amount are different. The billing amount calculation device according to claim 1.

3. The billing amount calculation device according to claim 1, further comprising an issuing unit that issues a first invoice to the predetermined supplier for the first billing amount and a second invoice to the predetermined store for the second billing amount.

4. A method for calculating the billing amount performed by a computer, A first acquisition step involves acquiring store order data, which includes a first quantity of the specified product and a first amount determined based on the first quantity and the unit price of the specified product, each time a specified store places an order for a specified product with a specified supplier over a predetermined period of several days. A second acquisition step of acquiring receipt and payment data relating to the specified goods at the specified supplier on the last day of the specified period, which includes the first inventory quantity of the specified goods on the last day of the specified period, and the second amount of the specified goods determined based on the second quantity of the specified goods shipped from the specified supplier to the specified store during the specified period and the unit price of the specified goods, If the sum of all the first quantities included in all the store order data acquired during the predetermined period and the third inventory quantity of the predetermined product determined based on the second inventory quantity of the predetermined product on the first day of the predetermined period differs from the first inventory quantity, the first calculation step is to calculate the first invoice amount to the predetermined supplier based on the difference between the second inventory quantity and the first inventory quantity and the unit price of the predetermined product. If the third amount for the specified product, which is determined based on the sum of all the first amounts included in all the store order data acquired during the predetermined period, differs from the second amount for the specified product, a second calculation step is performed to calculate a second billing amount to the specified store based on the difference between the third amount and the second amount. A method for calculating the billing amount, including the method itself.

5. On the computer, A first acquisition process that, over a predetermined period including multiple days, acquires store order data each time a predetermined store places an order for a predetermined product with a predetermined supplier, including a first quantity of the predetermined product and a first amount determined based on the first quantity and the unit price of the predetermined product. A second acquisition process for acquiring receipt and payment data relating to the specified goods at the specified supplier on the last day of the specified period, which includes the first inventory quantity of the specified goods on the last day of the specified period, and the second amount of the specified goods determined based on the second quantity of the specified goods shipped from the specified supplier to the specified store during the specified period and the unit price of the specified goods. If the sum of all the first quantities included in all the store order data acquired during the predetermined period and the third inventory quantity of the predetermined product determined based on the second inventory quantity of the predetermined product on the first day of the predetermined period differ from the first inventory quantity, a first calculation process is performed to calculate the first invoice amount to the predetermined supplier based on the difference between the second inventory quantity and the first inventory quantity and the unit price of the predetermined product. If the third amount for the specified product, which is determined based on the sum of all the first amounts included in all the store order data acquired during the predetermined period, differs from the second amount for the specified product, a second calculation process is performed to calculate a second billing amount to the specified store based on the difference between the third amount and the second amount. A program to calculate the billing amount for execution.

Images