System and program

Abstract

To support appropriate transactions.SOLUTION: A system capable of issuing a plurality of receipts in a single transaction is provided with issuance instruction means. The issuance instruction means allows each receipt to be issued with a specific matter relating to the tax of the single transaction displayed in a manner that differs among the plurality of receipts. The issuance instruction means may allow other receipts of the plurality of receipts to be issued after the completion of the single transaction for which one receipt of the plurality of receipts has been issued.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to a system and a program. [Background technology]

[0002] Conventionally, cash registers have been able to print receipts and invoices. In particular, electronic receipts that display computerized receipts on mobile terminal devices such as smartphones have become widespread in recent years. For example, a system is known that allows a paper receipt to be printed after a transaction for which an electronic receipt has been output (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2013-175212 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, if the tax deduction information is displayed on both the electronic receipt and the paper receipt, multiple receipts with the same effect will exist for one transaction. This can lead to problems such as fraudulent expense recording, and thus the inability to carry out a proper transaction.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of supporting appropriate transactions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a system capable of issuing multiple receipts for a single transaction, and is characterized by having an issuance instruction means for causing each receipt to be issued with specific information related to taxes for the single transaction displayed in a different manner among the multiple receipts.

[0007] In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes a computer to function as a system capable of issuing multiple receipts for a single transaction, and is characterized in that it causes the computer to function as an issuance instruction means that issues each receipt by displaying specific information related to taxes for the single transaction in a different manner among the multiple receipts. [Brief description of the drawings]

[0008] [Figure 1] 1 is an explanatory diagram showing a network configuration of a product sales data processing system 1 according to an embodiment. [Diagram 2] 1 is an explanatory diagram showing an example of installation of a registration settlement device 30 as seen from the customer side. [Diagram 3] FIG. 2 is a block diagram showing an example of a hardware configuration of a mobile terminal device 40. [Figure 4] 1 is an explanatory diagram showing an example of a functional configuration of a product sales data processing system 1. FIG. [Figure 5A] FIG. 2 is a diagram showing an example of transaction information stored in a transaction information DB11. [Figure 5B] FIG. 13 is a diagram showing an example of amount detailed information. [Figure 6] FIG. 4 is an explanatory diagram illustrating an example of a receipt according to the embodiment. [Figure 7] 10 is a flowchart showing an example of a process for issuing a receipt performed by the management server 10 of this embodiment. [Figure 8] FIG. 11 is a diagram illustrating an example of a functional configuration of a product sales data processing system 1 according to a second modified example. [Figure 9] FIG. 13 is a diagram showing an example of a non-detailed receipt relating to Modification 2. [Figure 10] 13 is a flowchart showing an example of a non-detailed receipt issuing process performed by a registered settlement device 30 according to Modification 2. [Figure 11] FIG. 13 is a diagram showing an example of a qualified invoice relating to the third modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment) (Network configuration of product sales data processing system 1) 1 is an explanatory diagram showing a network configuration of a product sales data processing system 1 according to an embodiment. The product sales data processing system 1 is an example of a system. The product sales data processing system 1 can be introduced in various stores such as supermarkets, home improvement stores, convenience stores, and various supply stores.

[0010] 1, the product sales data processing system 1 includes a management server 10, a store controller 20, a registration and settlement device 30, and a mobile terminal device 40. Each device is a computer device equipped with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, etc. Each device is connected to each other via a network 50 so as to be able to communicate with each other.

[0011] (Management Server 10) The management server 10 has a transaction information DB (database) 11 and manages transaction information for each customer (member customer). The transaction information includes member information for each customer and settlement information showing transaction history. It issues instructions to the registered settlement device 30 and the mobile terminal device 40 regarding the output of receipts. The member information includes various information such as member identification information (member ID) that identifies the member customer, the terminal ID of the mobile terminal device 40 held by the customer, the customer's name, date of birth, purchase history, etc.

[0012] (Store Controller 20) The store controller 20 manages sales and inventory of each store, product master, membership information of member customers, etc. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and sales price for each product. The product master also includes various information such as product identification information, product name, and unit price for products that require weighing. The store controller 20 stores various information required for transactions, such as the product master. The store controller 20 also stores various information such as the inventory status and sales history of its own store, in addition to the deposit and withdrawal records of the registered settlement device 30.

[0013] (Registration settlement device 30) The registration and settlement device 30 is a device that registers products and settles the payment. When settlement is completed, the registration and settlement device 30 issues a paper receipt. The registration and settlement device 30 can also read member information from a membership card held by a customer and generate registration information and settlement information based on the member information. There may be one registration and settlement device 30, or multiple registration and settlement devices. The registration and settlement device 30 also includes those located at service counters, etc.

[0014] The registration and settlement device 30 may be a clerk-operated type in which a clerk performs the registration operation and the settlement operation, or a self-service type in which a customer performs the registration operation or the settlement operation. The self-service type registration and settlement device 30 may be a full-self-service type in which the customer performs both the registration operation and the settlement operation, or a semi-self-service type in which the customer performs only the settlement operation. Note that the registration and settlement device 30 in which the customer performs only the settlement operation may be a device dedicated to settlement that does not have a product registration function and has only a settlement function.

[0015] The registered settlement device 30 is capable of switching between different operation modes. The operation modes include, for example, a clerk registration mode in which a clerk performs the registration operation, a full self-service mode in which a customer performs both the registration operation and the settlement operation, and a settlement mode in which a customer performs the settlement operation. The registered settlement device 30 has a function of settling the customer's account. For this reason, in the clerk registration mode, it is possible for the clerk to face the customer at the registered settlement device 30 and settle the account, or it is possible to have another registered settlement device 30 operating in the settlement mode obtain the information necessary for settlement and have the customer settle the account at the other registered settlement device 30.

[0016] (Mobile terminal device 40) The mobile terminal device 40 is a terminal device carried by a customer. The mobile terminal device 40 is, for example, a smartphone or a mobile phone. An application for displaying electronic receipts (hereinafter referred to as a "receipt issuing application") is installed in the mobile terminal device 40. When the customer installs the receipt issuing application, the customer registers as a member within the receipt application.

[0017] At the time of settlement, the customer launches the receipt issuing app on the mobile terminal device 40, causes the mobile terminal device 40 to display a barcode indicating the terminal ID that identifies the device (hereinafter referred to as the "app terminal code"), and causes the registered settlement device 30 to read the app terminal code. The registered settlement device 30 transmits transaction information to the management server 10 that associates the terminal ID indicated by the read app terminal code with settlement information generated during settlement. Upon receiving the settlement information from the registered settlement device 30, the management server 10 transmits the settlement information to the mobile terminal device 40 indicated by the terminal ID. Upon receiving the settlement information from the management server 10, the mobile terminal device 40 is able to display an electronic receipt based on the settlement information.

[0018] (Example of configuration of registration settlement device 30) Next, the configuration of the registration and settlement device 30 will be described with reference to FIG. 2 is an explanatory diagram showing an example of installation seen from the customer side of the registration and settlement device 30. Although not shown, a counter for placing a shopping basket is placed on either or both sides of the registration and settlement device 30.

[0019] The registration and settlement device 30 comprises a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer display unit 205, a customer scanner unit 206, a medium settlement unit 208, a change machine 209, a store clerk display unit 210, a key operation unit 211, a store clerk scanner unit 212, a printing unit 213, an audio output unit 214, a communication unit 215, a camera 216, and a sign pole 220. These can communicate with each other via a bus (not shown).

[0020] The CPU 201 is a central processing unit, and reads out and executes various programs stored in the ROM 202 to control the operation of the registration and settlement device 30. The various programs include a product sales data processing program according to this embodiment. The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including various programs.

[0021] The RAM 203 is a readable and writable memory that stores various information. For example, the RAM 203 stores information acquired from the outside (for example, product information acquired from the store controller 20), registration information indicating registered products, and payment information generated during payment.

[0022] Hard disk 204 stores various information. For example, hard disk 204 stores imaging results (e.g., video) captured by camera 216. Hard disk 204 may store various programs executed by CPU 201, instead of ROM 202. Hard disk 204 may also store information acquired from the outside and information generated in processing, instead of RAM 203.

[0023] The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various information to the customer and accepts various inputs from the customer. The customer-side display unit 205 displays preset keys (buttons for ordering products) corresponding to products, and accepts product registration when the preset keys are pressed.

[0024] The customer-side scanner unit 206 is a scanner unit for customers to optically read various information, including an application terminal code (terminal ID of the mobile terminal device 40) and a product code (barcode) attached to the product.

[0025] The medium settlement unit 208 is a settlement mechanism using credit cards and electronic money. Electronic money is stored (charged) in a transportation IC card or a mobile terminal device 40 such as a smartphone. The medium settlement unit 208 can also make a settlement using points from a point card.

[0026] The change machine 209 is a cash settlement mechanism. The change machine 209 faces the customer side and accepts various operations and cash insertion from the customer. Specifically, the change machine 209 has an insertion port and an ejection port for bills and coins. The change machine 209 calculates the amount inserted into the insertion port, calculates the change amount, which is the difference between the inserted amount and the purchase amount, and ejects the change from the ejection port.

[0027] The store clerk display unit 210 is a touch display for the store clerk. The store clerk display unit 210 displays various information to the store clerk and accepts various inputs from the store clerk. The store clerk display unit 210 displays preset keys corresponding to products, and accepts product registration when the preset keys are operated by the store clerk.

[0028] The key operation unit 211 is provided on the store clerk's side and has various keys (hardware keys, buttons). The key operation unit 211 accepts various inputs from the store clerk. The key operation unit 211 includes a mode switching button. The mode switching button is a button for switching the operation mode. The mode switching button includes a button for switching all registered settlement devices 30 at once, and a button for switching only the device itself. The key operation unit 211 also has a registration button corresponding to a product, and accepts the registration of the product when the registration button is operated by the store clerk.

[0029] The store clerk scanner unit 212 is a scanner unit for store clerks, and optically reads various information, including an application terminal code (terminal ID of the mobile terminal device 40), a store clerk code attached to the store clerk's name tag, and a product code (barcode) attached to the product.

[0030] The printing unit 213 prints and outputs various media (receipts, invoices, etc.). The audio output unit 214 outputs sounds. For example, the audio output unit 214 outputs audio guidance and warning sounds related to product registration and payment. The communication unit 215 is an interface for transmitting and receiving information to and from other devices (such as the management server 10, the store controller 20, and the mobile terminal device 40).

[0031] Camera 216 is attached to the upper right of customer side display unit 205. Camera 216 is a camera that continuously captures moving or still images. A CCD (charge coupled device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera can be used as camera 216. Camera 216 captures images of product registration operations and payment operations by a customer, and also captures images of products to be registered.

[0032] The sign pole 220 is, for example, a lamp or an LED (light emitting diode) and can be lit in a predetermined color or in a predetermined lighting manner. Depending on the lighting manner of the sign pole 220, it can indicate that it is in use, that there is an error, or that a fraudulent act has been performed by a customer.

[0033] (Hardware configuration of the mobile terminal device 40) Fig. 3 is a block diagram showing an example of a hardware configuration of mobile terminal device 40. In Fig. 3, mobile terminal device 40 includes a CPU 301, a memory 302, a communication I / F 303, a storage medium I / F 304, an input device 305, a display 306, and a speaker 307. Each unit is connected to each other via a bus 320.

[0034] The CPU 301 is responsible for the overall control of the mobile terminal device 40. The memory 302 includes, for example, a ROM, a RAM, and a flash ROM. For example, the flash ROM and the ROM store various programs such as the product sales data processing program according to this embodiment. The RAM is used as a work area for the CPU 301. The programs stored in the memory 302 are loaded into the CPU 301, causing the CPU 301 to execute the coded processes.

[0035] The communication I / F 303 is connected to a network 50 such as the Internet through a communication line, and is connected to other devices (e.g., the management server 10, the registration and settlement device 30, etc.) through the network 50. The communication I / F 303 also manages the interface between the network 50 and the inside of its own device, and controls the input and output of data from other devices. A storage medium I / F 303, under the control of the CPU 301, controls reading and writing of data from and to a storage medium (not shown), such as a memory card.

[0036] The input device 305 includes an operation button, a microphone, a camera, a scanner, and various sensors. The display 306 is, for example, a touch panel type liquid crystal display unit. The speaker 307 outputs sound.

[0037] (Regarding receipt issuance) The product sales data processing system 1 according to this embodiment is capable of issuing electronic receipts and paper receipts. If the electronic receipt and the paper receipt are both provided with information regarding tax deductions, then multiple receipts with the same effect will exist for one transaction. This may lead to, for example, fraudulent expense recording, and thus to a risk of not being able to carry out an appropriate transaction. Therefore, this embodiment is designed to support appropriate transactions. The functional configuration of the product sales data processing system 1 shown in FIG. 4 will be described below with reference to FIG. 5A, FIG. 5B, and FIG. 6.

[0038] (Functional configuration of product sales data processing system 1) Fig. 4 is an explanatory diagram showing an example of a functional configuration of the product sales data processing system 1. As shown in Fig. 4, the mobile terminal device 40 includes a first issuing unit 401. The first issuing unit 401 is realized by the CPU 301. That is, the CPU 301 executes a product sales data processing program stored in the memory 302, thereby realizing the function of the first issuing unit 401.

[0039] The registration and settlement device 30 includes a registration unit 411, a settlement unit 412, and a second issuing unit 413. Each unit is realized by the CPU 201. That is, the CPU 201 executes a product sales data processing program stored in the ROM 202 or the like to realize the function of each unit.

[0040] The management server 10 includes an issuance instruction unit 400. The issuance instruction unit 400 is realized by a CPU included in the management server 10. That is, the CPU included in the management server 10 executes a predetermined program (a product sales data processing program) to realize the function of the issuance instruction unit 400.

[0041] (Registration 411) The registration unit 411 registers products. The products to be registered include products to which a first tax rate is applied and products to which a second tax rate different from the first tax rate is applied. The first tax rate is a reduced tax rate, for example 8%. Products to which the first tax rate applies are products to which a reduced tax rate applies, for example, food and beverages excluding alcoholic beverages and eating out. Hereinafter, products to which the first tax rate applies are referred to as "reduced tax rate products." The second tax rate is a standard tax rate, for example 10%. Products to which the second tax rate is applied are products to which the normal tax rate is applied, for example, alcoholic beverages and eat-in (provision of services). In the following, products to which the second tax rate is applied are referred to as "normal tax rate products."

[0042] (Payment Department 412) The settlement unit 412 performs settlement for the products registered by the registration unit 411. The settlement unit 412 performs settlement using a predetermined payment type accepted by the registered settlement device 30. The settlement unit 412 acquires the application terminal code before settlement is completed. When settlement is completed, the settlement unit 412 sends a receipt issuance request to the management server 10. The receipt issuance request includes transaction information that associates the terminal ID indicated by the application terminal code with settlement information generated during settlement. When the management server 10 receives the receipt issuance request, the issuance instruction unit 400 stores the transaction information included in the receipt issuance request in the transaction information DB 11.

[0043] (An example of transaction information stored in the transaction information DB 11) Fig. 5A is a diagram showing an example of transaction information stored in the transaction information DB 11. As shown in Fig. 5A, the transaction information includes items of "transaction ID," "member information," and "payment information." "Transaction ID" is identification information that identifies a transaction. A transaction refers to the process from product registration to the completion of payment.

[0044] "Member information" includes the following items: "member ID", "terminal ID", "name", and "priority information". The "member ID" is identification information that identifies a customer who is a member. The “terminal ID” is identification information for identifying the mobile terminal device 40 . "Name" indicates the name of the member customer. The "priority information" indicates whether the issuance of eligible invoices should take priority over electronic receipts or paper receipts. Details of eligible invoices will be described later. The "priority information" is set by the customer, for example, when registering as a member. The default setting is that paper receipts are given priority.

[0045] "Settlement information" includes the following fields: "date and time", "product", "quantity", "tax rate", "price", "total amount", "payment type", and "detailed information ID". "Date and time" indicates the date and time when the transaction was made, for example, the date and time when the settlement was made. "Product" indicates the product purchased by the customer. "Quantity" indicates the purchase quantity of each product. "Tax rate" indicates the tax rate (reduced tax rate or normal tax rate) imposed on each product. "Price" indicates the selling price of each product (e.g., including tax). "Total amount" indicates the total selling price of all items (for example, including tax). Note that "Total amount" is an amount taking into account discounts, which will be described later with reference to FIG. 5B. "Payment type" indicates the payment type selected for payment. "Detailed information ID" indicates identification information for identifying the detailed amount information shown in FIG. 5B. By inputting data into each item, transaction information is entered into transaction information DB11 as a record.

[0046] (Example of detailed amount information) FIG. 5B is a diagram showing an example of amount detailed information. In the figure, the amount detailed information is described as information associated with the settlement information, but is included in the settlement information. That is, the amount detailed information is stored in the transaction information DB11 together with the transaction information. As shown in FIG. 5B, the amount detailed information is associated with a "detailed information ID." The amount detailed information includes the items of "tax amount before discount," "discount type," "discount amount," "tax amount including discount," "discount price," and "tax amount after discount." Details of calculation examples of each amount will be described later. "Tax amount before discount" refers to the tax amount at the price before discount. This tax amount is the tax amount to which the reduced tax rate or the standard tax rate is applied. "Discount type" indicates the type of discount, such as points, coupons, or sale items. "Discount amount" indicates the amount deducted from the price or the amount to be discounted. "Tax amount included in discount amount" refers to the tax amount included in the discount amount. This tax amount is the tax amount to which the reduced tax rate or standard tax rate is applied. "Discounted price" indicates the price after discount. "Tax amount after discount" refers to the tax amount on the discounted price. This tax amount is the tax amount to which the reduced tax rate or the standard tax rate is applied. By inputting data into each item, detailed amount information is input as a record.

[0047] (Regarding receipts) The product sales data processing system 1 according to this embodiment can simultaneously issue multiple receipts for one transaction. The multiple receipts include the following documents: -Qualified invoices (described below) Non-qualified invoices Regular detailed receipt Receipts that do not include registration details. In this embodiment, an example in which qualified invoices and unqualified invoices are issued will be described.

[0048] The multiple receipts include electronic receipts and paper receipts. The electronic receipt is issued by the first issuing unit 401. The electronic receipt is a receipt in which specific information related to the tax of a transaction is displayed in a first display mode. In this embodiment, the electronic receipt is either a qualified invoice or a receipt other than a qualified invoice (hereinafter referred to as a "non-qualified invoice"). The first issuing unit 401 causes the display 306 to output the electronic receipt.

[0049] The paper receipt is issued by the second issuing unit 413. The paper receipt is a receipt in which the above-mentioned specific items are displayed in a second display mode that is different from the first display mode. In this embodiment, the paper receipt is either a qualified invoice or a non-qualified invoice. The second issuing unit 413 causes the printing unit 213 to output the paper receipt.

[0050] (Example of a receipt) FIG. 6 is an explanatory diagram showing an example of a receipt according to this embodiment. FIG. 6(A) shows a qualified invoice 600a. FIG. 6(B) shows an unqualified invoice 600b. Parts common to both qualified invoice 600a and unqualified invoice 600b will be described using the same reference numerals. Qualified invoice 600a is displayed on display 306 of mobile terminal device 40. Unqualified invoice 600b is a paper medium printed by registered settlement device 30.

[0051] (Qualified invoice 600a: first display mode) The qualified invoice 600a is based on the invoice system. Specifically, the qualified invoice 600a contains the specific items (specific items related to tax) required when a business partner applies input tax credit in a transaction. The specific items related to tax are the following (1) to (6). An invoice that lacks any of these items may not be considered a qualified invoice. (1) The name or title and business registration number of the qualified invoice issuing business. (2) Date of transaction. (3) Transaction details (that the item is subject to a reduced tax rate). (4) The total amount of consideration (excluding or including tax) divided by tax rate and the applicable tax rate. (5) Consumption tax amount, etc., divided by tax rate. (6) The name of the business entity that will receive the document. (6) may be omitted.

[0052] 6 includes, as items corresponding to specific tax-related items (1) to (6), a business entity item 601, a transaction date item 602, a transaction content item 603 (603a, 603b), a consideration item 604 (604a, 604b), a consumption tax amount item 605 (605a, 605b), and a destination item 606. Qualified invoice 600a also includes an identification code 610 that identifies the transaction to which the invoice relates.

[0053] The business item 601 includes issuing business information (Supermarket Teraoka, etc.) and a registration number (T123...). The issuing business information indicates the business issuing the receipt, specifically the name and address of the store. The registration number indicates the registration number of the invoice issuing business issued by a specified institution such as the National Tax Agency (hereinafter referred to as the "business registration number"). The business registration number is expressed in half-width characters using a specified number of letters and numbers (for example, 14 digits). Specifically, the business registration number is, for example, an "alphabetical T + 13-digit corporate number" in the case of a corporation, and an "alphabetical T + 13-digit unique number" in the case of a sole proprietor, etc.

[0054] The transaction date item 602 includes the date and time the transaction was made (Sunday, August 27, 2023, 12:00), the register number (#000011), clerk information (999...Teraoka), and receipt number (0017). The date and time the transaction was made indicates the date and time the settlement was made. For example, the register number for register number 11 is "#000011". The clerk information indicates the identification information and name of the clerk in charge of the cash register operation. The receipt number is identification information that identifies the receipt, and for example, if it is the 17th transaction, it indicates "0017".

[0055] The transaction details item 603a shows the name of the product (e.g., XX Wagyu beef) and the price (e.g., 3000 yen) purchased by the customer. In the transaction details item 603a, if the product is subject to a reduced tax rate, that fact is displayed. In the transaction details item 603b, a "*" mark indicates that the product is subject to a reduced tax rate. In the illustration, a "*" mark is displayed for a reduced tax rate product (XX Wagyu beef). On the other hand, a "*" mark is not displayed for a normal tax rate product (XX fruit liquor). In the illustration, the price for each product is displayed including tax. The subtotal amount in the transaction details item 603a shows the total price of the products that include tax. Furthermore, the total amount in the transaction details item 603a shows the total price.

[0056] The consideration item 604a includes the discount amount given by points (1000 yen) and the current total (3000 yen). The discount amount given by points indicates the points (discount amount) applied to the current payment. Note that, as will be described in detail later, the amount of consumption tax included in the discount amount given by points is calculated based on the value divided proportionally between the amount of reduced tax rate products and the amount of normal tax rate products. The current total indicates the amount obtained by subtracting the discount amount given by points from the total amount.

[0057] The consumption tax amount item 604b indicates the payment type (cash, credit card, electronic money, etc.) (for example, cash) and the payment amount (¥3000).

[0058] The consumption tax amount item 605a includes the amount subject to the reduced tax rate (¥3000), the tax amount for reduced tax rate items (¥222), the amount subject to the normal tax rate (¥1000), and the tax amount for normal tax rate items (¥90). The following explanation will be given with reference to FIG. 8. The tax amount for reduced tax rate items (¥222: "tax amount before discount" in FIG. 8) indicates the reduced tax rate portion of the total amount before discount of ¥3000 (tax included). The tax amount for normal tax rate items (¥90: "tax amount before discount" in FIG. 8) indicates the normal tax rate portion of the total amount before discount of ¥1000 (tax included).

[0059] The consumption tax amount item 605b shows the details of the consumption tax amount divided by tax rate. The consumption tax amount item 605b includes the total amount of reduced tax rate products (tax included: 2250 yen), the reduced tax rate tax amount (166 yen), the total amount of normal tax rate products (tax included: 750 yen), and the normal tax rate tax amount (68 yen). The total amount of reduced tax rate products (tax included: 2250 yen) and the total amount of normal tax rate products (tax included: 750 yen) show the amount after the discount amount obtained by dividing the discount amount by points (1000 yen) is applied. Specifically, the discount amount is the amount obtained by dividing the total amount of reduced tax rate products (3000 yen) and the total amount of normal tax rate products (1000 yen). The total amount of the reduced tax rate items (¥3,000) and the total amount of the regular tax rate items (¥1,000) are divided pro rata, resulting in 75%:25%.

[0060] Specifically, the ratio of the amount of the reduced tax rate product (¥3000) to the total amount (¥4000) is ¥3000 / ¥4000=75%. Therefore, the discount amount for the reduced tax rate product is ¥750, which is the discount amount given by points (¥1000) multiplied by 75%. Therefore, the total amount after discount for the reduced tax rate product is ¥2250 (¥3000-¥750: "Discounted price" in Figure 8). The tax amount for the reduced tax rate product (¥166: "Discounted tax amount" in Figure 8) indicates the reduced tax rate portion of the discounted total amount of ¥2250 (tax included).

[0061] Additionally, the ratio of the amount of regular tax rate items (¥1000) to the total amount (¥4000) is ¥1000 / ¥4000=25%. Therefore, the discount amount for regular tax rate items is ¥250, which is the discount amount given by points (¥1000) multiplied by 25%. Therefore, the total amount after discount for regular tax rate items is ¥750 (¥1000-¥250: "Discounted price" in Figure 8). The tax amount for regular tax rate items (¥68: "Tax amount after discount" in Figure 8) indicates the regular tax rate portion of the discounted total amount of ¥750 (tax included).

[0062] Next, the consumption tax amount (¥77) on the discount amount (¥1000) by points in the consideration item 604a will be described in detail. As mentioned above, the discount amount for reduced tax rate products is ¥750, which is the discount amount (¥1000) by 75%. The tax amount for the reduced tax rate portion of ¥750 is ¥55 ("tax amount included in discount" in FIG. 8). Also, as mentioned above, the discount amount for normal tax rate products is ¥250, which is the discount amount (¥1000) by 25%. The tax amount for the normal tax rate portion of ¥250 is ¥22 ("tax amount included in discount" in FIG. 8). The consumption tax amount (¥77) on the discount amount (¥1000) by points is the sum of the tax amount for the reduced tax rate portion (¥55) and the tax amount for the normal tax rate portion (¥22).

[0063] The destination item 606 indicates the name or title of the person (customer) to whom the receipt (qualified invoice 600a) is to be delivered. The name or title entered in the destination item 606 may be entered by hand, or the registered settlement device 30 may accept the entry of the name or title and print the accepted content. The entry may be accepted from the clerk-side display unit 210 by operation of the clerk, or from the customer-side display unit 205 by operation of the customer.

[0064] The identification code 610 includes a transaction ID. The registered settlement device 30 can obtain transaction information corresponding to the transaction ID by reading the identification code 610 and inquiring of the management server 10. This makes it possible to issue a receipt (a "non-detailed receipt" described later), return the product, or make corrections.

[0065] (Non-qualified invoice 600b: second display mode) Unqualified invoice 600b differs from qualified invoice 600a in the display format for some of the above items 601 to 606. In the figure, one of the items is the business registration number in business item 601. Specifically, in unqualified invoice 600b, the business registration number is displayed with a strikethrough.

[0066] Some of the items may be other information included in the business item 601, or may be items 602-606 other than the business item 601 (for example, the consumption tax amount item 605). The display mode of some of the items on the non-qualified invoice 600b is not limited to a display mode in which a strikethrough is added, but may be a display mode in which a predetermined mark (for example, "*") is added to some of the items, or a display mode in which some of the items are not displayed. For example, one of the consumption tax items 605a and 605b may be deleted, or part of the consumption tax item 605a may be deleted, or part of the consumption tax item 605b may be deleted.

[0067] Additionally, the qualified invoice 600a may be displayed to indicate that it is a qualified invoice or meets the requirements for a qualified invoice, while the unqualified invoice 600b may be displayed to indicate that it is not a qualified invoice or does not meet the requirements for a qualified invoice.

[0068] (Receipt production request and production instruction unit 400) The receipt issue request sent from the registered settlement device 30 to the management server 10 includes the type of receipt to be issued (whether it is a qualified invoice 600a or not). Specifically, the registered settlement device 30 sends a receipt issue request including the type of receipt to the management server 10 based on a pre-setup or an operation by an operator (for example, pressing the issue button for qualified invoices 600a).

[0069] When the management server 10 receives a receipt issuance request, the issuance instruction unit 400 references the priority information stored in the transaction information DB 11 and sends receipt issuance instructions to the registered settlement devices 30 and the mobile terminal devices 40. The issuance instructions include an instruction to issue a qualified invoice 600a or an instruction to issue a non-qualified invoice 600b, as well as settlement information (including detailed amount information).

[0070] For example, if the priority information indicates an electronic receipt, the issuance instruction unit 400 instructs the mobile terminal device 40 to issue a qualified invoice 600a. This causes the first issuance unit 401 to display the qualified invoice 600a on the display 306 as an electronic receipt. In this case, the issuance instruction unit 400 also instructs the registered settlement device 30 to issue an unqualified invoice 600b. This causes the second issuance unit 413 to cause the printing unit 213 to print the unqualified invoice 600b as a paper receipt.

[0071] (Processing related to receipt issuance performed by management server 10 of this embodiment) Figure 7 is a flow chart showing an example of the process for issuing a receipt performed by the management server 10 of this embodiment. In Figure 7, the management server 10 determines whether settlement has been completed at the registered settlement device 30 and whether a receipt issuance request has been received from the registered settlement device 30 (step S701). The management server 10 waits until a receipt issuance request is received (step S701: NO). When the management server 10 receives a receipt issuance request (step S701: YES), it determines whether the request is a request to issue a qualified invoice 600a (step S702).

[0072] If the request is for issuance of the qualified invoice 600a (step S702: YES), the management server 10 refers to the priority information stored in the transaction information DB 11 (step S703). The management server 10 then determines whether the priority information indicates an electronic receipt (step S704). If the priority information indicates an electronic receipt (step S704: YES), the management server 10 sends an instruction to issue the qualified invoice 600a to the mobile terminal device 40 (step S705). This causes the mobile terminal device 40 to display the qualified invoice 600a on the display 306 as an electronic receipt.

[0073] Furthermore, the management server 10 transmits an instruction to issue the non-qualified invoice 600b to the registered settlement device 30 (step S706). As a result, the registered settlement device 30 causes the printing unit 213 to print the non-qualified invoice 600b as a paper receipt.

[0074] In step S704, if the priority information does not indicate an electronic receipt (step S704: NO), that is, if the priority information indicates a paper receipt, the management server 10 sends an issue instruction for the qualified invoice 600a to the registered settlement device 30 (step S707). As a result, the registered settlement device 30 causes the printing unit 213 to print the qualified invoice 600a as a paper receipt. Furthermore, the management server 10 sends an issue instruction for the unqualified invoice 600b to the mobile terminal device 40 (step S708). As a result, the mobile terminal device 40 causes the display 306 to display the unqualified invoice 600b as an electronic receipt.

[0075] In step S702, if the request is not for the issuance of a qualified invoice 600a (step S702: NO), that is, if the request is for the issuance of an unqualified invoice 600b, the management server 10 sends an instruction to issue the unqualified invoice 600b to the registered settlement device 30 (step S709). As a result, the registered settlement device 30 causes the printing unit 213 to print the unqualified invoice 600b as a paper receipt.

[0076] The management server 10 then proceeds to step S708 and transmits an instruction to issue the non-qualified invoice 600b to the mobile terminal device 40. As a result, the mobile terminal device 40 displays the non-qualified invoice 600b on the display 306 as an electronic receipt.

[0077] In addition, if it is desired to avoid issuing both qualified invoices 600a and unqualified invoices 600b to customers due to store operations, the unqualified invoice 600b on the paper receipt issued in step S706 or step S709 may not be issued to the customer.

[0078] Furthermore, in steps S708 and S709, unqualified invoices 600b displaying the same content are issued. For this reason, one unqualified invoice 600b may be displayed differently from the other unqualified invoice 600b (for example, by deleting the version number, the fact that it is a copy, or the word "receipt"), or a paper receipt of the unqualified invoice 600b may not be given to the customer.

[0079] Also, steps S708 and S709 may be performed in at least one of two ways. That is, if a qualified invoice is not to be issued (step S702: NO), an instruction to issue an unqualified invoice 600b may be sent to one of the mobile terminal device 40 and the registered settlement device 30. The destination of the issuance instruction may be a preset device, or, if priority information (priority information indicating which priority is given to the issuance of unqualified invoices 600b for each customer) is registered, the destination of the issuance instruction may be a device indicated by the priority information.

[0080] (Effects of the embodiment) As described above, the management server 10 according to this embodiment issues a qualified invoice 600a with specific items related to the tax of a transaction in a first display format, and issues a non-qualified invoice 600b with the specific items in a second display format. This makes it possible to prevent multiple receipts (qualified invoices 600a) that have the same effect in terms of tax deductions from being issued for a single transaction. This makes it possible to prevent fraudulent expense recording, thereby supporting proper transactions.

[0081] Furthermore, in this embodiment, the multiple receipts include electronic receipts and paper receipts. This allows either the electronic receipt or the paper receipt to be issued as the qualified invoice 600a. In other words, it is possible to issue electronic receipts and paper receipts according to the customer's needs while preventing multiple qualified invoices 600a from being issued. This improves the convenience of transactions.

[0082] In this embodiment, the specific items related to tax include at least one of the business registration number assigned to the business and the consumption tax amount divided by tax rate. As a result, for the unqualified invoice 600b, it is sufficient to display either the business item 601 or the consumption tax amount item 605 in a different manner from that of the qualified invoice 600a, so that the unqualified invoice 600b can be easily issued.

[0083] For example, the registered settlement device 30 may read the membership card (membership information) presented by the customer, and if the priority information included in the membership information indicates an electronic receipt, it may issue a paper receipt. In this case, the registered settlement device 30 issues a non-qualified invoice 600b on a paper receipt. In other words, the registered settlement device 30 issues a paper receipt with the specific information printed on the paper receipt in a different display format than the qualified invoice 600a. This makes it easy to issue a non-qualified invoice 600b on a paper receipt.

[0084] Furthermore, if the registered settlement device 30 does not read the membership card (membership information) presented by the customer, or if the priority information included in the membership information indicates a paper receipt, it may print a normal paper receipt. A normal paper receipt is, for example, a qualified invoice 600a. However, a normal paper receipt may also be an unqualified invoice 600b, or may not include at least one of the specific items (1) to (6) related to taxes.

[0085] (Modification of the embodiment) Next, modified examples of the embodiment will be described. In the following modified examples, the contents described in the above-mentioned embodiment will be omitted as appropriate. In addition, each of the following modified examples and the above-mentioned embodiment can be combined with each other.

[0086] (Variation 1) First, we will explain Variation 1. In the above embodiment, we have explained an example in which an electronic receipt and a paper receipt are issued simultaneously. In Variation 1, we will explain an example in which one of the electronic receipt and the paper receipt is issued first as a qualified invoice 600a when the transaction is completed, and then the other is additionally issued later (on the same day or at a later date) as an unqualified invoice 600b.

[0087] (Electronic receipt is issued first) First, an example in which an electronic receipt is issued first, and then a paper receipt is issued as an additional receipt will be described. In the first variation, during a transaction, the mobile terminal device 40 displays a qualified invoice 600a as an electronic receipt in response to an issuance instruction from the management server 10. After the transaction is completed, the registered settlement device 30 accepts pressing of a predetermined issue button to issue an additional paper receipt, and acquires a transaction ID (identification code 610 in FIG. 6) displayed on the electronic receipt. The transaction ID is acquired, for example, by the store clerk scanner unit 212 reading the identification code 610. Upon acquiring the transaction ID, the registered settlement device 30 inquires of the management server 10 and acquires settlement information corresponding to the transaction ID.

[0088] When the registered settlement device 30 acquires the settlement information, it prints a paper receipt based on the settlement information. The paper receipt is a non-qualified invoice 600b, that is, a receipt that does not meet the requirements of a qualified invoice 600a. The registered settlement device 30 may display the number of additional issues on the paper receipt. In this case, the management server 10 may store the number of additional issues in the transaction information DB 11. The registered settlement device 30 may display the number of additional issues on the store clerk display unit 210, etc., when it receives a press of a specified issue button.

[0089] (A paper receipt is issued first) Next, an example will be described in which a paper receipt is issued first, and then an electronic receipt is issued. At the time of the transaction, the registered settlement device 30 prints a qualified invoice 600a as a paper receipt. Then, after the transaction is completed, the registered settlement device 30 acquires the transaction ID (identification code 610 in FIG. 6) displayed on the paper receipt when issuing an additional electronic receipt. The transaction ID is acquired, for example, by the store clerk scanner unit 212 reading the identification code 610. Upon acquiring the transaction ID, the registered settlement device 30 requests the management server 10 to issue an electronic receipt. The management server 10 identifies the terminal ID (FIG. 5A) corresponding to the transaction ID, and transmits settlement information to the mobile terminal device 40 indicated by the terminal ID.

[0090] When the mobile terminal device 40 acquires the settlement information, it displays an electronic receipt based on the settlement information. The electronic receipt is a non-qualified invoice 600b, that is, a receipt that does not satisfy the requirements of a qualified invoice 600a. The mobile terminal device 40 may display the number of additional issuances on the electronic receipt.

[0091] If a customer loses the qualified invoice 600a as a paper receipt, the registered settlement device 30 may reprint the paper receipt (qualified invoice 600a) upon receiving an electronic receipt (unqualified invoice 600b) from the customer. In this case, the registered settlement device 30 may print a notice indicating reissue on the qualified invoice 600a, or may print the reason for reissue by accepting input of the reason for reissue.

[0092] In the first modification, an example is described in which qualified invoice 600a is issued first, and then unqualified invoice 600b is issued, but this is not limited to the above. For example, unqualified invoice 600b may be issued first, and then qualified invoice 600a may be issued. Specifically, one of the electronic receipt and the paper receipt may be issued as unqualified invoice 600b when the transaction is completed, and the other may be issued later (on the same day or at a later date) as qualified invoice 600a.

[0093] After issuing the qualified invoice 600a as an electronic receipt, a customer may wish to issue (change) the qualified invoice 600a as a paper receipt. In this case, the registration settlement device 30 accepts the change to the qualified invoice 600a as a paper receipt. The change may be accepted by either the customer side display unit 205 or the clerk side display unit 210. The registration settlement device 30 then queries the management server 10, and prints the qualified invoice 600a as a paper receipt for the transaction in response to the issuance instruction from the management server 10. Furthermore, the management server 10 issues a change instruction to the mobile terminal device 40 to display the unqualified invoice 600b as an electronic receipt. Upon receiving the change instruction, the mobile terminal device 40 displays the unqualified invoice 600b. In this way, it is possible to change the display medium (paper or display) of the qualified invoice 600a after the fact.

[0094] (Effects of Modification 1) As described above, the product sales data processing system 1 according to the first modification first issues a qualified invoice 600a when a transaction is completed, and then (on the same day or at a later date) issues an additional unqualified invoice 600b. This makes it possible to avoid issuing multiple receipts (qualified invoices 600a) with the same effect for one transaction, even if a customer requests a reissue of the receipt after the fact.

[0095] (Variation 2) Next, Variation 2 will be described. In the above embodiment, an example was described in which qualified invoices 600a and unqualified invoices 600b are issued as electronic receipts or paper receipts. Variation 2 will describe an example in which qualified invoices 600a and unqualified invoices 600b are issued as paper receipts only. Note that the following describes the case in which a receipt that does not include registered details (hereinafter referred to as a "non-detailed receipt") is issued after a detailed receipt including registered details has been issued (on the same day or at a later date).

[0096] (Functional configuration of product sales data processing system 1 according to modification 2) FIG. 8 is a diagram showing an example of the functional configuration of a product sales data processing system 1 according to the second modification. As shown in FIG. 8, the product sales data processing system 1 does not include a mobile terminal device 40. The registration and settlement device 30 further includes an issuance instruction unit 801 in addition to the functional units shown in the embodiment. The issuance instruction unit 801 issues a detailed receipt upon completion of a transaction. The detailed receipt is, for example, similar to the qualified invoice 600a in FIG. 6. Specific items are displayed on the detailed receipt in a first display mode.

[0097] After the transaction is completed, the customer requests a non-detailed receipt. The issuance instruction unit 801, in response to the clerk's operation, causes the second issuing unit 413 to issue an additional non-detailed receipt. Non-detailed receipts include qualified invoices and unqualified invoices. Qualified invoices and unqualified invoices each have specific information displayed in the second display mode.

[0098] (Regarding non-itemized receipts) FIG. 9 is a diagram showing an example of a non-detailed receipt according to the second modification. FIG. 9(A) shows a qualified invoice 900a among non-detailed receipts. FIG. 9(B) shows a non-qualified invoice 900b among non-detailed receipts. As shown in FIG. 9(A), the qualified invoice 900a includes a business entity item 901, a transaction date item 902, a transaction details item 903, a consideration item 904, and a consumption tax amount item 905 as items corresponding to the specific items (1) to (5) shown in the embodiment. The qualified invoice 900a also includes an identification code 910 that identifies the transaction to which the invoice pertains. The transaction details item 903 is written in a simplified manner compared to the transaction details item 603 shown in FIG. 6.

[0099] Unqualified invoice 900b shown in Figure 9(B) differs from qualified invoice 900a in the display format for some of the above items 901 to 905. In the figure, one of the items is the business registration number in business item 901. Specifically, in unqualified invoice 900b, the business registration number is displayed with a strikethrough.

[0100] Some of the items may be other information included in the business item 901, or may be items 902-905 (for example, consumption tax amount item 905) other than the business item 901. The display mode of some of the items on the non-qualified invoice 900b is not limited to a display mode in which a strikethrough is added, but may be a display mode in which some of the items are added with a specified mark (for example, "*"), or a display mode in which some of the items are not displayed.

[0101] Additionally, the qualified invoice 900a may be displayed to indicate that it is a qualified invoice or meets the requirements for a qualified invoice, while the unqualified invoice 900b may be displayed to indicate that it is not a qualified invoice or does not meet the requirements for a qualified invoice.

[0102] In the second modification, when issuing an additional non-detailed receipt, the issuance instruction unit 801 acquires the transaction ID (identification code 610 in FIG. 6) printed on the detailed receipt. The transaction ID is acquired, for example, by the store clerk scanner unit 212 reading the identification code 610. Upon acquiring the transaction ID, the issuance instruction unit 801 queries the management server 10 to acquire the settlement information corresponding to the transaction ID.

[0103] When the settlement information is acquired, the issuance instruction unit 801, for example, causes the clerk's display unit 210 to display an exchange button and an additional issue button. The exchange button is a button that accepts the issuance of an additional non-detailed receipt in exchange for a previously issued detailed receipt. When the exchange button is pressed, the issuance instruction unit 801 causes the second issuing unit 413 to issue a qualified invoice 900a as a non-detailed receipt. In this case, the clerk collects the detailed receipt presented by the customer.

[0104] The additional issuance button is a button that accepts the issuance of an additional non-detailed receipt without collecting the detailed receipt previously issued by the second issuing unit 413. When the additional issuance button is pressed, the issuance instruction unit 801 causes the second issuing unit 413 to issue a non-qualified invoice 900b as a non-detailed receipt. In this case, it is possible to issue only the non-qualified invoice 900b. However, even in this case, it may be possible to reissue the qualified invoice 900a by operation of an authorized administrator (e.g., the store manager).

[0105] (Non-detailed receipt issuing process performed by the registered settlement device 30 according to the second modified example) 10 is a flowchart showing an example of a non-detailed receipt issuing process performed by the registered settlement device 30 according to Modification 2. Note that the following process is performed after one transaction for which a detailed receipt has been issued by the second issuing unit 413 is completed.

[0106] In Fig. 10, the registered settlement device 30 determines whether or not a request for a non-detailed receipt has been accepted (step S1001). The registered settlement device 30 waits until it accepts the request for a non-detailed receipt (step S1001: NO). When the registered settlement device 30 accepts the request for a non-detailed receipt (step S1001: YES), the store clerk has the store clerk scanner unit 212 read the identification code 610 (see Fig. 6) printed on the detailed receipt (qualified invoice 600a), and the transaction ID is obtained.

[0107] The registered settlement device 30 then requests the management server 10 to send settlement information corresponding to the transaction ID (step S1003), and receives the settlement information from the management server 10 (step S1004). The registered settlement device 30 then determines whether to issue a non-detailed receipt in exchange for the detailed receipt (step S1005).

[0108] If a non-detailed receipt is to be issued in exchange for the detailed receipt (step S1005: YES), i.e., if the exchange button is pressed, the registered settlement device 30 issues a qualified invoice 900a as a non-detailed receipt (step S1006) and ends the series of processes. On the other hand, if a non-detailed receipt is not to be issued in exchange for the detailed receipt (step S1005: NO), i.e., if the additional issue button is pressed, the registered settlement device 30 issues a non-qualified invoice 900b as a non-detailed receipt (step S1007) and ends the series of processes.

[0109] In the second modification, the transaction information DB 11 is provided in the management server 10, but is not limited to this. The transaction information DB 11 may be provided in the registered settlement device 30 or in the store controller 20. In this case, in step S1003, the registered settlement device 30 requests the device itself or the store controller 20 to transmit settlement information, and in step S1004, receives the settlement information from the destination of the transmission request.

[0110] (Effects of Modification 2) As described above, the product sales data processing system 1 of the second variant issues a qualified invoice 900a (second display mode) or an unqualified invoice 900b as a non-detailed receipt after the completion of a transaction in which a detailed receipt (qualified invoice 600a: first display mode) has been issued. This makes it possible to issue a qualified invoice 900a even after a transaction has been completed. Furthermore, if the detailed receipt (qualified invoice 600a) cannot be collected from the customer, an unqualified invoice 900b is issued, thereby preventing the existence of multiple qualified invoices (qualified invoice 600a and qualified invoice 900a) with the same validity.

[0111] (Variation 3) Next, a description will be given of Variation 3. In Variation 2 described above, an example was described in which a detailed receipt and a non-detailed receipt are printed on separate paper media. In Variation 3, an example will be described in which a detailed receipt and a non-detailed receipt are printed on a single paper medium.

[0112] In the third variation, the issuing instruction unit 801 (FIG. 8) controls the second issuing unit 413 to issue a qualified invoice that combines a detailed receipt and a non-detailed receipt on a single paper medium. The detailed receipt displays specific items in a first display format. The non-detailed receipt displays specific items in a second display format.

[0113] (An example of a qualified invoice relating to Modification 3) Figure 11 is a diagram showing an example of a qualified invoice related to Variation 3. As shown in Figure 11 (A), qualified invoice 1100 includes a non-detailed receipt 1101 and a detailed receipt 1102. Non-detailed receipt 1101 includes items corresponding to (1) to (3) of the specific items (1) to (5) shown in the embodiment (business entity item 901, transaction date item 902, and transaction details item 903).

[0114] Of the specific items (1) to (5), the detailed receipt 1102 includes items that correspond to (2) to (5) (transaction date item 602, transaction details items 603a, 603b, consideration items 604a, 604b, and consumption tax amount items 605a, 605b). Therefore, qualified invoice 1100 meets the requirements for a qualified invoice because it includes specific items (1) to (5).

[0115] Now, let us assume that the customer separates the non-detailed receipt 1101 from the detailed receipt 1102. In this case, the non-detailed receipt 1101 does not meet the requirements for a qualified invoice because the consideration items 604a, 604b and the consumption tax amount item 605 are not listed. Furthermore, the detailed receipt 1102 does not meet the requirements for a qualified invoice because the business item 901 is not listed. In other words, even if the qualified invoice 1100 is separated, there will not be multiple documents that qualify as a qualified invoice.

[0116] Figure 11(b) is another example of a qualified invoice relating to Variation 3. As shown in Figure 11(b), qualified invoice 1110 includes a non-detailed receipt 1111 and a detailed receipt 1112. The non-detailed receipt 1111 includes items corresponding to (1) to (4) of the specific items (1) to (5) shown in the embodiment (business entity item 901, transaction date item 902, transaction details item 903, and consideration item 904).

[0117] Of the specific items (1) to (5), the detailed receipt 1112 includes items corresponding to (2), (3), and (5) (transaction date item 602, transaction details items 603a and 603b, and consumption tax amount items 605a and 605b). Therefore, the qualified invoice 1110 includes specific items (1) to (5) and therefore meets the requirements for a qualified invoice.

[0118] Now, let us assume that the customer separates the non-detailed receipt 1111 from the detailed receipt 1112. In this case, because the consumption tax amount items 605a and 605b are not listed on the non-detailed receipt 1111, the non-detailed receipt 1111 does not meet the requirements for a qualified invoice. Furthermore, because the detailed receipt 1112 does not list the business item 901 and the consideration item 904, the detailed receipt 1112 also does not meet the requirements for a qualified invoice. In other words, even if the qualified invoice 1110 is separated, there will not be multiple documents that qualify as qualified invoices.

[0119] (Effects of Modification 3) As described above, the registered settlement device 30 (second issuing unit 413) according to the third variant issues a qualified invoice 1100 (1110) that combines a detailed receipt 1102 (1112) in which specific items are displayed in a first display mode and a non-detailed receipt 1101 (1111) displayed in a second display mode on a single paper medium. This makes it possible to issue a qualified invoice that includes a detailed receipt and a non-detailed receipt when a transaction is completed, without the customer needing to request this from a store clerk. It also reduces the workload of store clerks in creating qualified invoices. Furthermore, it is possible to prevent multiple documents from existing as a qualified invoice.

[0120] The embodiments will be summarized below. [Name of invention] System and program [Technical field] The present invention relates to a system and a program. [Background technology] Conventionally, cash registers have been able to print receipts and invoices. In particular, electronic receipts that display computerized receipts on mobile terminal devices such as smartphones have become widespread in recent years. For example, a system is known that allows a paper receipt to be printed after a transaction for which an electronic receipt has been output (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2013-175212 A [Summary of the invention] [Problem to be solved by the invention] However, in the conventional technology, if the tax deduction information is displayed on both the electronic receipt and the paper receipt, multiple receipts with the same effect will exist for one transaction. This can lead to problems such as fraudulent expense recording, and thus the inability to carry out a proper transaction. The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of supporting appropriate transactions.

[0121] [Means for solving the problem] (1) In order to solve the above-mentioned problems, one aspect of the present invention is a system capable of issuing multiple receipts for a single transaction, characterized in that the system includes an issuance instruction means for causing each of the multiple receipts to be issued with specific tax-related information for the single transaction displayed in a different manner among the multiple receipts. The above configuration makes it possible to prevent multiple receipts (qualified invoices 600a) that have the same effect in terms of tax deductions from being issued for one transaction, thus preventing fraudulent expense recording and supporting proper transactions.

[0122] (2) In the configuration of (1) above, the issuance instruction means may be configured to issue another receipt of the plurality of receipts after completion of the one transaction for which one receipt of the plurality of receipts has been issued. With the above configuration, qualified invoice 900a can be issued even after one transaction has been completed. Also, if the detailed receipt (qualified invoice 600a) cannot be collected from the customer, a non-qualified invoice 900b is issued, which prevents the existence of multiple qualified invoices (qualified invoice 600a and qualified invoice 900a) with the same validity.

[0123] (3) In the configuration of (1) or (2) above, the multiple receipts may include electronic receipts and paper receipts. According to the above configuration, either an electronic receipt or a paper receipt can be issued as the qualified invoice 600a. In other words, it is possible to issue electronic receipts and paper receipts according to the customer's needs while preventing multiple qualified invoices 600a from being issued. This improves the convenience of transactions.

[0124] (4) In the configuration of (1) or (2) above, the specific information may include at least one of a registration number assigned to the business operator and a consumption tax amount divided by tax rate. According to the above configuration, for non-qualified invoices 600b, it is only necessary to change the display mode of either the business item 601 or the consumption tax amount item 605 to a different display mode from that of qualified invoices 600a, so that non-qualified invoices 600b can be easily issued.

[0125] (5) In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes a computer to function as a system capable of issuing multiple receipts for a single transaction, characterized in that the program causes the computer to function as an issuance instruction means that issues each receipt by displaying specific information related to taxes for the single transaction in a different manner among the multiple receipts. The above configuration makes it possible to prevent multiple receipts (qualified invoices 600a) that have the same effect in terms of tax deductions from being issued for one transaction, thus preventing fraudulent expense recording and supporting proper transactions.

[0126] In addition, all or part of each function (input / output, memory, processing (including judgment)) of the product sales data processing system 1 (management server 10, registration settlement device 30, and mobile terminal device 40) described above may be realized in a device other than the device described as the entity that executes the function.

[0127] Specifically, in the above description, the management server 10, the registration settlement device 30, and the mobile terminal device 40 are configured to include the functional units shown in FIG. 4 and FIG. 8. All or part of each functional unit may be included in another computer device. For example, all or part of each functional unit may be included in the store controller 20, or may be included in another computer device. In addition, the number of computer devices on which each functional unit is included is not limited to multiple, and may be one. For example, one computer device may include all of the functional units.

[0128] Specifically, for example, instead of the management server 10, the store controller 20 may instruct the mobile terminal device 40 to issue a qualified invoice 600a with the above-mentioned specific items in a first display mode, and instruct the registered settlement device 30 to issue an unqualified invoice 600b with the above-mentioned specific items in a second display mode.

[0129] In relation to the above, the registration settlement device 30 and the mobile terminal device 40 may function as a so-called thin client specialized in the input / output interface portion with respect to various displays, etc. In other words, the registration settlement device 30 and the mobile terminal device 40 may accept various inputs (operator operations and device detection), transmit input information (operation information, detection information, etc.) to the management server 10, receive the processing results of the management server 10 based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

[0130] The programs for implementing the above-described product sales data processing system 1, management server 10, registration settlement device 30, and mobile terminal device 40 may be recorded in a computer-readable storage medium, and the programs may be read and executed by a computer system. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable storage medium" refers to portable media such as USB (Universal Serial Bus) flash memory, SSD (Solid State Drive), flexible disk, optical magnetic disk, ROM, CD-ROM, and storage devices such as hard disks built into a computer system. The term "computer-readable storage medium" also refers to storage devices that hold a program for a certain period of time, such as volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The above-mentioned program may be transmitted from a computer system that stores the program in a storage device, etc., to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The above program may also be one that realizes part of the above-mentioned functions. Furthermore, it may be a so-called differential file (differential program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system. [Explanation of symbols]

[0131] Reference Signs List 1...Product sales data processing system, 10...Management server, 11...Transaction information DB, 20...Store controller, 30...Registration and settlement device, 40...Mobile terminal device, 213...Printing unit, 306...Display, 400...Issuance instruction unit, 401...First issuing unit, 411...Registration unit, 412...Settlement unit, 413...Second issuing unit, 600a...Qualified invoice, 600b...Non-qualified invoice, 801...Issuance instruction unit, 900a...Qualified invoice, 900b...Non-qualified invoice, 1100...Qualified invoice, 1110...Qualified invoice

Claims

1. A system capable of issuing multiple receipts for one transaction, The system further comprises an issuance instruction means for causing each of the plurality of receipts to be issued with the specific item relating to the tax on the one transaction displayed in a different manner among the plurality of receipts.

2. the issuing instruction means issues another receipt out of the plurality of receipts after completion of the one transaction for which one receipt out of the plurality of receipts has been issued, 2. The system of claim 1 .

3. The plurality of receipts includes electronic receipts and paper receipts.

3. The system according to claim 1 or 2.

4. The specific information includes at least one of a registration number assigned to the business operator and a consumption tax amount divided by tax rate.

3. The system according to claim 1 or 2.

5. A program that causes a computer to function as a system capable of issuing multiple receipts for one transaction, The computer, a program that functions as an issuance instruction means for issuing each receipt by displaying specific information related to the tax on the one transaction in a different manner among the plurality of receipts;

Images