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

Description

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

In Patent Document 1, ``The 1st store, the 2nd store, the 3rd store, and the Nth store are operated by company A in a direct/FC format. is installed." (see paragraph 0013 of Patent Document 1), and further, "POS total data and deposit machine data are collected from the POS registers and deposit machines of each store from the first store to the Nth store. Once received (step S300), data editing is performed in step S302 to generate POS register comparison data and deposit machine comparison data, where the POS register comparison data is the cash sales amount extracted from the POS aggregate data. , if change expenses, expense payments, etc. are recorded, the amount obtained by subtracting the recorded amount from the cash sales amount is used as the POS register comparison data." reference).

Japanese Patent Application Laid-Open No. 2003-308375

In this way, in the field of managing the sales amount of each FC store in a franchise (hereinafter sometimes referred to as "FC") contract, there have conventionally been the following problems. That is, 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 at the store, and the headquarters sales amount, which is the sales amount for the store of the FC contract, is managed at the store. A method (invoicing method) in which the headquarters bills the store for the amount (cost of ingredients, etc.) as a claim (billing method), and as shown in FIG. There is a method (settlement method) in which the head office pays the amount calculated by deducting (in other words, offsetting) the head office sales amount (food cost, etc.) from the sales amount as a debt to the store. Which contract method is adopted depends on each FC store. In general, when a corporation is the owner of an FC store, the billing method is adopted because the credit is high. If you are the owner, the settlement method will be adopted because the credit is low.

Here, when the person in charge of the FC head office registers the sales amount of the head office (such as the cost of ingredients) on the system, if the contract method with the FC store is the billing method, the person in charge registers it as the amount of the receivable. On the other hand, if the contract method with the FC store is the settlement method, it was necessary to make a decision to register it as the offset amount in the debt, so mistakes are likely to occur, and it also leads to delays in monthly settlement. I had a problem.

The present invention has been made in view of the above problems, and automatically distributes the head office sales amount to the amount of receivables or the amount of offset in debts without the person in charge at the FC head office making a judgment, 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 credits to the FC store of the headquarters, and debt data, which is data of debts to the FC store of the 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 comprising a control unit and a storage unit, wherein the storage unit stores sales data at a store under a franchise contract. It is a classification that means that the store sales amount, which is an amount, is managed by the store, and the headquarters claims the sales amount, which is the sales amount of the headquarters of the franchise contract to the store, as a claim against the store. A billing classification and a classification that means that all the store sales amount is deposited with the headquarters, and the headquarters pays the store the amount calculated by subtracting the headquarters sales amount from the deposited store sales amount as a debt. Store master containing either one of the settlement categories and store identification data for identifying the store, and data related to sales of the headquarters to the store, including the store identification data and headquarters sales amount Headquarters sales data and store sales data, which is data relating to sales at the store, including store identification data and store sales amounts, are stored, and the control unit is configured to:
When the division in the store master associated with the store identification data in the head office sales data is the billing division, the store identification data in the head office sales data and the head office sales data associated with the store identification data and the division in the store master linked to the store identification data in the headquarters sales data. In the case of the settlement classification, the debt statement data and the headquarters sales data having the store identification data in the headquarters sales data and the total amount of the store sales in the store sales data linked to the store identification data The amount obtained by recording the head office sales amount in the head office sales data linked to the store identification data and the head office sales data linked to the store identification data of the above as a negative amount, which is the amount to offset the total amount in the debt statement data. and debt data creation means for creating debt data as the debt including set-off detail data having an amount.

Further, in the data creation device according to the present invention, the head office sales data further includes an accounting date, which is the date when the head office sales amount is recorded, and the store sales data is the date on which the sales occurred at the store. The sales date is further included, and the store master further includes an applicable period, which is a period for which the classification is applied, is linked to the store identification data in the headquarters sales data, and to which the recording date belongs if the classification in the store master associated with the applicable period is the billing classification, the credit data creating means creates the credit data, associates it with the store identification data in the headquarters sales data, and When the classification in the store master linked to the applicable period to which the recording date belongs is the settlement classification, the debt data creating means provides the store sales data linked to the sales date belonging to the applicable period. creating the debt data having as the total amount the sum of the store sales amounts in the above.

Further, in the data creation device according to the present invention, the control unit pays the sum of the total amount in the debt detailed data and the offset amount in the offset detailed data as a debt to the store of the headquarters. characterized by further comprising payment processing execution means for executing

Further, in the data creation device according to the present invention, the headquarter sales amount is a royalty payable by the store to the headquarter in the franchise contract or the cost of what the headquarter 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 having a control unit and a storage unit, wherein the storage unit stores store sales, which is the amount of sales at the store under a franchise contract. Billing classification, which is a classification meaning that the amount is managed by the store, and the sales amount of the headquarters, which is the sales amount of the headquarters of the franchise contract to the store, is billed by the headquarters to the store as a claim, and the store All the sales amount is deposited with the said headquarters, and the said headquarters pays the amount settled by deducting the said headquarters sales amount from the deposited store sales amount as a debt to the said store. a store master containing either one of the categories and store identification data for identifying the store; headquarters sales data, which is data related to sales of the headquarters to the store, including store identification data and headquarters sales amount; , and store sales data, which is data relating to sales at the store, including store identification data and store sales amount, and the store identification data in the headquarters sales data, which is executed by the control unit. If the division in the store master linked to is the billing classification, the invoice includes the store identification data in the headquarters sales data and the headquarters sales amount in the headquarters sales data linked to the store identification data a claim data creation step of creating claim data as the claim including detailed data; Debt statement data having the store identification data in the data and the total amount of the store sales amount in the store sales data linked with the store identification data, and the store identification data and the store identification data in the headquarters sales data Includes offset detail data that has an offset amount that is an amount obtained by negatively recording the headquarters sales amount in the headquarters sales data linked with and is an amount for offsetting the total amount in the debt specification data and a debt data creation step of creating debt data as the debt.

Further, a data creation program according to the present invention is a data creation program to be executed by an information processing apparatus having a control unit and a storage unit, wherein the storage unit stores a sales amount at a store under a franchise contract. A billing classification, which is a classification that means that the sales amount is managed by the store and that the headquarters charges the sales amount, which is the sales amount of the headquarters of the franchise contract to the store, as a claim against the store; Settlement classification, which means that the head office pays the store as a liability for the amount settled by deducting the head office sales amount from the deposited store sales amount after all the store sales amount is deposited with the head office. Head office sales data, which is data relating to sales of the head office to the store, including a store master containing either one of the classifications and store identification data for identifying the store, and head office sales data including the store identification data and the head office sales amount and store sales data, which is data relating to sales at the store, including store identification data and store sales amount, and the store in the headquarters sales data for causing the control unit to execute When the division in the store master linked to the identification data is the billing division, the store identification data in the headquarters sales data and the headquarters sales amount in the headquarters sales data linked to the store identification data are combined. and a claim data creation step of creating claim data as the claim including billing detail data having the Debt detail data having the store identification data in the headquarters sales data and the total amount of the store sales in the store sales data linked to the store identification data, and the store identification data in the headquarters sales data and the store Offset detail data having an offset amount that is an amount obtained by recording a negative amount of the head office sales amount in the head office sales data linked to the identification data and is an amount for offsetting the total amount in the debt detail data and a debt data creation step of creating debt data as the debt including

According to the present invention, without judgment by the person in charge at the FC headquarters, the sales amount at the headquarters is automatically sorted into the amount of receivables or the offsetting amount in the debts, Data and obligation data, which is the data of the obligations of the FC headquarters to the FC store, can be created.

FIG. 1 is a block diagram showing an example of the configuration of a data creation device. FIG. 2 is a diagram showing an example of an image of the billing system. FIG. 3 is a diagram showing an example of an image of the payment method. FIG. 4 is a diagram showing an example of an overview of processing according to the present embodiment. FIG. 5 is a diagram showing an example of details of processing according to the present embodiment.

Embodiments of a data creation device, a data creation method, and a data creation program will be described in detail below with reference to the drawings. It should be noted that the present invention is not limited by this embodiment.

[1. Overview]
FC contracts are broadly divided into the following two contract methods. First, as shown in Fig. 2, the FC store owner manages the store sales proceeds, and the FC headquarters bills the owner of the FC store for royalties, food ingredients, etc., for each closing date. There is The billing method is often employed in contracts with corporate owners with high credit. On the other hand, as shown in Fig. 3, all store sales proceeds are deposited with the FC headquarters, and the amount after deducting royalties and the cost of delivered ingredients is paid to the owner of the FC store every closing date. There is a method. The settlement method is often adopted in contracts with individual owners with low credit.

Here, in the past, depending on the type of contract method with the FC store, from the perspective of the FC headquarters, whether the actual shipment of ingredients to the FC store or the recording of expenses would increase the receivables, or would be the offset amount in the debt. Therefore, even if the act of registering and inputting food shipment results and expense recording is the same, it is necessary to separate the registration screen or the input screen in consideration of the type of contract method with the FC store. rice field. As a result, there were problems such as frequent mistakes, errors in materials for owners of FC stores, and delays in monthly settlement of accounts.

Therefore, in this embodiment, for example, the person in charge at the FC headquarters decides whether to register the cost of foodstuffs delivered to the FC store, the expenses for the FC store, etc. as the amount of the claim or the offset amount of the debt. It is possible to do so without being conscious of it, and furthermore, it is possible to automatically allocate the cost of ingredients and expenses to the amount of the claim or the amount of offset in the debt. Also, in this embodiment, for example, even if there is a change in the owner of the FC store during the month, appropriate distribution can be made according to the contract method with each owner before and after the change. Specific configurations and operations will be described below.

[2. Constitution]
An example of the configuration of the data creation device 100 according to this 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. As shown in FIG.

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, and may be a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. It may be an information processing device.

The data creation device 100 includes a control section 102 , a communication interface section 104 , a storage section 106 and an input/output interface section 108 . Each unit included in the data creation device 100 is 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). Data such as various masters described later 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 section 108 . 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 realizes a pointing device function in cooperation with a mouse. Note that, hereinafter, the output device 114 may be referred to as the monitor 114 and the input device 112 may be referred to as the keyboard 112 or the mouse 112 .

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

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, bond data 106d, and debt data 106e. ing.

As shown in FIG. 5, the store contract master 106a, for example, manages the store sales amount, which is the sales amount at the store in the franchise contract, at the store, and manages the store sales amount, which is the sales amount for the store under the franchise contract. The billing classification (billing method), which is a classification that means that the sales amount is billed to the store as a claim by the headquarters, and the store sales amount are all deposited with the headquarters, and the store sales amount deposited is deducted from the store sales amount. Identify one of the settlement categories (settlement method), which means that the head office pays the store as a debt, the amount calculated by deducting the sales amount (contract form) and the store. store identification data (store code and store name) for the purpose, the application period (application start date) that is the period for which the classification (contract form) is applied, and the owner identification for identifying the owner in the store data (owner code and owner name), and so on.

The sales data 106b is data relating to the sales of the headquarters to the store. As shown in FIG. 5, the sales data 106b includes, for example, the recording date, which is the date when the headquarters sales amount was recorded, the store identification data (store code and store name), and the sales data from the headquarters to the store. Product identification data (product code and product name) for identifying the product that was purchased, the number of sales of the product, the unit sales price (unit price) of the product, the headquarters sales amount (amount), and the headquarters sales amount Including consumption tax, etc.

The head office sales amount is, for example, a royalty to be paid by the store to the head office in the franchise contract, or the cost of items provided by the head office to the store. The costs include, for example, the cost of foodstuffs and raw materials wholesaled by the headquarters to the store, and the usage fee of the system provided by the headquarters to the store.

The over-the-counter 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, the sales date, which is the date when the sales occurred at the store, the store identification data (store code and store name), and the products sold at the store. Product identification data (product code and product name) for identification, the number of sales of the product, the unit sales price (unit price) of the product, the store sales amount (amount), and the consumption tax on the store sales amount , etc.

The bond data 106d is bond data created by the bond data creation unit 102a, which will be described later, based on the sales data 106b when the classification (contract form) in the store contract master 106a is the billing classification (billing method). . The credit data 106d has, as shown in FIG. 5, detailed billing data (three pieces of billing detailed data labeled SK1 to SK3 in FIG. 5).

The debt data 106e is created by the debt data creation unit 102b based on the sales data 106b and store sales data 106c when the division (contract type) in the store contract master 106a is the settlement division (settlement method). Debt data. As shown in FIG. 5, the debt data 106e is created based on the debt detail data (in FIG. 5, two debt detail data with SM3 to SM4) created based on the store sales data 106c and the sales data 106b. (In FIG. 5, two offset detail data with SM1 to SM2 attached).

The control unit 102 is a CPU or the like that controls the data generation device 100 in an integrated manner. 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 information processing based on these stored programs. Run.

The control unit 102 functionally conceptually performs, for example, (1) when the division in the store master linked to the store identification data in the headquarters sales data is the billing division, the division in the headquarters sales data a bond data creation unit 102a as bond data creating means for creating bond data as the bond including billing detail data having store identification data and the head office sales amount in the head office sales data linked to the store identification data; , (2) when the division in the store master associated with the store identification data in the head office sales data is the settlement division, the store identification data in the head office sales data is associated with the store identification data; the sum of the store sales amounts in the store sales data, the store identification data in the headquarters sales data, and the headquarters sales amount in the headquarters sales data linked to the store identification data minus the as a debt data creation means for creating debt data as said debt including offset detail data having an offset amount which is the amount recorded in the above and is an amount for offsetting said total amount in said debt detail data and (3) a payment processing execution of paying the sum of the total amount in the debt detail data and the offset amount in the offset detail data as a debt to the store of the headquarters. and a payment processing execution unit 102c as means.

If the contract type in the store contract master 106a associated with the store identification data in the sales data 106b is a billing method, the bond data creation unit 102a associates the store identification data in the sales data 106b with the store identification data. A claim data 106d is created as a claim including billing detail data having the head office sales amount in the sales data 106b.

If the contract form in the store contract master 106a linked to the store identification data in the sales data 106b and linked to the applicable period to which the recording date belongs is billing, the bond data creation unit 102a creates the bond data 106d. may be created.

If the contract type in the store contract master 106a linked to the store identification data in the sales data 106b is the settlement method, the debt data creation unit 102b generates the store identification data in the sales data 106b and the store linked to the store identification data. Debt detail data having the total amount of store sales in the sales data 106c, the store identification data in the sales data 106b, and the headquarters sales amount in the sales data 106b linked to the store identification data are negatively recorded. Then, the debt data 106e as the debt including the offset detail data having the offset amount which is the amount for offsetting the total amount in the debt detail data is created.

If the contract form in the store contract master 106a linked to the store identification data in the sales data 106b and linked to the applicable period to which the recording date belongs is the settlement method, the debt data creation unit 102b determines the applicable period The debt data 106e having, as the total amount, the sum of the store sales amounts in the store sales data 106c associated with the sales date belonging to the above may be created.

The payment processing execution unit 102c executes processing 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.

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

When sales are generated from the head office to the store, sales data 106b is created by inputting the sales by a person in charge at the head office. On the other hand, when sales occur at the store, store sales data 106c is created by inputting store sales by the person in charge of the store.

Then, with reference to the store contract master 106a, allocation to credits or debts is automatically performed as follows according to the contract method with the store.

If the contract method with the store is the billing method, the bond data 106d is created based on the sales data 106b. In this way, in the case of the billing method, sales from the head office to the store result in an increase in receivables from the head office's point of view.

When the contract method with the store is the settlement method, the debt data 106e is created based on the sales data 106b and the store sales data 106c. Specifically, all the store sales amounts in the store sales data 106c are recorded as liabilities as deposits to be returned to the store. Also, the amount of sales from the head office to the store in the sales data 106b is posted as a negative amount to be deducted from the deposit. The sum of the deposit and the offset amount is the final amount returned by the headquarters to the store.

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

In FIG. 5, the detailed data of the store contract master 106a are denoted by TK1-TK4, the detailed data of the sales data 106b are denoted by U1-5, and the detailed data of the store sales data 106c are denoted by U1-5. The data are labeled with TU1-90, the detailed data of the bond data 106d are labeled with SK1-3, and the detailed data of the debt data 106e are labeled with SM1-4. These symbols are added for convenience of explanation, and are not the data or the information contained in the data.

[4-1. Creation of receivables data for FC store B store]
First, generation of bond data 106d for B store, which is an FC store, will be described.

Referring to the store contract master 106a, the contract form associated with store code: T101 and store name: B store in the detailed data U3 is billing. In this case, the bond data creation unit 102a creates billing statement data SK2 based on the statement data U3. Specifically, as shown in the invoice detail data SK2, the bond data creation unit 102a connects the store code: T101 and the store name: B store in the detail data U3, and the store code: T101 and the store name: B store. Other information in the attached detailed data U3 (recording 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), Create invoice detail data SK2 containing

In a similar manner, the bond data creation unit 102a creates billing statement data SK3 based on the statement data U4.

As described above, the bond data creation unit 102a creates the bond data 106d including the detailed billing data SK2 and the detailed billing data SK3 as the bond data for the FC store B, as shown in the bond data 106d. .

[4-2. Creation of Debt Data for FC Store C]
Next, the preparation of debt data 106e for store C, 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 detailed data U5 is the settlement method. In this case, the debt data creation unit 102b creates debt detailed data SM4 based on the detailed data TU61-TU90. Specifically, as shown in the debt detail data SM4, the debt data creation unit 102b links the store code: T102 and the store name: C store in the detail data U5, and the store code: T102 and the store name: C store. Information based on other information in the attached detailed data TU61-90 (recording date: April 30, 2018, product code: Z999, product name: deposit, quantity: 1, unit price: 600,000, amount: 600,000 and consumption tax: 48,000) and debt statement data SM4. As the recording date, the end of the month "2018/4/30" may be set as in this example, or the contract switching date may be set. As the product code and the product name, "Z999" and "deposit" are set, respectively, because sales in the detailed data TU61-TU90 are recorded as deposits. As the unit price and the amount, 600,000 (for 30 items of 20,000), which is the total amount of sales amounts of 20,000 in each of the item data TU61 to TU90, is set. The 600,000 is the amount that C store once deposits with the FC headquarters.

On the other hand, the debt data creation unit 102b creates offset detailed data SM2 based on the detailed data U5. Specifically, as shown in the offset detail data SM2, the debt data creation unit 102b links the store code: T102 and the store name: C store in the detail data U5, and the store code: T102 and the store name: C store. Information based on other information in the attached detailed data U5 (accounting date: April 1, 2018, product code: S100, product name: flour 10 kg, quantity: 5, unit price: -10,000, amount: -50,000 and consumption tax: -4,000) and offset detail data SM2. As the unit price, -10,000, which is the minus unit price of 10,000 in the detailed data U5, is set. As the amount, -50,000, which is the minus amount of 50,000 in the detailed data U5, is set. The -50,000 is the offset amount to be deducted (offset) from the 600,000 when the total amount of 600,000 explained in the preceding paragraph is returned to Store C.

As described above, the debt data creation unit 102b creates the debt data 106e including the debt detail data SM4 and the offset detail data SM2 as the debt data for the FC store C, as shown in the debt data 106e. . Subsequently, payment processing may be performed, as described in the next paragraph.

The payment processing executing unit 102c executes the payment processing as a debt of the FC head office to the C store (ie refund).

[4-3. Creation of receivable data and debt data for FC store A]
Finally, the generation of bond data 106d and debt data 106e for FC store A will be described. In this example, as shown in the shop contract master 106a, the owner has changed from the corporation XX to the individual Hanako Yamada on April 21, 2018. Even in such a case, according to the data creation device 100 according to the present embodiment, as will be described below, when wholesale to XX Corporation during the period of contract with XX Corporation The head office sales amount can be distributed as the amount of receivables billed to XX Co., Ltd. On the other hand, the head office sales amount when wholesaled to Hanako Yamada during the period of contract with Hanako Yamada is to offset the sales proceeds that are temporarily kept by Hanako Yamada and returned as debt. can be distributed as an offset amount.

(1) 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 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 it is. Here, the accounting date 2018/4/1 in the detailed data U1 belongs to the applicable period (from 2018/1/1 to 2018/4/20) of the detailed data TK1. Therefore, the contract form associated with the detailed data U1 is the billing method, which is the contract form of the detailed data TK1. Although detailed description is omitted below, the bond data creation unit 102a creates detailed billing data SK1 based on the detailed data U1 in the same manner as described in [4-1].

As described above, the bond data creation unit 102a generates bond data including the billing detail data SK1 as bond data for the period in which company XX of FC store A is the owner, as shown in bond data 106d. 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 it is. Here, the accounting date 2018/4/21 in the detailed data U2 belongs to the applicable period (after 2018/4/21) of the detailed data TK2. In this case, the debt data creation unit 102b creates debt detailed data SM3 based on the detailed data TU21 to TU30. Specifically, as shown in the debt detail data SM3, the debt data creation unit 102b links the store code: T100 and the store name: A store in the detail data U2, and the store code: T100 and the store name: A store. Information based on other information in the attached detailed data TU21-30 (Recording date: April 30, 2018, product code: Z999, product name: deposit, quantity: 1, unit price: 200,000, amount: 200,000 and consumption tax: 16,000) and debt statement data SM3. The unit price and the amount are 200,000 (10 items of 20,000), which is the sum of the sales amounts of 20,000 in each of the item data TU21 to TU30 having sales dates belonging to the application target period (after April 21, 2018) of the item data TK2. minutes) is set. The 200,000 is the amount Hanako Yamada once entrusted to FC Headquarters.

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

As described above, the debt data creation unit 102b generates debt detailed data SM3 and offset detailed data SM1 as debt data for the period in which Ms. Hanako Yamada of the FC store A is the owner, as shown in the debt data 106e. create debt data 106e including

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

[4-4. summary]
By referring to the receivables data 106d created through the processes [4-1] to [4-3] above, the total amount of receivables held by the FC headquarters is the amount and consumption in each of the detailed billing data SK1 to SK3. It can be understood that the sum of all taxes (amount 100,000 + consumption tax 8,000 + amount 30,000 + consumption tax 2,400 + amount 20,000 + consumption tax 1,600 = 162,000. In addition, [4-1] to [4-3 ], the total amount of debt held by the FC headquarters is the sum of the amounts and consumption tax in each of the offset detail data SM1-2 and the debt detail 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 creation device 100 according to the present embodiment, without the judgment of the person in charge of the FC headquarters, the sales amount of the headquarters is automatically sorted into the amount of receivables or the amount of offset in debts, Furthermore, it is possible to create credit data 106d, which is credit data of the FC head office to the FC store, and debt data 106e, which is credit data of the FC head office to the FC store. For this reason, for example, as in the past, the person in charge of the FC head office judges whether the head office sales amount will increase the receivables or will be the offset amount in the debt, and the registration screen and input of the head office sales amount Since it is no longer necessary to separate the screens, it is possible to prevent errors caused by this work, errors in materials for owners of FC stores, and delays in monthly settlement of accounts.

[5. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

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

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

Also, with regard to the data generation device 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions of the data generation device 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in the present embodiment, and the data creation device if necessary. 100 mechanically read. That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

In addition, this computer program may be stored in an application program server connected to the data creation apparatus 100 via any network, and all or part of it can be downloaded as necessary. be.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" means memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (Registered trademark) such as Blu- shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, the installation procedure after reading, and the like.

The various databases stored in the storage unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks. It stores programs, tables, databases, files for web pages, and so on.

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

Furthermore, the specific forms of distribution and integration of devices are not limited to those shown in the figures, and all or part of them can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

INDUSTRIAL APPLICABILITY The present invention is useful, for example, in an industry that develops multiple stores by concluding FC contracts.

100 data creation device 102 control unit
102a bond 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 Store sales data
106d Credit 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 comprising a control unit and a storage unit,
The storage unit contains
The store sales amount, which is the sales amount at the store under the franchise contract, is managed by the store, and the headquarters bills the store for the headquarters sales amount, which is the sales amount for the store under the franchise contract. The billing classification, which is a classification that means that the store sales amount is all deposited with the headquarters, and the headquarters deducts the amount settled by deducting the headquarters sales amount from the deposited store sales amount as a debt to the store. a store master containing either one of the settlement categories, which is a category meaning payment, and store identification data for identifying the store;
headquarters sales data, which is data relating to sales of the headquarters to the stores, including store identification data and headquarters sales amounts;
store sales data, which is data related to sales at the store, including store identification data and store sales amount;
is stored and
The control unit
When the division in the store master associated with the store identification data in the head office sales data is the billing division, the store identification data in the head office sales data and the head office sales data associated with the store identification data a claim data creation means for creating claim data as said claim including billing detail data having said headquarters sales amount in
When the division in the store master associated with the store identification data in the headquarters sales data is the settlement division, the store identification data in the headquarters sales data and the store sales data associated with the store identification data Debt detail data having the total amount of the store sales amount in the above, the store identification data in the headquarters sales data, and the headquarters sales amount in the headquarters sales data linked to the store identification data The amount recorded as a minus a debt data creation means for creating debt data as the debt including offset detail data having a set-off amount that is an amount for offsetting the total amount in the debt detail data;
to provide
A data creation device characterized by: The head office sales data further includes a recording date, which is the date when the head office sales amount is recorded,
The store sales data further includes a sales date, which is the date the sale occurred at the store,
The store master further includes an applicable period, which is a period to which the classification is applied,
When the classification in the store master linked to the store identification data in the headquarters sales data and linked to the applicable period to which the recording date belongs is the billing classification, the claim data creating means create receivables data,
When the division in the store master linked to the store identification data in the headquarters sales data and linked to the applicable period to which the recording date belongs is the settlement category, the debt data creating means Creating the debt data having as the total amount the sum of the store sales amounts in the store sales data associated with the sales date belonging to the applicable period;
The data creation device according to claim 1, characterized by: The control unit
further comprising payment processing execution 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 detail data as a debt to the store of the headquarters;
3. The data creation device according to claim 1 or 2, characterized by: The headquarters sales amount is the royalty payable by the store to the headquarters in the franchise contract or the cost of what the headquarters provided to the store,
4. The data creation device according to any one of claims 1 to 3, characterized by: A data creation method executed by an information processing device comprising a control unit and a storage unit,
The storage unit contains
The store sales amount, which is the sales amount at the store under the franchise contract, is managed by the store, and the headquarters bills the store for the headquarters sales amount, which is the sales amount for the store under the franchise contract. The billing classification, which is a classification that means that the store sales amount is all deposited with the headquarters, and the headquarters deducts the amount settled by deducting the headquarters sales amount from the deposited store sales amount as a debt to the store. a store master containing either one of the settlement categories, which is a category meaning payment, and store identification data for identifying the store;
headquarters sales data, which is data relating to sales of the headquarters to the stores, including store identification data and headquarters sales amounts;
store sales data, which is data related to sales at the store, including store identification data and store sales amount;
is stored and
executed by the control unit;
When the division in the store master linked to the store identification data in the headquarters sales data is the billing classification, the store identification data in the headquarters sales data and the headquarters sales data linked to the store identification data a claim data creation step of creating claim data as said claim including billing detail data having said headquarters sales amount in
When the division in the store master associated with the store identification data in the headquarters sales data is the settlement division, 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, the store identification data in the headquarters sales data, and the headquarters sales amount in the headquarters sales data linked to the store identification data are recorded as negative amounts and a debt data creation step of creating debt data as the debt including offset 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: A data creation program to be executed by an information processing device comprising a control unit and a storage unit,
The storage unit contains
The store sales amount, which is the sales amount at the store under the franchise contract, is managed by the store, and the headquarters bills the store for the headquarters sales amount, which is the sales amount for the store under the franchise contract. The billing classification, which is a classification that means that the store sales amount is all deposited with the headquarters, and the headquarters deducts the amount settled by deducting the headquarters sales amount from the deposited store sales amount as a debt to the store. a store master containing either one of the settlement categories, which is a category meaning payment, and store identification data for identifying the store;
headquarters sales data, which is data relating to sales of the headquarters to the stores, including store identification data and headquarters sales amounts;
store sales data, which is data related to sales at the store, including store identification data and store sales amount;
is stored and
for causing the control unit to execute
When the division in the store master associated with the store identification data in the head office sales data is the billing division, the store identification data in the head office sales data and the head office sales data associated with the store identification data a claim data creation step of creating claim data as said claim including billing detail data having said headquarters sales amount in
When the division in the store master associated with the store identification data in the headquarters sales data is the settlement division, the store identification data in the headquarters sales data and the store sales data associated with the store identification data Debt detail data having the total amount of the store sales amount in the above, the store identification data in the headquarters sales data, and the headquarters sales amount in the headquarters sales data linked to the store identification data The amount recorded as a minus and a debt data creation step of creating debt data as the debt including offset 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:

Images