JP2020035275A - Data creation device, data creation method, and data creation program - Google Patents

Abstract

To provide a data creation device or the like that can create credit data for FC stores of FC headquarters and debt data for the FC stores of the FC headquarters, even if a person in charge of the FC headquarters does not determine, by automatically allocating the sales amount of the headquarters to the amount of receivables or the setoff amount in the debt.SOLUTION: In the present embodiment, (1) if the contract form in a store contract master linked to a store code in sales data is a billing method, the device creates credit data including billing statement data having a store code in the sales data and an amount in the sales data associated with the store code. Further, (2) if the contract form in the store contract master linked to the store code in the sales data is a settlement method, the device creates debt data including debt statement data having the store code in the sales data and the total amount in the over-the-counter sales data associated with the store code as well as setoff statement data having the store code in the sales data and the setoff amount in which the amount in the sales data associated with the store code is recorded as a negative value.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a data creation device, a data creation method, and a data creation program.

  Patent Literature 1 states that “the first store, the second store, the third store, to the N-th store are operated by a company A in a direct management / FC form, etc. Each of these stores has a POS register and a deposit machine. Is installed. ”(See paragraph 0013 and the like in Patent Document 1), and further,“ POS total data and depositing machine data are collected from the POS registers and the depositing machine of each of the first to Nth stores. Upon receipt (step S300), data editing processing is performed in step S302, and POS register comparison data and depositing machine comparison data are generated, where the POS register comparison data is a cash sales amount extracted from the POS total data. When the change expenditure, expense payment, etc. are recorded, the amount obtained by subtracting the recorded amount from the cash sales amount is the POS register comparison data. That. "To be disclosed (refer to paragraph 0023 of Patent Document 1).

JP 2003-308375 A

  As described above, in the field of managing the sales amount of each FC store in a franchise (hereinafter sometimes referred to as “FC”) contract, there have been the following problems conventionally. In other words, as shown in FIG. 2, in the contract method in the FC contract, the store sales amount, which is the sales amount at the FC store, is managed by the store, and the head office sales amount, which is the sales amount of the head office of the FC contract, to the store. A method (a billing method) in which the headquarters claims the amount (food costs, etc.) to the store as a receivable, and, as shown in FIG. There is a method (payment method) in which the headquarters pays the amount obtained by subtracting (in other words, offsetting) the sales amount of the headquarters (food costs etc.) from the sales amount as a debt to the store. Which of the above-mentioned contract methods is adopted differs depending on each FC store. Generally, when the corporation is the owner of the FC store, the credit method is high, so the billing method is adopted, and the individual uses the FC store. If you are the owner, the credit method is low, so the settlement method is adopted.

  Here, when registering the sales amount of the headquarters (food costs, etc.) on the system, if the contract method with the FC store is a billing method, the person in charge of the FC headquarters registers the amount as a receivable amount. On the other hand, if the contract method with the FC store is a settlement method, it is necessary to make a decision to register it as an offset amount in the debt, so errors are likely to occur and it will also delay the monthly settlement There was a problem.

  The present invention has been made in view of the above-mentioned problems, and automatically allocates the sales amount of the headquarters to the amount of the receivables or the offset amount in the debt without the judgment of the person in charge of the FC headquarters. It is an object of the present invention to provide a data creation device, a data creation method, and a data creation program capable of creating credit data, which is data of a bond to an FC store at a headquarters, and debt data, which is data of a debt to a FC store at a FC headquarters.

In order to solve the above-described problems and achieve the object, a data creation device according to the present invention is a data creation device including a control unit and a storage unit, wherein the storage unit stores sales at a store under a franchise contract. A store sales amount, which is an amount, is managed at the store, and the headquarters sales amount, which is the sales amount of the headquarters of the franchise contract, to the store is a category that means that the headquarters claims the store as receivables. Deposit all the billing section and the store sales amount to the headquarters, and deduct the headquarters sales amount from the deposited store sales amount and settle the amount paid by the headquarters as a debt to the store. A store master including any one of the settlement classes, store identification data for identifying the store, store identification data and Head office sales data, which is data on sales of the head office to the store, including sales amounts, and store sales data, which is data on sales at the stores, including store identification data and store sales amounts, are stored. And the control unit includes:
When the division in the store master associated with the store identification data in the headquarters sales data is the billing division, the headquarters sales data associated with the store identification data and the store identification data in the headquarters sales data Claim data creation means for creating the claim data including the claim statement data having the head office sales amount, and the section in the shop master associated with the shop identification data in the head office sales data. In the case of the settlement section, in the debt statement data and the headquarters sales data, the store identification data in the headquarters sales data and the total amount of the store sales in the store sales data associated with the store identification data are included. The above-mentioned store identification data and the amount obtained by subtracting the head office sales amount from the head office sales data linked to the store identification data And debt data creating means for creating debt data as the debt including offset statement data having an offset amount that is an amount for offsetting the total amount in the debt statement data. Features.

  Further, in the data creation device according to the present invention, the headquarters sales data further includes a recording date that is a date on which the headquarters sales amount is recorded, and the store sales data is a date when sales at the store occur. The store master further includes a sales date, the store master further includes an application target period that is a period to which the classification is applied, and the store identification data in the headquarters sales data is linked, and the accounting date belongs to the store master data. If the section in the store master associated with the applicable period is the billing section, the receivables data creating means creates the receivables data, and is associated with the store identification data in the headquarters sales data, and In the case where the section in the store master associated with the applicable period to which the accounting date belongs is the settlement section, the debt data creating unit belongs to the applicable period. To create the debt data with the sum of the shop sales amount in the store sales data that attach the sales date and the string as the total amount, and said.

  Further, in the data creation device according to the present invention, the control unit may be configured to pay the sum of the total amount in the debt statement data and the offset amount in the offset statement data as debt to the store of the headquarters. And a payment processing execution unit for executing the payment processing.

  Further, the data creation device according to the present invention is characterized in that the headquarters sales amount is a royalty to be paid by the store to the headquarters in the franchise agreement or an expense of what the headquarters provided to the store. And

  Further, a data creation method according to the present invention is a data creation method executed by an information processing apparatus including a control unit and a storage unit, wherein the storage unit stores the sales amount of the store under the franchise contract. The amount is managed in the store, the headquarters of the franchise contract is the sales amount of the headquarters to the store, the headquarters sales amount is a classification that means that the headquarters claims the store as receivables, the claim classification and the store Any of the settlement divisions, which means that the headquarters pays all the sales amounts to the headquarters and deducts the headquarters sales amount from the deposited store sales amount to the store as an obligation. A store master including one of the categories and the store identification data for identifying the store, the store identification data and the head office sales amount The headquarters sales data, which is data on sales of the headquarters to the store, and store sales data, which is data on sales at the store, including store identification data and store sales amount, are stored. When the section in the store master associated with the store identification data in the headquarters sales data is the billing section, the store identification data and the store identification data in the headquarters sales data are executed by the control unit. Claim data creation step of creating claim data as the claim including claim statement data having the head office sales amount in the head office sales data, and the store identification data in the head office sales data If the section in the store master is the settlement section, the store identification data and the store identification data in the headquarters sales data Debt statement data having the total amount of the store sales amounts in the store sales data associated therewith, the store identification data in the headquarters sales data, and the headquarters sales amount in the headquarters sales data associated with the store identification data Debt data creation step of creating debt data as the debt including offsetting statement data having an offset amount that is an amount for recording the total amount in the debt statement data as a negative amount And the following.

  Further, a data creation program according to the present invention is a data creation program to be executed by an information processing apparatus including a control unit and a storage unit, wherein the storage unit stores a sales amount in a store under a franchise contract. The sales division is managed by the store, and the headquarters sales amount, which is the sales amount of the headquarters of the franchise contract to the store, is a classification that means that the headquarters claims the store as receivables. Deposit all store sales to the headquarters, deduct the headquarters sales amount from the deposited store sales amount and settle the amount that means that the headquarters pays the store as a debt. A store master including any one of the sections and store identification data for identifying the store, and store identification data Headquarters sales data, which is data on sales of the headquarters to the store, including store sales amounts, and store sales data, which is data on sales at the stores, including store identification data and store sales amounts, are stored. If the section in the store master associated with the store identification data in the head office sales data is the billing section to be executed by the control unit, the store identification in the head office sales data A credit data creating step for creating claim data as the claim including data on a claim having the head office sales amount in the head office sales data associated with the shop identification data; and the store in the head office sales data If the section in the store master associated with the identification data is the settlement section, the store identification data in the headquarter sales data is used. Debt statement data having the data and the total amount of the store sales in the store sales data associated with the store identification data, and the head office sales associated with the store identification data and the store identification data in the head office sales data Debt data as the debt including offset statement data having an offset amount that is an amount obtained by subtracting the head office sales amount in the data and that is an amount for offsetting the total amount in the debt statement data And a debt data creation step of creating the debt data.

  According to the present invention, the sales amount of the headquarters is automatically allocated to the amount of the receivables or the offset amount in the debts without the judgment of the person in charge of the FC headquarters. There is an effect that debt data, which is data of debt to the FC store of the FC headquarters, can be created.

FIG. 1 is a block diagram illustrating an example of the configuration of the data creation device. FIG. 2 is a diagram illustrating an example of an image of a billing method. FIG. 3 is a diagram illustrating an example of an image of the settlement method. FIG. 4 is a diagram illustrating an example of an outline of a process according to the present embodiment. FIG. 5 is a diagram illustrating an example of details of a process according to the present embodiment.

  Hereinafter, embodiments of a data creation device, a data creation method, and a data creation program will be described in detail with reference to the drawings. The present invention is not limited by the embodiment.

[1. Overview]
FC contracts are roughly divided into the following two contract systems. First, as shown in FIG. 2, the FC store owner manages the store sales, and the FC headquarters invoices the FC store owner for royalties, delivered food costs, etc. for each closing date. There is. The billing method is often adopted in contracts with high-credit corporate owners. On the other hand, as shown in Fig. 3, all store sales are deposited with the FC headquarters, and on each closing day, the amount obtained after deducting royalties and delivered food costs is paid to the owner of the FC store. There is a method. The settlement method is often adopted in contracts with low-credit private owners.

  Here, in the past, depending on the type of contract with the FC store, if the result of shipping foodstuffs to the FC store and the accounting of expenses from the FC headquarters were viewed from the FC headquarters, the amount of receivables would increase, or the offset amount in the debt and It is necessary to divide the registration screen or the input screen in consideration of the type of contract method with the FC store, even if the registration and inputting actions of food shipment results and expense accounting are the same. Was. For this reason, there has been a problem that mistakes frequently occur, errors occur in materials for owners of FC stores, and monthly settlement is delayed.

  Therefore, in the present embodiment, for example, the person in charge of the FC headquarters determines whether to register the material costs and the expenses for the FC store for the delivery to the FC store as the amount of the receivable or the offset amount in the debt. In addition, it is possible to automatically allocate the food cost and the cost to the amount of the receivable or the offset amount in the debt. Further, in the present embodiment, for example, even when the owner of the franchise store is changed during the month, appropriate distribution according to the contract method with the owner before and after the change can be performed. Hereinafter, a specific configuration and operation will be described.

[2. Constitution]
An example of the configuration of the data creation device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the data creation device 100.

  The data creation device 100 is a commercially available desktop personal computer. Note that the data creation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable personal computer such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer. It may be an information processing device.

  The data creation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the data creation device 100 are communicably connected via an arbitrary communication path.

  The communication interface unit 104 communicably connects the data creation 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 another device via a communication line. Here, the network 300 has a function of connecting the data creation 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). Note that data of various masters and the like described below may be stored in the server 200, for example.

  An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that realizes a pointing device function in cooperation with a mouse can be used. In the following, the output device 114 may be described as a monitor 114 and the input device 112 may be described as a keyboard 112 or a mouse 112.

  The storage unit 106 stores various databases, tables, files, and the like. In the storage unit 106, a computer program for cooperating with an OS (Operating System) and giving instructions to a CPU (Central Processing Unit) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, and the like can be used.

  The storage unit 106 includes, for example, a store contract master 106a as a store master, sales data 106b as head office sales data, over-the-counter sales data 106c as store sales data, receivables data 106d, and debt data 106e. ing.

  As shown in FIG. 5, the store contract master 106a manages, for example, the store sales amount, which is the sales amount at the store in the franchise contract, at the store, and the head office, which is the sales amount of the headquarters of the franchise contract, to the store. The head office bills the store as receivables to the store as a claim category (a billing method), and deposits all the store sales amounts into the head office. Identify the store and one of the payment classes (payment method), which is a classification meaning that the headquarters pays the store as a debt to the store after deducting the sales amount. Identification data (store code and store name) to be used, and the applicable period (the contract period) The use start date), the owner identification data for identifying the owner of the shop (owner code and owner name), and the like.

  The sales data 106b is data on sales of the headquarters to the store. As shown in FIG. 5, the sales data 106b includes, for example, an accounting date, which is the date on which the head office sales amount is estimated, the store identification data (store code and store name), and sales of the store to the store. Product identification data (product code and product name) for identifying the product, the number of sales of the product, the unit sales price (unit price) of the product, the head office sales amount (amount), and the head office sales amount Includes consumption tax and etc.

  The headquarters sales amount is, for example, a royalty to be paid by the store to the headquarters in the franchise contract or a cost of what the headquarters provided to the store. The costs include, for example, costs of ingredients and raw materials that the headquarters has wholesaled to the store, and usage fees of the system provided by the headquarters to the store.

  The store sales data 106c is data relating to sales at the store. As shown in FIG. 5, the over-the-counter sales data 106c includes, for example, a sales date, which is the date when the sales at the store occurred, the store identification data (store code and store name), and a product sold at the store. Product identification data (product code and product name) for identification, the number of sales of the product, the sales unit price (unit price) of the product, the store sales amount (amount), and the consumption tax of the store sales amount , Etc.

  The receivable data 106d is receivable data created by a receivable data creation unit 102a, which will be described later, based on the sales data 106b when the category (contract form) in the store contract master 106a is the billing category (billing method). . As shown in FIG. 5, the bond data 106d has billing specification data (in FIG. 5, three billing specification data with SK1 to SK3).

  The debt data 106e is created based on the sales data 106b and the over-the-counter sales data 106c by the debt data creation unit 102b described later when the classification (contract form) in the store contract master 106a is the settlement class (payment method). Debt data. As shown in FIG. 5, the debt data 106e is created based on debt statement data (in FIG. 5, two debt statement data to which SM3 to SM4 are attached) created based on over-the-counter sales data 106c and sales data 106b. (In FIG. 5, two offset specification data labeled SM1 and SM2).

  The control unit 102 is a CPU or the like that controls the data creation device 100 as a whole. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various types of information processing based on the stored programs. Execute.

  The control unit 102 functionally conceptually includes, for example, (1) when the section in the store master associated with the store identification data in the headquarter sales data is the billing section, A credit data creation unit 102a as claim data creation means for creating claim data as the claim including the billing statement data having the shop identification data and the head office sales amount in the head office sales data associated with the shop identification data; (2) When the section in the store master associated with the store identification data in the headquarters sales data is the settlement section, the store identification data in the headquarters sales data is associated with the store identification data. Debt statement data having the total amount of the store sales in the store sales data and the store identification data in the headquarters sales data and Offset statement data having an offset amount, which is an amount obtained by subtracting the head office sales amount in the head office sales data associated with the pavement identification data and which is an amount for offsetting the total amount in the debt statement data. (3) calculating the sum of the total amount in the debt detail data and the offset amount in the offsetting detail data; and (3) a debt data creating unit 102b as debt data creating means for creating debt data as the debt. And a payment processing execution unit 102c as payment processing execution means for executing processing for paying the headquarters as a debt to the store.

  When the contract form in the store contract master 106a associated with the store identification data in the sales data 106b is a billing method, the receivable data creation unit 102a associates the store identification data in the sales data 106b with the store identification data. Claim data 106d is created as a claim including billing statement data having the head office sales amount in the sales data 106b.

  The receivable data creation unit 102a associates the receivable data 106d with the store identification data in the sales data 106b and, when the contract form in the store contract master 106a associated with the applicable period to which the accounting date belongs is a billing method. May be created.

  When the contract form in the store contract master 106a associated with the store identification data in the sales data 106b is a settlement method, the debt data creation unit 102b stores the store identification data in the sales data 106b and the store associated with the store identification data. Debt statement data having the total amount of store sales in the sales data 106c, store identification data in the sales data 106b, and the head office sales amount in the sales data 106b associated with the store identification data as a minus amount. Then, the debt data 106e as the debt including offset statement data having an offset amount which is an amount for offsetting the total amount in the debt statement data is created.

  If the contract form in the store contract master 106a associated with the store identification data in the sales data 106b and associated with the applicable period to which the accounting date belongs is the settlement method, the debt data creating unit 102b And the debt data 106e having the sum of the store sales amounts in the store sales data 106c associated with the sales date belonging to.

  The payment process execution unit 102c executes a process of paying the sum of the total amount in the debt statement data and the offset amount in the offset statement data as debt to the store at the headquarters.

[3. Outline of processing]
In this section, an outline of the processing according to the present embodiment will be described with reference to FIG.

  When sales from the headquarters to the store occur, salespeople are input by a person in charge of the headquarters, and sales data 106b is created. On the other hand, when sales at the store occur, store sales input is performed by a person in charge of the store, and store sales data 106c is created.

  Then, referring to the store contract master 106a, the distribution to the receivables or payables is automatically performed according to the contract method with the store as described below.

  When the contract method with the store is a billing method, the credit data 106d is created based on the sales data 106b. As described above, in the case of the billing method, the sales from the headquarters to the store increase the receivables as viewed from the headquarters.

  When the contract method with the store is a settlement method, debt data 106e is created based on the sales data 106b and the in-store sales data 106c. Specifically, all of the over-the-counter sales amounts in the over-the-counter sales data 106c are recorded as debts as deposits to be returned to the store. Further, the sales amount from the headquarters to the store in the sales data 106b is negatively recorded as an offset amount to be subtracted from the deposit. Then, the sum of the deposit and the offset amount is the amount finally returned by the headquarters to the store.

[4. Processing details]
In this item, details of the processing according to the present embodiment will be described with reference to FIG. In the following description, it is assumed that the contents of the store contract master 106a, the sales data 106b, and the in-store sales data 106c are as shown in FIG.

  In FIG. 5, the detailed data of the store contract master 106a is denoted by TK1-4, the detailed data of the sales data 106b is denoted by U1-5, and the detailed data of the over-the-counter sales data 106c is denoted. The data is denoted by TU 1 to 90, the detailed data of the credit data 106d is denoted by SK1 to 3, and the detailed data of the debt data 106e is denoted by SM 1 to 4. These symbols are given for the sake of explanation and are not data and information included in each data.

[4-1. Creation of credit data for franchise store B]
First, creation of the credit data 106d for the B store, which is an FC store, will be described.

  Referring to the store contract master 106a, the contract form associated with the store code: T101 and the store name: B store in the statement data U3 is a billing method. In this case, the receivables data creation unit 102a creates the invoice details data SK2 based on the details data U3. Specifically, as shown in the billing statement data SK2, the receivable data creation unit 102a links the shop code: T101 and the shop name: B shop and the shop code: T101 and the shop name: B shop in the statement data U3. Other information in the detailed data U3 attached (accounting date: April 1, 2018, product code: S100, product name: flour 10 kg, sales volume: 3, unit price: 10,000, amount: 30,000, and consumption tax: 2,400), The billing statement data SK2 including the following is created.

  In a similar manner, the receivables data creating unit 102a creates the invoice details data SK3 based on the details data U4.

  As described above, the bond data creating unit 102a creates the bond data 106d including the billing statement data SK2 and the billing statement data SK3 as the claim data for the B store, which is an FC store, as shown in the claim data 106d. .

[4-2. Creation of debt data for C store, a franchise store]
Next, creation of the debt data 106e for the C store, which is an FC store, will be described.

  Referring to the store contract master 106a, the contract form associated with the store code: T102 and the store name: C store in the statement data U5 is a settlement method. In this case, the debt data creation unit 102b creates debt statement data SM4 based on the statement data TU61 to TU90. Specifically, as shown in the debt statement data SM4, the debt data creation unit 102b links the shop code: T102 and the shop name: C shop in the statement data U5 with the shop code: T102 and the shop name: C shop. Information based on other information in the attached detail data TU61 to 90 (Accounting date: April 30, 2018, product code: Z999, product name: deposit, quantity: 1, unit price: 600,000, amount: 600,000, and consumption tax: 48,000). As the accounting date, “2018/4/30”, which is the end date of the month, as in this example, may be set, or a contract switching date may be set. As the product code and the product name, the sales in the detailed data TU61 to TU90 are recorded as deposits, and thus “Z999” and “deposit” are set, respectively. As the unit price and the amount, 600,000 (30 items of 20,000) which is the total amount of the sales amount 20,000 in each of the item data TU61 to TU90 is set. The 600,000 is the amount that Store C once deposits in the FC headquarters.

  On the other hand, the debt data creation unit 102b creates offset statement data SM2 based on the statement data U5. Specifically, as shown in the offset statement data SM2, the debt data creation unit 102b links the shop code: T102 and the shop name: C shop in the statement data U5 with the shop code: T102 and the shop name: C shop. Information based on other information in the attached detail data U5 (Accounting date: April 1, 2018, Product code: S100, Product name: Flour 10kg, Quantity: 5, Unit price: -10,000, Amount: -50,000, and consumption tax: -4,000) to generate the offsetting detail data SM2. As the unit price, −10,000, which is a minus amount of the unit price 10,000 in the detailed data U5, is set. As the amount of money, -50,000 which is the amount obtained by subtracting the amount of money 50,000 in the detailed data U5 is set. The -50,000 is an offset amount to be subtracted from the total amount of 600,000 when returning the total amount of 600,000 described in the previous paragraph to the C store.

  As described above, as shown in the debt data 106e, the debt data creating unit 102b creates the debt data 106e including the debt statement data SM4 and the offset statement data SM2 as the debt data for the C store that is the FC store. . Subsequently, a payment process may be performed as described in the next paragraph.

  The payment processing execution unit 102c executes the payment processing as 550,000, which is the sum of the total amount of 600,000 in the debt detail data SM4 and the offset amount -50,000 in the offset detail data SM2, as the debt to the store C of the FC headquarters (that is, the payment processing) Will be returned).

[4-3. Creation of receivables and debt data for FC store A]
Finally, creation of the credit data 106d and the debt data 106e for the FC store A will be described. Note that, in this example, as shown in the store contract master 106a, the owner switches from corp. Corporation OO to individual Hanako Yamada on April 21, 2018. Even in such a case, according to the data creating apparatus 100 according to the present embodiment, as described below, when wholesale is performed to the corporation XX during the period in which the contract is made with the corporation XX, The sales amount of the headquarters can be distributed as the amount of receivables to be claimed to XX Corporation. On the other hand, the sales amount at the headquarters for wholesale to Hanako Yamada during the contract with Hanako Yamada is to offset the sales that are once deposited from Hanako Yamada and returned as debt. Can be allocated as the offset amount.

(1) Creation of Claim Data Referring to the store contract master 106a, the contract form associated with the store code: T100 and the store name: A store in the detailed data U1 includes the billing method included in the detailed data TK1 and the detailed data TK2. Since it is a settlement method, it is not possible to specify which contract method. Here, the accounting date 2018/4/1 in the detailed data U1 belongs to the applicable period of the detailed data TK1 (from 2018/1/1 to 2018/4/20). Therefore, the contract form associated with the detail data U1 is a billing method that is the contract form of the detail data TK1. Hereinafter, the detailed description is omitted, but in the same manner as described in [4-1], the receivables data creating unit 102a creates the invoice details data SK1 based on the details data U1.

  As described above, as shown in the credit data 106d, the credit data creation unit 102a sets the credit data including the billing statement data SK1 as the credit data for the period in which XX of the FC store A is the owner. Create 106d.

(2) Creation of Debt Data Referring to the store contract master 106a, the contract form associated with the store code: T100 and the store name: A store in the detailed data U2 includes the billing method included in the detailed data TK1 and the detailed data TK2. Since it is a settlement method, it is not possible to specify which contract method. Here, the accounting date 2018/4/21 in the detail data U2 belongs to the applicable period of the detail data TK2 (after April 21, 2018). In this case, the debt data creation unit 102b creates debt statement data SM3 based on the statement data TU21 to TU30. Specifically, as shown in the debt statement data SM3, the debt data creation unit 102b links the shop code: T100 and the shop name: A shop in the statement data U2 with the shop code: T100 and the shop name: A shop. Information based on other information in the attached detail data TU21-30 (Accounting date: April 30, 2018, Product code: Z999, Product name: Deposit, Quantity: 1, Unit price: 200,000, Amount: 200,000, and consumption tax: 16,000) is created. The unit price and the amount of money are 200,000 (10 items of 20,000), which is the sum of the sales amount 20,000 in each of the item data TU21 to 30 having the sales date belonging to the applicable period of the item data TK2 (after April 21, 2018). Minute) is set. The 200,000 is the amount that Hanako Yamada once deposits at the FC headquarters.

  On the other hand, although detailed description is omitted, in the same manner as described in [4-2], the debt data creating unit 102b creates the offset statement data SM1 based on the statement data U2. The -200,000 included in the offset specification data SM1 is an offset amount to be subtracted (offset) from the total 200,000 when returning the total 200,000 described in the previous paragraph to Hanako Yamada.

  As described above, as shown in the debt data 106e, the debt data creation unit 102b sets the debt statement data SM3 and the offset statement data SM1 as the debt data for the period in which Hanako Yamada of the FC store is the owner. Is created.

  Here, since the sum of the total amount of 200,000 in the debt statement data SM3 and the offset amount of -200,000 in the offset statement data SM1 is 0 yen, the payment (return) to Hanako Yamada of the FC headquarters is 0 yen. .

[4-4. Summary]
As described above, with reference to the credit data 106d created through the processes of [4-1] to [4-3], the total amount of the credits held by the FC headquarters is the amount and consumption in each of the billing statement data SK1 to SK3 The sum of all taxes (amount 100,000 + consumption tax 8,000 + amount 30,000 + consumption tax 2,400 + amount 20,000 + consumption tax 1600 = 162,000 = 162,000. Also, [4-1] to [4-3] ], The total amount of debt held by the FC headquarters is the sum of the amount and consumption tax in each of the offset statement data SM1-2 and the debt statement data SM3-4. Value (amount-200,000 + consumption tax-16,000 + amount-50,000 + consumption tax-4,000 + amount 200,000 + consumption tax 16,000 + amount 600,000 + consumption tax 48,000 = 594,000

  As described above, according to the data creating apparatus 100 according to the present embodiment, the sales amount of the headquarters is automatically allocated to the amount of the receivables or the offset amount in the debts without the judgment of the person in charge of the FC headquarters, Further, it is possible to create the credit data 106d, which is the data of the credit to the FC store of the FC headquarters, and the debt data 106e, which is the data of the debt to the FC store of the FC headquarters. For this reason, for example, as in the past, the person in charge of the FC headquarters determines whether the headquarters sales amount will be an increase in receivables or an offset amount in debts, and a registration screen or input of the headquarters sales amount will be made. Since there is no need to perform screen division work, it is possible to prevent errors due to the work, errors in data for owners of FC stores, delays in monthly settlement, and the like.

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

  For example, among the processes described in the embodiment, all or some of the processes described as being performed automatically can be manually performed, or all of the processes described as being performed manually can be performed. Alternatively, a part thereof can be automatically performed by a known method.

  In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions of each processing, screen examples, and database configurations shown in the present specification and drawings are not described unless otherwise specified. Can be changed arbitrarily.

  Further, regarding the data creating apparatus 100, the illustrated components are functionally conceptual, and do not necessarily need to be physically configured as illustrated.

  For example, all or any part of the processing functions provided in the data creation apparatus 100, in particular, each processing function performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment. 100 is read mechanically. That is, in a storage unit such as a ROM or a hard disk drive (HDD), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. The computer program is executed by being loaded into the RAM, and forms a control unit in cooperation with the CPU.

  Further, this computer program may be stored in an application program server connected to the data creating apparatus 100 via an arbitrary network, and it is also possible to download all or part of the computer program as needed. is there.

  Further, a program for executing the processing described in the present embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registered). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical, Digital, Digital and Digital), DVD (Digital, Digital and Digital) Any "portable physical media It is intended to include.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as a source code or a binary code. Note that the “program” is not necessarily limited to a single program, but achieves its function in cooperation with a program that is distributed as a plurality of modules or libraries or a separate program represented by an OS. Including things. It should be noted that a known configuration and procedure can be used for a specific configuration and reading procedure for reading a recording medium in each apparatus described in the embodiment, an installation procedure after reading, and the like.

  Various databases and the like stored in the storage unit are storage devices such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. It stores programs, tables, databases, files for web pages, and the like.

  Further, the data creation device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device to which an arbitrary peripheral device is connected. Further, the data creation device 100 may be realized by installing software (including a program or data) for realizing the processing described in the present embodiment in the device.

  Furthermore, the specific form of the distribution / integration of the apparatus is not limited to the illustrated one, and all or a part of the apparatus may be functionally or physically Can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

  INDUSTRIAL APPLICABILITY The present invention is useful, for example, in an industry in which multiple stores are developed under an FC contract.

Reference Signs List 100 data creation device 102 control unit
102a Credit data creation unit
102b Debt data creation unit
102c Payment processing execution unit 104 Communication interface unit 106 Storage unit
106a Store contract master
106b Sales data
106c Over-the-counter sales data
106d receivables data
106e Debt data 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

A data creation device including a control unit and a storage unit,
In the storage unit,
The store manages the store sales amount, which is the sales amount at the store in the franchise agreement, at the store, and the headquarters claims the store sales amount, which is the sales amount of the headquarters of the franchise contract, to the store as receivables. The headquarters as a liability to the store, by depositing the billing division and the store sales amount, which is a classification meaning that, with the headquarters, and subtracting the headquarters sales amount from the deposited store sales amount and adjusting the amount. A store master including any one of the settlement classes, which is a class that means to pay, and store identification data for identifying the store,
Headquarters sales data, which is data on sales of the headquarters to the store, including store identification data and headquarters sales amounts,
Including store identification data and store sales amount, store sales data that is data on sales at the store,
Is stored,
The control unit includes:
When the division in the store master associated with the store identification data in the headquarters sales data is the billing division, the headquarters sales data associated with the store identification data and the store identification data in the headquarters sales data Claim data creating means for creating claim data as the claim including claim detail data having the head office sales amount,
When the section in the store master associated with the store identification data in the headquarters sales data is the settlement section, the store identification data in the headquarters sales data and the store sales data associated with the store identification data. Debt statement data having the total amount of the store sales amount in the above and the store identification data in the headquarters sales data and the amount obtained by subtracting the headquarter sales amount in the headquarters sales data associated with the store identification data Debt data creating means for creating debt data as the debt including offsetting detail data having an offset amount that is an amount for offsetting the total amount in the debt detail data,
Having,
A data creation device characterized by the following. The headquarters sales data further includes a recording date that is a date on which the headquarters sales amount is recorded,
The store sales data further includes a sales date that is a date when sales at the store occur,
The store master further includes an application period that is a period to which the classification is applied,
When the section in the store master associated with the store identification data in the headquarters sales data and associated with the applicable period to which the accounting date belongs is the billing section, Create receivables data,
When the section in the store master associated with the store identification data in the headquarters sales data, and associated with the applicable period to which the accounting date belongs, is the settlement section, the debt data creating means includes Creating the debt data having the sum of the store sales amounts in the store sales data associated with the sales dates belonging to the applicable period as the total amount,
The data creation device according to claim 1, wherein: The control unit includes:
Payment processing executing means for executing a process of paying the sum of the total amount in the debt statement data and the offset amount in the offset statement data as a debt to the store of the headquarters,
The data creation device according to claim 1, wherein: The headquarters sales amount is a royalty to be paid by the store to the headquarters in the franchise agreement or a cost of what the headquarters provided to the store.
The data creation device according to any one of claims 1 to 3, wherein: A data creation method executed by an information processing device including a control unit and a storage unit,
In the storage unit,
The store manages the store sales amount, which is the sales amount at the store in the franchise agreement, at the store, and the headquarters claims the store sales amount, which is the sales amount of the headquarters of the franchise contract, to the store as receivables. The headquarters as a liability to the store, by depositing the billing division and the store sales amount, which is a classification meaning that, with the headquarters, and subtracting the headquarters sales amount from the deposited store sales amount and adjusting the amount. A store master including any one of the settlement classes, which is a class that means to pay, and store identification data for identifying the store,
Headquarters sales data, which is data on sales of the headquarters to the store, including store identification data and headquarters sales amounts,
Including store identification data and store sales amount, store sales data that is data on sales at the store,
Is stored,
Executed by the control unit,
When the division in the store master associated with the store identification data in the headquarters sales data is the billing division, the headquarters sales data associated with the store identification data and the store identification data in the headquarters sales data Claim data creation step of creating claim data as the claim including claim statement data having the head office sales amount,
When the section in the store master associated with the store identification data in the headquarters sales data is the settlement section, the store identification data in the headquarters sales data and the store sales data associated with the store identification data. Debt statement data having the total amount of the above-mentioned store sales amount and the store identification data in the headquarter sales data and the amount obtained by subtracting the head office sales amount in the head office sales data associated with the store identification data. Debt data creating step of creating debt data as the debt including offsetting detail data having an offset amount that is an amount for offsetting the total amount in the debt detail data,
Including,
A data creation method characterized by the following. A data creation program to be executed by an information processing device including a control unit and a storage unit,
In the storage unit,
The store manages the store sales amount, which is the sales amount at the store in the franchise agreement, at the store, and the headquarters claims the store sales amount, which is the sales amount of the headquarters of the franchise contract, to the store as receivables. The headquarters as a liability to the store, by depositing the billing division and the store sales amount, which is a classification meaning that, with the headquarters, and subtracting the headquarters sales amount from the deposited store sales amount and adjusting the amount. A store master including any one of the settlement classes, which is a class that means to pay, and store identification data for identifying the store,
Headquarters sales data, which is data on sales of the headquarters to the store, including store identification data and headquarters sales amounts,
Including store identification data and store sales amount, store sales data that is data on sales at the store,
Is stored,
For causing the control unit to execute,
When the division in the store master associated with the store identification data in the headquarters sales data is the billing division, the headquarters sales data associated with the store identification data and the store identification data in the headquarters sales data Claim data creation step of creating claim data as the claim including claim statement data having the head office sales amount,
When the division in the store master associated with the store identification data in the headquarters sales data is the settlement section, the store identification data in the headquarters sales data and the store sales data associated with the store identification data. Debt statement data having the total amount of the store sales amount in the above and the store identification data in the headquarters sales data and the amount obtained by subtracting the headquarter sales amount in the headquarters sales data associated with the store identification data Debt data creating step of creating debt data as the debt including offsetting detail data having an offset amount that is an amount for offsetting the total amount in the debt detail data,
Including,
A data creation program characterized by the following.

Images