Sales data processing device

Abstract

To make electronic receipts suitable for the invoice system. [Solution] A sales data processing device that provides a customer with a receipt for a sales transaction, comprising: a receipt provision method identification means that identifies a method of providing the customer with the receipt; and a receipt data generation means that generates receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means, wherein when the receipt data generation means generates receipt data for an electronic receipt that will be a qualified invoice, it does not generate receipt data for a paper receipt that will be a qualified invoice.

Description

Technical Field

[0001] The present invention relates to a sales data processing apparatus.

Background Art

[0002] Techniques related to the issuance of electronic receipts are known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, for example, in relation to the invoice system (qualified invoice preservation method), there is room for improvement in electronic receipts.

[0005] <l The present invention has been made in view of such circumstances, and an object thereof is to provide a technique for suitably adapting an electronic receipt to an invoice system.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-described problems is a sales data processing apparatus that provides a receipt for a transaction related to sales to a customer, the apparatus including receipt providing method specifying means for specifying a method of providing the receipt to the customer, and receipt data generating means for generating receipt data of the receipt to be provided to the customer according to the providing method specified by the receipt providing method specifying means, wherein when the receipt data generating means generates receipt data for an electronic receipt that becomes a qualified invoice, the receipt data generating means does not generate receipt data for a paper receipt that becomes a qualified invoice.

Brief Description of the Drawings

[0007] [Figure 1] This figure shows an example of the system configuration according to this embodiment. [Figure 2] This is an explanatory diagram describing various file types. [Figure 3] This is an explanatory diagram describing the output of electronic and paper receipts. [Figure 4] This is an explanatory diagram describing the receipt settings information. [Figure 5] This is a flowchart illustrating an example of the operation of the registration and settlement device. [Figure 6] This is a flowchart illustrating an example of the operation of the registration and settlement device. [Figure 7] This is an example of a screen from a registration and payment device. [Figure 8] These are examples of paper and electronic receipts. [Figure 9] This is an example of a screen from a registration and payment device. [Figure 10] This is an example of a screen from a registration and payment device. [Modes for carrying out the invention]

[0008] Figure 1 shows an example configuration of System 1 according to this embodiment. System 1 is applicable to various types of businesses (supermarkets, convenience stores, drugstores, home centers, consumer electronics retailers, etc.). System 1 is capable of outputting receipts (invoices) that comply with the invoice system.

[0009] System 1, as shown in Figure 1, includes a registration and settlement device 10, a customer management server 20, a transaction management server 30, and an electronic receipt management server 40. The registration and settlement device 10 is installed in the store. The customer management server 20, transaction management server 30, and electronic receipt management server 40 are installed at headquarters (which may be a data center).

[0010] As indicated by the arrows, the registration and settlement device 10 can communicate with the headquarters' servers (customer management server 20, transaction management server 30, electronic receipt management server 40) via the internet or other means, either through other devices (for example, a store controller installed in the store (not shown)) or without other devices. Although Figure 1 shows one registration and settlement device 10, there may be two or more registration and settlement devices 10.

[0011] The servers on the headquarters side (customer management server 20, transaction management server 30, and electronic receipt management server 40) may be able to communicate with each other. For example, although the arrows are omitted, customer management server 20 and transaction management server 30 may be able to communicate with each other. The same applies to other combinations.

[0012] The customer terminal 50 is the customer's (member's) device (e.g., a smartphone, tablet, or personal computer). The customer terminal 50 communicates with the electronic receipt management server 40. For example, the customer terminal 50 accesses the electronic receipt management server 40 and displays an electronic receipt. Although Figure 1 shows one customer terminal 50, there are multiple customer terminals 50. Also, in the following explanation, the customer terminal 50 will be assumed to be a smartphone.

[0013] (Registration and settlement device 10) The registration and payment device 10 performs a registration process to register products and a payment process to settle the price of the products registered through the registration process. The registration and payment device 10 may be a device that registers products and settles payments based on the operations of a store clerk (store clerk operation device). The registration and payment device 10 may be a device that registers products and settles payments based on the operations of a customer (full self-service device). The registration and payment device 10 may be a device that registers products and settles payments based on the operations of a store clerk (face-to-face semi-self-service device). The registration and payment device 10 may be a device that has multiple operating modes (for example, full self-service mode, face-to-face semi-self-service mode) (mode change device).

[0014] Although not shown in the diagram, the registration and settlement device 10 includes, for example, a CPU, a memory unit, a display unit, a cash settlement unit (change dispenser), a non-cash settlement unit, a scanner unit, a printing unit, an audio output unit, and a communication unit. If the registration and settlement device 10 is an employee-operated device (the same applies if it is a face-to-face semi-self-service device or a mode change device), it includes an employee-side display unit and a customer-side display unit as the display unit. If the registration and settlement device 10 is a fully self-service device, it includes a customer-side display unit. The non-cash settlement unit may also be externally attached as a settlement terminal. The registration and settlement device 10 may further include an information reading unit for reading information from cards (IC cards, magnetic cards), a key operation unit operated by an employee, a human presence sensor for detecting the presence of a customer or employee, a light-emitting unit used for calling an employee, a camera for capturing images of the customer or their actions, etc.

[0015] The registration and settlement device 10 registers products by scanning the barcode of the product with the scanner unit, but products may also be registered by operating the product button (product preset button) corresponding to each product.

[0016] The registration settlement device 10 can acquire customer identification information for identifying the customer of the transaction. For example, the registration settlement device 10 acquires customer identification information from the membership card carried (brought) by the customer. When it is a membership card with a barcode (a barcode encoding the customer identification information), the registration settlement device 10 acquires the customer identification information by reading the barcode on the membership card with the scanner unit. When the membership card is an IC card or a magnetic card, the registration settlement device 10 acquires the customer identification information by reading the IC chip or the magnetic stripe with the information reading unit (by placing the membership card over the information reading unit or swiping it). Note that the registration settlement device 10 may acquire customer identification information from a device carried by the customer (for example, a smartphone, a wearable terminal, etc.). For example, the registration settlement device 10 acquires the customer identification information by reading the information stored in the storage unit of the device with the information reading unit (by placing the device over the information reading unit). In the following description, it is assumed that the registration settlement device 10 acquires the customer identification information by reading the barcode on the membership card with the scanner unit.

[0017] Also, as described above, the registration settlement device 10 can output a receipt corresponding to the invoice system. In the receipt corresponding to the invoice system, the registration number of the invoice system (the "registered number of the eligible invoice issuer" of the business operator itself) is shown. When the registration settlement device 10 outputs a receipt corresponding to the invoice system, it refers to (checks) the registration number of the invoice system and outputs a receipt showing the registration number of the invoice system as the receipt corresponding to the invoice system. Note that the registration settlement device 10 may store the registration number of the invoice system in its own storage unit and refer to the registration number of the invoice system stored in its own storage unit. The registration settlement device 10 may refer to the registration number of the invoice system stored in another device. The registration settlement device 10 may also inquire another device about the registration number of the invoice system.

[0018] (Customer management server 20) The customer management server 20 manages customers (customers who have registered as members). Specifically, the customer management server 20 stores a customer file (customer master). The customer file is a file that stores customer information. The details of the customer information in the customer file will be described later (Figure 2(A)).

[0019] (Transaction management server 30)

[0020] The transaction management server 30 manages transactions. Specifically, the transaction management server 30 stores a transaction file. The transaction file is a file that stores transaction information. The transaction information in the transaction file includes, as data items, for example, transaction identification information (information that identifies a transaction. For example, a transaction number), transaction date and time, store identification information (information that identifies a store), device identification information (information that identifies a registration settlement device 10 when there are multiple registration settlement devices 10 in a store), product registration information, and settlement information (also referred to as payment information). The transaction information of a transaction for which customer identification information has been obtained further includes customer identification information as a data item.

[0021] For example, after a transaction is completed (after the settlement process is completed), the registration settlement device 10 transmits the transaction information to the transaction management server 30 (either directly or via a store controller (not shown)), and the transaction management server 30 that has received the transaction information stores the received transaction information in the transaction file. When the registration settlement device 10 has obtained customer identification information, it transmits the transaction information including the customer identification information to the transaction management server 30.

[0022] (Electronic receipt management server 40) The electronic receipt management server 40 manages electronic receipts. Specifically, the electronic receipt management server 40 stores an electronic receipt file. The electronic receipt file is a file that stores electronic receipt information. The details of the electronic receipt information in the electronic receipt file will be described later (Figure 2(B)).

[0023] (Other servers) System 1 (headquarters side) may have other servers. For example, it may have a product management server or an electronic journal management server. The product management server stores product files (product master). Product files are files that store product information. Product information in product files includes data items such as product identification information (e.g., JAN code, in-store code), product name, and price (selling price). Product information may also include data items such as cost (purchase price). The electronic journal management server stores electronic journal files. Electronic journal files are files that store electronic journal information. Electronic journal information in electronic journal files includes data items such as transaction identification information, store identification information, device identification information, and event information (information that stores various events that occurred during a transaction, such as registration, settlement-related actions or operations, reading of member identification information, deposits and withdrawals, display of various messages, etc., in chronological order or with timestamps).

[0024] Figure 2 is an explanatory diagram describing various files. Figure 2(A) is an explanatory diagram describing customer files stored by the customer management server 20. Figure 2(B) is an explanatory diagram describing electronic receipt files stored by the electronic receipt management server 40. Figures 2(C) and 2(D) will be described later.

[0025] The customer information in the customer file includes, for example, data items such as customer identification information, basic information, evaluation-related information, benefit information, and receipt setting information, as shown in Figure 2(A).

[0026] Basic information refers to information that indicates the basic attributes of the customer (the customer identified by the customer identification information). Basic information includes, for example, the customer's name (e.g., full name, nickname, etc.), contact information (e.g., telephone number, email address, etc.), attributes (e.g., date of birth, gender, etc.), and registration date and time. Basic information is information obtained from the customer when they register as a member. Customer identification information may be assigned a number when the customer registers as a member.

[0027] Evaluation information is information related to evaluations based on the customer's purchase history. Evaluation information includes, for example, customer rank, last visit date (purchase date), total purchase amount for the previous month, and number of visits (number of purchases) for the previous month. The total purchase amount and number of visits for the previous month are obtained by aggregating transaction information. The customer rank is obtained by aggregating and analyzing (classifying) transaction information.

[0028] Reward information is information related to the rewards offered to the customer. Reward information may include, for example, the number of points available. The number of points is updated based on transaction information (added when points are awarded, subtracted when points are used). Reward information may also include information about available coupons.

[0029] Receipt setting information is information related to the receipt settings of a customer. This information includes details (described below) for identifying whether the customer requires paper receipts (receipts printed on receipts), electronic receipts, and compliance with the invoice system. The receipt setting information is obtained from the customer when they register as a member, or when they change their receipt settings. Because receipt setting information controls the output of paper and electronic receipts, it is also referred to as receipt control information.

[0030] The electronic receipt information in the electronic receipt file includes, for example, customer identification information, transaction identification information, and electronic receipt information as data items, as shown in Figure 2(B). The electronic receipt information is the information that forms the basis for displaying the electronic receipt. The electronic receipt management server 40, in response to a request from a customer's customer terminal 50, refers to the electronic receipt information of that customer, generates screen information for that customer's electronic receipt, and transmits the generated screen information to the customer's customer terminal 50.

[0031] In the following explanation, receipts that comply with the invoice system may be referred to as "invoice-compliant receipts" or "invoice-compliant receipts." Furthermore, when distinguishing between electronic receipts and paper receipts, electronic receipts that comply with the invoice system may be referred to as "invoice-compliant electronic receipts" or "invoice-compliant electronic receipts," and paper receipts that comply with the invoice system may be referred to as "invoice-compliant paper receipts" or "invoice-compliant paper receipts." On the other hand, receipts that do not comply with the invoice system may be referred to as "non-invoice-compliant receipts" or "non-invoice-compliant receipts." Furthermore, when distinguishing between electronic receipts and paper receipts, electronic receipts that do not comply with the invoice system may be referred to as "non-invoice-compliant electronic receipts" or "non-invoice-compliant electronic receipts," and paper receipts that do not comply with the invoice system may be referred to as "non-invoice-compliant paper receipts" or "non-invoice-compliant paper receipts."

[0032] Figure 3 is an explanatory diagram illustrating the output of electronic and paper receipts. System 1 supports multiple output patterns for receipts (electronic and paper receipts) as shown in Figure 3 (multiple output modes are available). In the column in Figure 3, "None" indicates that no receipt output is required, "Required (Invoice)" indicates that invoice-compatible receipt output is required, and "Required (Non-Invoice)" indicates that non-invoice-compatible receipt output is required.

[0033] Output pattern 1 is a mode in which neither an electronic receipt nor a paper receipt is output. In the case of output pattern 1, the registered payment device 10 does not generate information for electronic receipts (information that forms the basis for displaying the electronic receipt; information sent to the electronic receipt management server 40) nor information for paper receipts (information that forms the basis for printing the paper receipt; information supplied to the printing unit).

[0034] Output pattern 2 is a configuration in which a paper receipt that does not support invoices is output without outputting an electronic receipt. In the case of output pattern 2, the registration settlement device 10 generates information for paper receipts that do not support invoices (it does not generate information for electronic receipts).

[0035] Output pattern 3 is a mode in which an invoice-compatible paper receipt is output without outputting an electronic receipt. In the case of output pattern 3, the registration settlement device 10 generates information for the invoice-compatible paper receipt (it does not generate information for the electronic receipt).

[0036] Output pattern 4 is a configuration in which an electronic receipt that does not support invoices is output without outputting a paper receipt. In the case of output pattern 4, the registration and settlement device 10 generates information for the electronic receipt that does not support invoices (it does not generate information for paper receipts).

[0037] Output pattern 5 is a configuration in which an invoice-compatible electronic receipt is output without printing a paper receipt. In the case of output pattern 5, the registration and settlement device 10 generates information for the invoice-compatible electronic receipt (it does not generate information for a paper receipt).

[0038] Output pattern 6 is a configuration in which an electronic receipt that does not support invoices and a paper receipt that does not support invoices are output. In the case of output pattern 6, the registration settlement device 10 generates information for the electronic receipt that does not support invoices and information for the paper receipt that does not support invoices.

[0039] Output pattern 7 is a configuration in which an invoice-compatible electronic receipt and a non-invoice-compatible paper receipt are output. In the case of output pattern 7, the registration settlement device 10 generates information for the invoice-compatible electronic receipt and information for the non-invoice-compatible paper receipt.

[0040] Output pattern 8 is a configuration in which an electronic receipt that does not support invoices and a paper receipt that supports invoices are output. In the case of output pattern 8, the registration settlement device 10 generates information for the electronic receipt that does not support invoices and information for the paper receipt that supports invoices.

[0041] The invoice system registration number is referenced when printing an invoice-compliant receipt (at least one of either an invoice-compliant electronic receipt or an invoice-compliant paper receipt). Specifically, it is referenced in output patterns 3, 5, 7, and 8.

[0042] (Example of receipt settings information) Figure 4 is an explanatory diagram illustrating receipt setting information (receipt control information). As explained earlier, receipt setting information (see Figure 2(A)), which is one of the data items of customer information in the customer file, is information related to receipt settings (control), and includes information for identifying whether paper receipts are required, whether electronic receipts are required, and whether compliance with the invoice system is required. Specifically, as shown in Figure 4(A), receipt setting information may also include electronic receipt requirement classification, paper receipt requirement classification, qualified invoice requirement classification, and qualified invoice designation classification.

[0043] The electronic receipt requirement setting indicates whether or not an electronic receipt is required. An electronic receipt requirement setting of "0" indicates that an electronic receipt is not required. An electronic receipt requirement setting of "1" indicates that an electronic receipt is required.

[0044] The "Paper Receipt Requirement Classification" is a setting that indicates whether or not a paper receipt is required. A "Paper Receipt Requirement Classification of 0" indicates that a paper receipt is not required. A "Paper Receipt Requirement Classification of 1" indicates that a paper receipt is required.

[0045] The Qualified Invoice Requirement Classification is setting information regarding whether or not compliance with the invoice system is required. A Qualified Invoice Requirement Classification of "0" indicates that compliance with the invoice system is not required. A Qualified Invoice Requirement Classification of "1" indicates that compliance with the invoice system is required.

[0046] The qualified invoice requirement category is referenced when at least one of either an electronic receipt or a paper receipt is required (i.e., when the electronic receipt requirement category is "1" and the paper receipt requirement category is "0", or when the electronic receipt requirement category is "0" and the paper receipt requirement category is "1", or when the electronic receipt requirement category is "1" and the paper receipt requirement category is "1"). Therefore, if neither an electronic receipt nor a paper receipt is required (i.e., when both the electronic receipt requirement category is "0" and the paper receipt requirement category is "0"), the qualified invoice requirement category is not set (if it is set, it may be treated as a setting error).

[0047] The Qualified Invoice Designation Category is setting information related to the designation of receipts that comply with the invoice. Qualified Invoice Designation Category "1" indicates that an electronic receipt has been designated as the receipt that complies with the invoice. Qualified Invoice Designation Category "2" indicates that a paper receipt has been designated as the receipt that complies with the invoice.

[0048] The qualified invoice designation category is referenced when both electronic and paper receipts are required (i.e., when both the electronic receipt requirement category is "1" and the paper receipt requirement category is "1") and when compliance with the invoice system is required (i.e., when the qualified invoice requirement category is "1"). Therefore, in all other cases, do not set this category (if you do set it, it may be treated as a setting error).

[0049] The correspondence between the values ​​in each category in Figure 4(A) and the output patterns in Figure 3 is as follows. (1) Electronic receipt requirement "0 (not required)", paper receipt requirement "0 (not required)" → Output pattern 1 (2) Electronic receipt requirement "0 (not required)", paper receipt requirement "1 (required)", qualified invoice requirement "0 (not required)" → Output pattern 2 (3) Electronic receipt requirement category "0 (not required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "1 (required)" → Output pattern 3 (4) Electronic receipt requirement category "1 (required)", paper receipt requirement category "0 (not required)", qualified invoice requirement category "0 (not required)" → Output pattern 4 (5) Electronic receipt requirement category "1 (required)", paper receipt requirement category "0 (not required)", qualified invoice requirement category "1 (required)" → Output pattern 5 (6) Electronic receipt requirement category "1 (required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "0 (required)" → Output pattern 6 (7) Electronic receipt requirement category "1 (required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "1 (required)", qualified invoice designation category "1 (electronic receipt designated)" → Output pattern 7 (8) Electronic receipt requirement category "1 (required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "1 (required)", qualified invoice designation category "2 (paper receipt designated)" → Output pattern 8

[0050] (Another example of receipt settings information 1) The receipt settings information may include the output receipt category, the qualification invoice requirement category, and the qualification invoice designation category, as shown in Figure 4(B). In other words, the output receipt category may be included instead of the electronic receipt requirement category and the paper receipt requirement category in the receipt settings information of Figure 4(A).

[0051] The output receipt category is setting information related to receipt output. The output receipt category is setting information that encompasses the settings for whether an electronic receipt is required and whether a paper receipt is required. Output receipt category "0" indicates that neither an electronic receipt nor a paper receipt is required. Output receipt category "1" indicates that an electronic receipt is required, but a paper receipt is not. Output receipt category "2" indicates that an electronic receipt is not required, but a paper receipt is required. Output receipt category "3" indicates that both an electronic receipt and a paper receipt are required.

[0052] Note that the qualified invoice requirement category is referenced in Example 1 when the output receipt category is "1", "2", or "3". Therefore, if the output receipt category is "0", the qualified invoice requirement category is not set (if it is set, it may be treated as a setting error).

[0053] Furthermore, the qualified invoice designation category is referenced in Example 1 when the output receipt category is "3" and the qualified invoice requirement category is "1". Therefore, in all other cases, do not set it (if you set it, it may be treated as a setting error).

[0054] The correspondence between the values ​​in each category in Figure 4(B) and the output patterns in Figure 3 is as follows: (1) Output receipt category "0 (not required)" → Output pattern 1 (2) Output receipt category "2 (paper receipt)", qualified invoice requirement category "0 (not required)" → Output pattern 2 (3) Output receipt category "2 (paper receipt)", qualified invoice requirement category "1 (required)" → Output pattern 3 (4) Output receipt category "1 (electronic receipt)", qualified invoice requirement category "0 (not required)" → Output pattern 4 (5) Output receipt category "1 (electronic receipt)", qualified invoice requirement category "1 (required)" → Output pattern 5 (6) Output receipt category "3 (both)", qualified invoice requirement category "0 (required)" → Output pattern 6 (7) Output receipt category "3 (both)", qualified invoice requirement category "1 (required)", qualified invoice designation category "1 (electronic receipt designated)" → Output pattern 7 (8) Output receipt category "3 (both)", qualified invoice requirement category "1 (required)", qualified invoice specification category "2 (paper receipt specified)" → Output pattern 8

[0055] (Another example of receipt settings information 2) The receipt settings information may include, as shown in Figure 4(C), the electronic receipt requirement, the paper receipt requirement, and the qualified invoice compatibility requirement. In other words, the qualified invoice requirement and qualified invoice designation requirements in the receipt settings information in Figure 4(A) may be replaced with the qualified invoice compatibility requirement.

[0056] The Qualified Invoice Classification is setting information regarding the handling of receipts under the invoice system. The Qualified Invoice Classification is setting information that encompasses the settings for the Qualified Invoice Requirement Classification and the Qualified Invoice Designation Classification. Qualified Invoice Classification "0" indicates that neither electronic nor paper receipts will be supported under the invoice system. Qualified Invoice Classification "1" indicates that electronic receipts will be supported under the invoice system, but paper receipts will not. Qualified Invoice Classification "2" indicates that paper receipts will be supported under the invoice system, but electronic receipts will not.

[0057] The qualified invoice classification is referenced when at least one of either an electronic receipt or a paper receipt is required (i.e., when the electronic receipt requirement is "1" and the paper receipt requirement is "0", or when the electronic receipt requirement is "0" and the paper receipt requirement is "1", or when the electronic receipt requirement is "1" and the paper receipt requirement is "1"). Therefore, if neither an electronic receipt nor a paper receipt is required (i.e., when both the electronic receipt requirement and the paper receipt requirement are "0"), it should not be set (if it is set, it may be treated as a setting error).

[0058] Furthermore, the qualified invoice category "1" can be set when an electronic receipt is required (when the electronic receipt requirement category is "1"). In other words, if an electronic receipt is not required (when the electronic receipt requirement category is "0"), the qualified invoice category "1" should not be set (if it is set, it may be treated as a setting error). Similarly, the qualified invoice category "2" can be set when a paper receipt is required (when the paper receipt requirement category is "1"). In other words, if a paper receipt is not required (when the paper receipt requirement category is "0"), the qualified invoice category "2" should not be set (if it is set, it may be treated as a setting error).

[0059] The correspondence between the values ​​in each category in Figure 4(C) and the output patterns in Figure 3 is as follows: (1) Electronic receipt requirement "0 (not required)", paper receipt requirement "0 (not required)" → Output pattern 1 (2) Electronic receipt requirement category "0 (not required)", paper receipt requirement category "1 (required)", qualified invoice support category "0 (not supported)" → Output pattern 2 (3) Electronic receipt requirement category "0 (not required)", paper receipt requirement category "1 (required)", qualified invoice support category "2 (paper receipt supported)" → Output pattern 3 (4) Electronic receipt requirement category "1 (Required)", paper receipt requirement category "0 (Not required)", qualified invoice support category "0 (Not supported)" → Output pattern 4 (5) Electronic receipt requirement category "1 (Required)", paper receipt requirement category "0 (Not required)", qualified invoice support category "1 (Electronic receipt supported)" → Output pattern 5 (6) Electronic receipt requirement category "1 (Required)", Paper receipt requirement category "1 (Required)", Qualified invoice support category "0 (Not supported)" → Output pattern 6 (7) Electronic receipt requirement category "1 (Required)", Paper receipt requirement category "1 (Required)", Qualified invoice support category "1 (Electronic receipt supported)" → Output pattern 7 (8) Electronic receipt requirement category "1 (Required)", Paper receipt requirement category "1 (Required)", Qualified invoice support category "2 (Paper receipt supported)" → Output pattern 8

[0060] (Another example of receipt settings information 3) The receipt settings information may include the output receipt category and the qualified invoice category, as shown in Figure 4(D). In other words, the output receipt category may be included instead of the electronic receipt requirement category and paper receipt requirement category in the receipt settings information in Figure 4(C).

[0061] Note that the qualified invoice category is referenced in Example 3 when the output receipt category is "1", "2", or "3". Therefore, if the output receipt category is "0", the qualified invoice category should not be set (if it is set, it may be treated as a setting error).

[0062] Furthermore, the qualified invoice support category "1" can be set when an electronic receipt is required (when the output receipt category is "1" or "3"). In other words, if an electronic receipt is not required (when the output receipt category is "0" or "2"), the qualified invoice support category "1" should not be set (if it is set, it may be treated as a setting error). Similarly, the qualified invoice support category "2" can be set when a paper receipt is required (when the output receipt category is "2" or "3"). In other words, if a paper receipt is not required (when the output receipt category is "0" or "1"), the qualified invoice support category "2" should not be set (if it is set, it may be treated as a setting error).

[0063] The correspondence between the values ​​in each category in Figure 4(D) and the output patterns in Figure 3 is as follows. (1) Output receipt category "0 (not required)" → Output pattern 1 (2) Output receipt category "2 (paper receipt)", qualified invoice support category "0 (not supported)" → Output pattern 2 (3) Output receipt category "2 (paper receipt)", qualified invoice support category "2 (paper receipt compatible)" → Output pattern 3 (4) Output receipt category "1 (electronic receipt)", qualified invoice compatibility category "0 (not compatible)" → Output pattern 4 (5) Output receipt category "1 (electronic receipt)", qualified invoice support category "1 (electronic receipt compatible)" → Output pattern 5 (6) Output receipt category "3 (both)", qualified invoice support category "0 (not supported)" → Output pattern 6 (7) Output receipt category "3 (both)", qualified invoice support category "1 (electronic receipt support)" → Output pattern 7 (8) Output receipt category "3 (both)", qualified invoice support category "2 (paper receipt support)" → Output pattern 8

[0064] (Another example of receipt settings information 4) The receipt settings information may include an output pattern category, as shown in Figure 4(E). The output pattern category indicates output pattern X. In other words, you may directly specify (set) the output pattern shown in Figure 3.

[0065] The correspondence between the values ​​of the output pattern categories in Figure 4(E) and the output patterns in Figure 3 is as follows: (1) Output pattern category "1" → Output pattern 1 (2) Output pattern category "2" → Output pattern 2 (3) Output pattern category "3" → Output pattern 3 (4) Output pattern category "4" → Output pattern 4 (5) Output pattern category "5" → Output pattern 5 (6) Output pattern category "6" → Output pattern 6 (7) Output pattern category "7" → Output pattern 7 (8) Output pattern category "8" → Output pattern 8

[0066] (Example of operation) Figures 5 and 6 are flowcharts illustrating an example of the operation of the registration and settlement device 10. The flowchart in Figure 5(A) shows the operation from the start of a customer's transaction. The flowchart in Figure 5(B) shows the details of the member card interruption processing (steps S1, S6, S8) in Figure 5(A). The flowchart in Figure 6 shows the operation that follows the flowchart in Figure 5(A) (the operation following step S10). Note that Figures 5 and 6 describe general operations, and other operations (for example, increasing or decreasing the number of items purchased, canceling registration, reading gift certificates / coupons, reissuing receipts, returns, etc.) are omitted.

[0067] (Flowchart in Figure 5(A)) Step S1: The registration and settlement device 10 executes the member card interruption process. The member card interruption process will be described later. Next, proceed to step S2. Step S2: The registration and settlement device 10 determines whether a product scan or other action (barcode scanning, operation of product preset buttons) has occurred. If a product scan or other action has occurred (Step S2: YES), proceed to Step S3. If no product scan or other action has occurred (Step S2: NO), return to Step S2.

[0068] Step S3: The registration and settlement device 10 registers the products that it determined had been scanned or otherwise processed in step S2. Then proceed to step S4. Step S4: The registration and settlement device 10 determines whether a product has been scanned or otherwise processed. If a product has been scanned or otherwise processed (Step S4: YES), proceed to Step S5. If no product has been scanned or otherwise processed (Step S4: NO), proceed to Step S6. Step S5: The registration and settlement device 10 registers the products that it determined had been scanned or otherwise processed in Step S4. The process then proceeds to Step S6. Step S6: The registration and settlement device 10 executes the member card interruption process. The member card interruption process will be described later. Next, proceed to step S7. Step S7: The registration and settlement device 10 determines whether a registration completion operation has occurred (for example, operation of the subtotal button, operation of the registration completion button, etc.). If a registration completion operation has occurred (Step S7: YES), proceed to Step S8. If no registration completion operation has occurred (Step S7: NO), return to Step S4.

[0069] Step S8: The registration and settlement device 10 executes the member card interruption process. The member card interruption process will be described later. Next, proceed to step S9. Step S9: The registration and settlement device 10 determines whether it has accepted the selection of a settlement method (payment method). If it has accepted the settlement method (Step S9: YES), proceed to Step S10. If it has not accepted the settlement method (Step S9: NO), return to Step S8. Step S10: The registration and settlement device 10 settles the payment according to the payment method accepted in step S9. The process then proceeds to step S30 in Figure 6.

[0070] (Supplement to Steps S9 and S10) For example, if the registered settlement device 10 accepts the selection of cash payment (step S9: YES), the cash settlement unit executes the cash settlement (e.g., accepts the deposit, accepts the operation of the cash total key after accepting the deposit exceeding the payment amount, and dispenses change if there is change). Also, for example, if the registered settlement device 10 accepts the selection of electronic money (transportation IC card) payment (step S9: YES), the non-cash settlement unit executes the electronic money settlement (e.g., transmits the information necessary for electronic money settlement to the electronic money server (not shown) and receives information from the electronic money server indicating that the settlement has been successfully completed (e.g., settlement completion notification)). Also, for example, if the registered settlement device 10 accepts the selection of credit payment (step S9: YES), the non-cash settlement unit executes the credit payment (e.g., transmits the information necessary for credit payment to the credit server (not shown) and receives information from the credit server indicating that the settlement has been successfully completed (e.g., settlement completion notification)). The same applies to point settlement, where the user pays by consuming (using) their points.

[0071] (Flowchart in Figure 5(B) / Member card interrupt processing) Step S20: The registration and settlement device 10 determines whether the read flag is set. The read flag indicates whether the customer identification information of the customer has been read in the transaction. A value of "0 (clear)" for the read flag indicates that the customer identification information has not been read. A value of "1 (set)" for the read flag indicates that the customer identification information has been read. The initial value of the read flag (value at the start of the transaction) is "0". If the read flag is set (Step S20: YES), the flowchart (member card interruption process) ends and returns to the flowchart in Figure 5(A) (i.e., if it was the member card interruption process in Step S1, proceed to Step S2. If it was the member card interruption process in Step S6, proceed to Step S7. If it was the member card interruption process in Step S8, proceed to Step S9). If the read flag is not set (Step S20: NO), proceed to Step S21.

[0072] Step S21: The registration and settlement device 10 determines whether the customer's membership card has been read (for example, whether the barcode on the membership card has been read by the scanner unit). If the membership card has been read (Step S21: YES), the process proceeds to Step S22. If the membership card has not been read (Step S22: NO), the flowchart (membership card interrupt processing) ends, and the process returns to the flowchart in Figure 5(A).

[0073] Step S22: The registration and settlement device 10 stores the customer identification information (customer identification information of the customer) of the membership card that it determined to have been read in step S21. The process then proceeds to step S23. Step S23: The registration and settlement device 10 requests (queries) the customer information of the customer from the customer management server 20. For example, the registration and settlement device 10 sends customer information request information, which includes the customer identification information stored (acquired) in step S22, to the customer management server 20. The process then proceeds to step S24. When the customer management server 20 receives customer information request information from the registration and settlement device 10, it sends (responds) customer information corresponding to the customer identification information contained in the customer information request information. Step S24: The registration and settlement device 10 obtains (receives) the customer information of the customer from the customer management server 20 and stores it. As shown in Figure 2(A), the customer information includes customer identification information, but the customer identification information in the customer information obtained in step S24 is the same as the customer identification information stored in step S22 (i.e., the same customer identification information is stored redundantly). Therefore, the registration and settlement device 10 may store the customer information stored in step S24 in place of the customer identification information stored in step S22 (by deleting the customer identification information stored in step S22). Also, as shown in Figure 2(A), the customer information includes receipt setting information. Step S25: The registration and settlement device 10 sets the read flag. Then the flowchart (member card interrupt processing) ends and returns to the flowchart in Figure 5(A).

[0074] (Flowchart in Figure 6) Step S30: The registration and settlement device 10 determines whether the read flag is set. If the read flag is set (Step S30: YES), proceed to step S31. If the read flag is not set (Step S30: NO), proceed to step S33.

[0075] Step S31: The registration and settlement device 10 identifies the output pattern based on the receipt setting information. That is, the registration and settlement device 10 identifies which of output patterns 1 to 8 (see Figure 3) the output pattern of the customer's receipt is based on the receipt setting information contained in the customer information of the customer that was stored in step S24 of Figure 5(B). The process then proceeds to step S32.

[0076] (Supplement to Step S31) For example, if the structure (contents, items) of the receipt settings information included in the customer information of the customer is as shown in Figure 4(A), the registration and settlement device 10 will identify which of the output patterns from output pattern 1 to output pattern 8 the customer's receipt output pattern will be, based on the values ​​of each category (electronic receipt requirement category, paper receipt requirement category, qualified invoice requirement category, qualified invoice designation category), as explained in Figure 4(A). Similarly, if the structure of the receipt settings information included in the customer information of the customer is as shown in Figure 4(B), the registration and settlement device 10 will identify which of the output patterns from output pattern 1 to output pattern 8 the customer's receipt output pattern will be, based on the values ​​of each category (output receipt category, qualified invoice requirement category, qualified invoice designation category), as explained in Figure 4(B). The same applies if the structure of the receipt settings information included in the customer information of the customer is as shown in Figures 4(C) to 4(E).

[0077] Step S32: The registration and settlement device 10 clears the read flag. Then proceed to step S34.

[0078] Step S33: The registration and settlement device 10 identifies the output pattern of the customer's receipt as output pattern 2 (identifies it as output pattern 2). In other words, the registration and settlement device 10 identifies output pattern 2 if it has not read the membership card. The process then proceeds to step S34.

[0079] Step S34: The registration and settlement device 10 generates receipt information according to the output pattern. The process then proceeds to step S35.

[0080] (Supplement to Step S34) If the registration and settlement device 10 identifies output pattern 2 in step S31 or step S33, it generates information for paper receipts that do not support invoices (it does not generate information for electronic receipts). If the registration and settlement device 10 identifies output pattern 3 in step S31, it generates information for paper receipts that support invoices (it does not generate information for electronic receipts). If the registration and settlement device 10 identifies output pattern 4 in step S31, it generates information for electronic receipts that do not support invoices (it does not generate information for paper receipts). If the registration and settlement device 10 identifies output pattern 5 in step S31, it generates information for electronic receipts that support invoices (it does not generate information for paper receipts). If the registration and settlement device 10 identifies output pattern 6 in step S31, it generates information for electronic receipts that do not support invoices and information for paper receipts that do not support invoices. If the registration and settlement device 10 identifies output pattern 7 in step S31, it generates information for electronic receipts compatible with invoices and information for paper receipts not compatible with invoices. If the registration and settlement device 10 identifies output pattern 8 in step S31, it generates information for electronic receipts not compatible with invoices and information for paper receipts compatible with invoices. If the registration and settlement device 10 identifies output pattern 1 in step S31, it does not generate information for either electronic or paper receipts.

[0081] Furthermore, if the registration and settlement device 10 identifies output patterns 4 to 8 in step S31 (when generating information for an electronic receipt) and the payment is non-cash (for example, when electronic money payment or credit card payment is made in step S10 of Figure 5(A)), it may also generate electronic media information related to the non-cash payment (slip data for an electronic slip) in addition to the information described above (information that is generated according to each of the output patterns 4 to 8).

[0082] Furthermore, if the registration and settlement device 10 specifies output patterns 2, 3, 6-8 in step S31 or step S33 (when generating information for paper receipts), and in the case of non-cash settlement, it may generate, in addition to the information described above (the information described as being generated according to each of the output patterns 2, 3, 6-8), information for paper media related to the non-cash settlement (slip data for paper slips).

[0083] Furthermore, when output patterns 6 to 8 are specified (when generating information for both paper receipts and electronic receipts), both electronic media information and paper media information related to the non-cash payment may be generated, or either electronic media information or paper media information may be generated.

[0084] Step S35: The registration and settlement device 10 determines whether to print an electronic receipt (whether the output pattern is one that prints an electronic receipt). The registration and settlement device 10 determines whether to print an electronic receipt if the output pattern is 4 to 8, and whether to not print an electronic receipt if the output pattern is 1 to 3. If an electronic receipt is to be printed (Step S35: YES), proceed to step S36. If an electronic receipt is not to be printed (Step S35: NO), proceed to step S37. Step S36: The registration and settlement device 10 transmits the transaction identification information for the transaction, the customer identification information stored in step S22 of Figure 6(A), and the electronic receipt information generated in step S34 to the electronic receipt management server 40. The process then proceeds to step S37.

[0085] (Supplement to Step S36) If the registration and settlement device 10 identifies output pattern 4 in step S31, it sends the electronic receipt information generated in step S34 as electronic receipt information, which is not compatible with invoices, to the electronic receipt management server 40. If the registration and settlement device 10 identifies output pattern 5 in step S31, it sends the electronic receipt information generated in step S34 as electronic receipt information, which is compatible with invoices, to the electronic receipt management server 40. If the registration and settlement device 10 identifies output pattern 6 in step S31, it sends the electronic receipt information generated in step S34 as electronic receipt information, which is not compatible with invoices, to the electronic receipt management server 40. If the registration and settlement device 10 identifies output pattern 7 in step S31, it sends the electronic receipt information generated in step S34 as electronic receipt information, which is compatible with invoices, to the electronic receipt management server 40. If the registration and settlement device 10 identifies output pattern 8 in step S31, it sends the electronic receipt information that does not support invoices, which was generated in step S34, to the electronic receipt management server 40 as electronic receipt information.

[0086] Furthermore, if the registration and settlement device 10 generates electronic media information (slip data for electronic slips) related to non-cash payments in step S34, it transmits the electronic media information related to non-cash payments to the electronic receipt management server 40.

[0087] Step S37: The registration and settlement device 10 determines whether to print a paper receipt (whether the output pattern is one that prints a paper receipt). The registration and settlement device 10 determines whether to print a paper receipt if the output pattern is 2, 3, or 6-8, and whether to not print a paper receipt if the output pattern is 1, 4, or 5. If a paper receipt is to be printed (Step S37: YES), proceed to Step S38. If a paper receipt is not to be printed (Step S37: NO), proceed to Step S39. Step S38: The registration and settlement device 10 prints and issues a paper receipt based on the paper receipt information generated in step S34. The process then proceeds to step S39.

[0088] (Supplement to Step S38) If the registration and settlement device 10 identifies output pattern 2 in step S31, it prints and issues a paper receipt based on the invoice-incompatible paper receipt information generated in step S34. If the registration and settlement device 10 identifies output pattern 3 in step S31, it prints and issues a paper receipt based on the invoice-compatible paper receipt information generated in step S34. If the registration and settlement device 10 identifies output pattern 6 in step S31, it prints and issues a paper receipt based on the invoice-incompatible paper receipt information generated in step S34. If the registration and settlement device 10 identifies output pattern 7 in step S31, it prints and issues a paper receipt based on the invoice-incompatible paper receipt information generated in step S34. If the registration and settlement device 10 identifies output pattern 8 in step S31, it prints and issues a paper receipt based on the invoice-compatible paper receipt information generated in step S34.

[0089] Furthermore, if the registration and settlement device 10 generates paper media information (slip data for paper slips) related to non-cash settlements in step S34, it prints and issues the paper media based on said paper media information.

[0090] Step S39: The registration and settlement device 10 generates transaction information, etc. Then proceed to step S40. Step S40: The registration and settlement device 10 transmits transaction information, etc. Then proceed to step S41.

[0091] (Supplement to steps S39 and S40) For example, the registration and settlement device 10 generates transaction information for the transaction (step S39) and transmits it to the transaction management server 30 (step S40). Also, for example, the registration and settlement device 10 generates electronic journal information for the transaction (step S39) and transmits it to the electronic journal management server (not shown) (step S40).

[0092] Step S41: If the registration and settlement device 10 has stored customer information in step S24 of Figure 5(B), it erases the customer information. If the registration and settlement device 10 has stored customer identification information in step S22 of Figure 5(B) and has not erased it in step S24, it also erases the customer identification information. This flowchart then ends.

[0093] In the flowcharts shown in Figures 5 and 6, the output pattern (see Figure 3) is identified after the payment is completed (step S10 in Figure 5(A)) rather than when the membership card is read (step S31 in Figure 6). However, the output pattern may also be identified when the membership card is read. For example, the registration and settlement device 10 may identify the output pattern in the membership card interrupt processing shown in Figure 5(B).

[0094] Furthermore, while the flowcharts in Figures 5 and 6 show the payment method being selected after product registration, the payment method may also be selected before product registration. In other words, after selecting the payment method, the scanning of the first product for registration may be accepted, and if the registration is completed, payment may be processed according to the selected payment method. Although omitted in the flowcharts, the customer may be asked about the need for a shopping bag (whether or not) before the payment process begins.

[0095] Furthermore, while the flowcharts shown in Figures 5 and 6 prevent the membership card from being read multiple times (by preventing a second reading), it is also possible to allow reading multiple times. In other words, control based on the read flag may be omitted.

[0096] (Screen example) Figure 7 shows an example of the screen of the registration and settlement device 10. Figure 7(A) is an example of the subtotal screen. Figure 7(B) is an example of the payment method selection screen. For example, in a transaction (a transaction in which XX Wagyu beef is registered as item 1, XX milk as item 2, XX fruit wine as item 3, and a coupon that can be used as a subtotal discount of 1000 yen is registered), when the subtotal button is pressed (the operation in step S7 of Figure 5(A)), the registration and settlement device 10 displays the subtotal screen shown in Figure 7(A) on the staff-side display and the payment method selection screen shown in Figure 7(B) on the customer-side display. In this transaction, the membership card is read.

[0097] In the upper area AR10 of the subplan screen shown in Figure 7(A), the customer name (shown as "AAA" in the figure) is displayed. The customer name "AAA" is customer information (more specifically, the customer name within the basic information that makes up the customer information) obtained based on the membership card (customer identification information). In the upper area AR20 of the payment method selection screen shown in Figure 7(B), "Membership card read" is displayed.

[0098] In the payment method selection screen shown in Figure 7(B), the Cash button is used when paying with cash. The Transportation IC button is used when paying with electronic money using a transportation IC card. The Credit button is used when paying with a credit card. The Points button is used when paying with points. In this transaction, the Points button is displayed because the membership card has been read (meaning point payment is possible), but the Points button will not be displayed if the membership card has not been read.

[0099] Note that the screens shown in Figures 7(A) and 7(B) assume that the registration payment device 10 is a face-to-face semi-self-service device or a mode change device (face-to-face semi-self-service mode), but the same applies to cases where the registration payment device 10 is an employee-operated device, a fully self-service device, or a mode change device (fully self-service mode). If the registration payment device 10 is an employee-operated device, the payment method selection screen may be displayed on the employee-side display. If the registration payment device 10 is a fully self-service device or a mode change device (fully self-service mode), the payment method selection screen may be displayed on the customer-side display following the sub-plan screen.

[0100] (Example receipt) Figure 8 shows examples of paper and electronic receipts. Figure 8(A) is an example of an invoice-compatible paper receipt. Figure 8(B) is an example of an invoice-compatible electronic receipt (specifically, an example of display on a customer terminal (smartphone) 50).

[0101] For example, if the payment method selection screen shown in Figure 7(B) is set up and the transportation IC button is selected, and the electronic money payment (payment in step S10 of Figure 5(A)) is completed, the registered payment device 10 will print and issue an invoice-compliant paper receipt as shown in Figure 8(A) (i.e., if the output pattern is output pattern 3 or output pattern 8). The invoice-compliant paper receipt shown in Figure 8(A) has "T1234567890123" printed on it as the registration number for the invoice system.

[0102] For example, if the payment method selection screen shown in Figure 7(B) is set up and the transportation IC button is selected, and after the electronic money payment is completed, the registered payment device 10 outputs an invoice-compatible electronic receipt (i.e., if the output pattern is output pattern 5 or output pattern 7), it sends electronic receipt information to the electronic receipt management server 40 so that an invoice-compatible electronic receipt like the one shown in Figure 8(B) is displayed on the customer terminal 50. The invoice-compatible electronic receipt shown in Figure 8(B) displays "T1234567890123" as the registration number for the invoice system.

[0103] The barcode at the bottom of the paper receipt shown in Figure 8(A) and the electronic receipt shown in Figure 8(B) is used to identify the transaction (transaction details), for example, for returns (described later). This barcode encodes, for example, transaction identification information. In addition to transaction identification information, this barcode may encode one or more of the following: transaction date (time) or device identification information.

[0104] Note that there are differences in the printed / displayed items between the paper receipt shown in Figure 8(A) and the electronic receipt shown in Figure 8(B). However, when both paper and electronic receipts are output (in output patterns 6-8), the printed / displayed items may be the same. Both the paper and electronic receipts only need to be at least valid as a simplified invoice.

[0105] (Notification of information regarding the receipt output at the time of reading the membership card) Although it has been explained that the registration and payment device 10 may specify an output pattern at the time it reads the member card (for example, in the member card interrupt processing shown in Figure 5(B)), if the output pattern is specified at the time the member card is read, the content indicated by the specified output pattern may be notified to the operator (either the store clerk, the customer, or both).

[0106] Figure 9 shows an example screen of the registration and settlement device 10. The registration and settlement device 10 may display a subplan screen as shown in Figure 9(A) on the staff-side display unit instead of the subplan screen shown in Figure 7(A), and a payment method selection screen as shown in Figure 9(B) on the customer-side display unit instead of the payment method selection screen shown in Figure 7(B). The subplan screen shown in Figure 7(A) and the subplan screen shown in Figure 9(A) differ in the display content of the upper area AR10. The payment method selection screen shown in Figure 7(B) and the payment method selection screen shown in Figure 9(B) differ in the presence or absence of display by the lower area AR30.

[0107] In the upper area AR10 of the subplan screen shown in Figure 9(A), the customer name "AAA" is displayed, along with information regarding the output of an electronic receipt (shown as "〇〇" in the figure) and information regarding the output of a paper receipt (shown as "××" in the figure). In the lower area AR30 of the payment method selection screen shown in Figure 9(B), information regarding the output of an electronic receipt (shown as "〇〇" in the figure) and information regarding the output of a paper receipt (shown as "××" in the figure) are displayed.

[0108] The information regarding the output of electronic receipts, "〇〇," and the information regarding the output of paper receipts, "××," in the upper area AR10 and lower area AR30 correspond to the output pattern identified from customer information (more specifically, receipt setting information that constitutes the customer information) obtained based on the membership card (customer identification information). For example, if the registration and settlement device 10 identifies output pattern 1, it will display "Electronic receipt output: None Paper receipt output: None" in the upper area AR10 and lower area AR30. Also, for example, if the registration and settlement device 10 identifies output pattern 2, it will display "Electronic receipt output: None Paper receipt output: Yes (non-invoice)" in the upper area AR10 and lower area AR30. Also, for example, if the registration and settlement device 10 identifies output pattern 7, it will display "Electronic receipt output: Yes (invoice) Paper receipt output: Yes (non-invoice)" in the upper area AR10 and lower area AR30.

[0109] Note that the subtotal screen shown in Figure 9(A) and the payment method selection screen shown in Figure 9(B) are screens displayed after the subtotal button has been pressed. However, if the registration and settlement device 10 has identified an output pattern, it may also display information regarding the output of an electronic receipt or a paper receipt before the subtotal button has been pressed. For example, the registration and settlement device 10 may display information such as that shown in the upper area AR10 and the lower area AR30 on the registration screen (a screen displayed on the staff's display before the subtotal button has been pressed) or the registration confirmation screen (a screen displayed on the customer's display before the subtotal button has been pressed).

[0110] (Check receipt output) When the registration and settlement device 10 identifies an output pattern using a membership card, it may confirm receipt output with a store employee or customer. Specifically, the registration and settlement device 10 identifies an output pattern in step S31 or step S33 and generates receipt information according to the identified output pattern (step S34 in Figure 6). However, if the process proceeds to step S34 via step S31, it may confirm receipt output with a store employee or customer before generating the receipt information (between step S32 and step S34).

[0111] Figure 10 shows an example of the screen of the registration and settlement device 10. For example, when output pattern 2 is selected, the registration and settlement device 10 displays a small screen SG1 as shown in Figure 10(A) as a pop-up on the customer-side display and the staff-side display. When output pattern 7 is selected, the small screen SG1 as shown in Figure 10(B) is displayed as a pop-up on the customer-side display and the staff-side display.

[0112] Furthermore, if the registration and payment device 10 is a face-to-face semi-self-service device, the small screen SG1 may be displayed on the staff-side display unit first, and then the small screen SG1 may also be displayed on the customer-side display unit in response to staff operations (operations on the staff-side display unit; these may be operations on the small screen SG1 or other operations). Alternatively, the small screen SG1 may not be displayed on the staff-side display unit, but may be displayed on the customer-side display unit in response to staff operations (operations on the staff-side display unit). If there is a change in the receipt output (a change resulting from operations after the operation of the change button BT41 described later), the staff-side display unit and the customer-side display unit may be notified of the change (or the content of the change).

[0113] If the "no change" button BT40 on the small screen SG1 is pressed, the registration and settlement device 10 will erase the small screen SG1 (if the small screen SG1 is displayed on both the customer-side display and the employee-side display, both small screens SG1 will be erased), and generate receipt information according to the output pattern confirmed by the operation of the "no change" button BT40 (i.e., the identified output pattern) (step S34 in Figure 6).

[0114] When the button BT41 for changing the small screen SG1 is pressed, the registration and settlement device 10 clears the small screen SG1 (clears both small screens if they are displayed on both the customer-side display and the staff-side display), and displays a pop-up small screen SG2 (not shown) on the customer-side display or the staff-side display to accept an operation to change the content of the receipt output. When the registration and settlement device 10 accepts an operation to change the content of the receipt output on the small screen SG2, it clears the small screen SG2 (clears both small screens SG2 if they are displayed on both the customer-side display and the staff-side display), and generates receipt information according to the change (i.e., the output pattern corresponding to the changed content) (step S34 in Figure 6).

[0115] Changes received on the small screen SG2 may or may not be reflected in the customer's future transactions (they may be applied only to the transaction in question). If the changes are to be reflected in the customer's future transactions, the registration settlement device 10 sends information indicating the changes received on the small screen SG2, along with the customer identification information, to the customer management server 20 (the customer management server 20 updates the customer information based on the information indicating the changes).

[0116] Furthermore, you may confirm whether or not to reflect this change in future transactions for the customer, for example, on a small screen SG2. For example, you may display a "Reflect" button to operate if you want to reflect the change, and a "Do not reflect" button to operate if you do not want to reflect the change, on the small screen SG2.

[0117] (Returns, corrections) The registration and settlement device 10 is capable of performing return processing. If the registration and settlement device 10 performs return processing for goods sold in a transaction (transaction A) for which a receipt has already been printed, it may process the receipt printing as follows.

[0118] If some of the items on the receipt for transaction A are returned, a return receipt for the returned items and a correction receipt for the items not returned can be printed. If all of the items on the receipt for transaction A are returned, a return receipt can be printed (i.e., if all items are returned, a correction receipt will not be issued). The following explanation assumes that some of the items in transaction A have been returned.

[0119] If, in transaction A, an invoice-incompatible paper receipt was issued instead of generating an electronic receipt (output pattern 2), an invoice-incompatible paper correction receipt and a paper return receipt will be issued. The paper receipt for transaction A (invoice-incompatible paper receipt) will be collected from the customer.

[0120] If, in transaction A, an invoice-compliant paper receipt was issued instead of generating an electronic receipt (output pattern 3), an invoice-compliant paper correction receipt and a paper return receipt will be issued. The paper receipt for transaction A (invoice-compliant paper receipt) will be collected from the customer.

[0121] If, in transaction A, a non-invoice-compatible electronic receipt was generated without issuing a paper receipt (output pattern 4), the electronic receipt for transaction A (non-invoice-compatible electronic receipt) will be made unavailable for viewing. Alternatively, in addition to making the electronic receipt for transaction A unavailable for viewing, a non-invoice-compatible paper correction receipt and a paper return receipt may also be issued.

[0122] Alternatively, the electronic receipt for transaction A may be made unavailable for viewing using the following method: The registered settlement device 10 sends information (viewing prohibition notice) to the electronic receipt management server 40 to prohibit viewing of the electronic receipt for transaction A. The electronic receipt management server 40 prohibits viewing of the electronic receipt for transaction A based on the viewing prohibition notice.

[0123] Instead of making the electronic receipt for transaction A unavailable for viewing, you may update the electronic receipt for transaction A to reflect the details after the return.

[0124] Alternatively, the electronic receipt for transaction A may be updated with the details after the return using the following method: The registration settlement device 10 sends the information for the correction receipt that does not support invoices and the information for the return receipt to the electronic receipt management server 40. The electronic receipt management server 40 stores the information for the correction receipt that does not support invoices and the information for the return receipt in place of the electronic receipt information for transaction A. The same applies to output patterns 6 and 8.

[0125] If an invoice-compliant electronic receipt was generated for transaction A without issuing a paper receipt (output pattern 5), the electronic receipt for transaction A (invoice-compliant electronic receipt) will be made unavailable for viewing. In addition to making it unavailable for viewing, a paper correction receipt and a paper return receipt that are compatible with the invoice may also be issued. In other words, even if an invoice-compliant electronic receipt was generated for the original transaction (transaction A), an invoice-compliant electronic receipt will not be generated during the correction process.

[0126] Instead of making the electronic receipt for transaction A unavailable for viewing, you may update the electronic receipt for transaction A to reflect the details after the return.

[0127] Alternatively, the electronic receipt for transaction A may be updated with the details after the return using the following method: The registration settlement device 10 transmits the information for the corrected receipt or the return receipt, which corresponds to the invoice, to the electronic receipt management server 40. The electronic receipt management server 40 stores the information for the corrected receipt or the return receipt, which corresponds to the invoice, in place of the electronic receipt information for transaction A. The same applies to output pattern 7.

[0128] Alternatively, the electronic receipt for transaction A may be updated with the information after the return by the following method: The registration settlement device 10 sends the information for the correction receipt or the return receipt that does not support invoices to the electronic receipt management server 40. The electronic receipt management server 40 stores the information for the correction receipt or the return receipt that does not support invoices in place of the electronic receipt information for transaction A. In other words, after the correction, the electronic receipt may be updated to one that does not support invoices. The same applies to output pattern 7.

[0129] Instead of prohibiting access to the electronic receipt for transaction A (an invoice-compatible electronic receipt), it is acceptable to change the electronic receipt for transaction A to an invoice-incompatible electronic receipt.

[0130] Alternatively, the electronic receipt for transaction A (an invoice-compatible electronic receipt) may be changed to an invoice-incompatible electronic receipt using the following method: The registered settlement device 10 sends information (a change instruction notification) to the electronic receipt management server 40 to change the electronic receipt for transaction A to an invoice-incompatible electronic receipt. The electronic receipt management server 40 changes the electronic receipt for transaction A to an invoice-incompatible electronic receipt based on the change instruction notification.

[0131] If a non-invoice-compatible electronic receipt is generated and a non-invoice-compatible paper receipt is issued for transaction A (in the case of output pattern 6), the electronic receipt for transaction A (non-invoice-compatible electronic receipt) will be made unavailable for viewing, and a non-invoice-compatible paper correction receipt and a paper return receipt will be issued. The paper receipt for transaction A (non-invoice-compatible paper receipt) will be collected from the customer.

[0132] Instead of making the electronic receipt for transaction A unavailable for viewing, you may update the electronic receipt for transaction A to reflect the details after the return.

[0133] If an invoice-compliant electronic receipt was generated for transaction A, but a non-invoice-compliant paper receipt was issued (output pattern 7), the electronic receipt for transaction A (invoice-compliant electronic receipt) will be made unavailable for viewing, and a non-invoice-compliant paper correction receipt and a paper return receipt will be issued. In other words, even if an invoice-compliant electronic receipt was generated for the original transaction (transaction A), an invoice-compliant electronic receipt will not be generated during the correction process. The paper receipt for transaction A (non-invoice-compliant paper receipt) will be collected from the customer.

[0134] Instead of making the electronic receipt for transaction A unavailable for viewing, you may update the electronic receipt for transaction A to reflect the details after the return.

[0135] Instead of prohibiting viewing of the electronic receipt for transaction A (an invoice-compatible electronic receipt) and issuing a non-invoice-compatible paper correction receipt and a paper return receipt, the electronic receipt for transaction A may be changed to a non-invoice-compatible electronic receipt, and a paper correction receipt (or a non-invoice-compatible paper correction receipt) and a paper return receipt may be issued.

[0136] If, in transaction A, an electronic receipt that does not support invoices is generated and an invoice-compliant paper receipt is issued (in the case of output pattern 8), the electronic receipt for transaction A (the electronic receipt that does not support invoices) will be made unavailable for viewing, and an invoice-compliant paper correction receipt and a paper return receipt will be issued. The paper receipt for transaction A (the paper receipt that does not support invoices) will be collected from the customer.

[0137] Instead of making the electronic receipt for transaction A unavailable for viewing, you may update the electronic receipt for transaction A to reflect the details after the return.

[0138] (Reissuance of paper receipt) The registration and settlement device 10 may process the reissuance (issuance) of a receipt for a transaction (transaction B) for which a receipt has already been printed as follows:

[0139] If, in transaction B, an invoice-incompatible paper receipt was issued instead of generating an electronic receipt (output pattern 2), the invoice-incompatible paper receipt will be reissued.

[0140] If an invoice-compliant paper receipt was issued for transaction B without generating an electronic receipt (output pattern 3), a non-invoice-compliant paper receipt will be reissued. In other words, when reissuing a paper receipt for a transaction in which an invoice-compliant paper receipt was issued, a non-invoice-compliant paper receipt will be reissued (reissuance of invoice-compliant paper receipts is prohibited). Alternatively, instead of prohibiting the reissuance of invoice-compliant paper receipts, an invoice-compliant paper receipt may be reissued in a manner that makes it clear that it is a reissue (e.g., by using a watermark). The reissuance of invoice-compliant paper receipts may be conditional on the presence (intervention) of a store employee (e.g., a manager). For example, if a store employee who is a manager logs in, an invoice-compliant paper receipt may be reissued.

[0141] If, in transaction B, a non-invoice-compatible electronic receipt was generated instead of issuing a paper receipt (output pattern 4), then, since no paper receipt was issued for transaction B and an electronic receipt exists, the issuance of a paper receipt is prohibited. Alternatively, the non-invoice-compatible electronic receipt may be made unavailable for viewing, and a paper receipt issued. The issuance of a paper receipt may be conditional on the presence (intervention) of a store employee.

[0142] If an invoice-compliant electronic receipt was generated in transaction B without issuing a paper receipt (output pattern 5), then since no paper receipt was issued in transaction B and an electronic receipt exists, the issuance of a paper receipt is prohibited. Alternatively, the issuance of a non-invoice-compliant paper receipt may be permitted (the issuance of an invoice-compliant paper receipt is prohibited). Alternatively, the viewing of the invoice-compliant electronic receipt may be prohibited, and a paper receipt (either a non-invoice-compliant paper receipt or an invoice-compliant paper receipt) may be issued. In other words, even if an invoice-compliant electronic receipt was generated in the original transaction (transaction B), an invoice-compliant electronic receipt will not be generated in the reissue process. The issuance of a paper receipt may be conditional on the presence of a store employee.

[0143] If, in transaction B, an electronic receipt that does not support invoices is generated and a paper receipt that does not support invoices is issued (in the case of output pattern 6), the reissuance of the paper receipt is prohibited because an electronic receipt exists. Alternatively, the electronic receipt that does not support invoices may be made unavailable for viewing, and a paper receipt may be reissued. The reissuance of the paper receipt may be conditional on the presence of a store employee (e.g., a manager).

[0144] If an invoice-compliant electronic receipt was generated and a non-invoice-compliant paper receipt was issued in transaction B (output pattern 7), the reissuance of the paper receipt is prohibited because an electronic receipt exists. Alternatively, the reissuance of a non-invoice-compliant paper receipt may be permitted. Alternatively, the viewing of the invoice-compliant electronic receipt may be prohibited, and a paper receipt (either a non-invoice-compliant paper receipt or an invoice-compliant paper receipt) may be reissued. In other words, even if an invoice-compliant electronic receipt was generated in the original transaction (transaction B), an invoice-compliant electronic receipt will not be generated during the reissuance process. The reissuance of paper receipts may be conditional on the presence of a store employee (e.g., a manager).

[0145] If, in transaction B, an electronic receipt that does not support invoices was generated and an invoice-compliant paper receipt was issued (in the case of output pattern 8), the reissuance of the paper receipt is prohibited because an electronic receipt exists. Alternatively, the reissuance of the non-invoice-compliant paper receipt may be permitted (reissuance of the invoice-compliant paper receipt is not permitted). Alternatively, the viewing of the non-invoice-compliant electronic receipt may be prohibited, and a paper receipt (either a non-invoice-compliant paper receipt or an invoice-compliant paper receipt) may be reissued. The reissuance of paper receipts may be conditional on the presence of a store employee (e.g., a manager).

[0146] (Electronic receipt member) In addition to the customer management server 20, a configuration including an electronic receipt member server 21 (not shown) may also be provided. The electronic receipt member server 21 manages electronic receipt members. For example, the electronic receipt member server 21 stores an electronic receipt member file. The electronic receipt member file is a file that stores electronic receipt member information. As shown in Figure 2(C), the electronic receipt member information in the electronic receipt member file includes, as data items, electronic receipt member identification information, receipt setting information, and customer identification information for each of the one or more stores (customer management server 20) (in the figure, customer identification information for store A, customer identification information for store B, etc.). The electronic receipt member identification information is identification information that identifies electronic receipt members. The receipt setting information of the electronic receipt member information (Figure 2(C)) includes information similar to the receipt setting information of the customer information (Figure 2(A)), as shown in Figures 4(A) to 4(E). Furthermore, each store (Store A, Store B, ...) may be operated by a different company, or it may be operated by the same company but have different store names.

[0147] In a configuration that includes an electronic receipt member server 21, each customer management server 20 does not include receipt setting information, as shown in Figure 2(D). In other words, in a configuration that includes an electronic receipt member server 21, the electronic receipt member server 21 manages the receipt setting information (Figure 2(C)), so individual customer management servers 20 do not manage receipt setting information. Note that Figure 2(D) shows the customer management server 20 of store A, but the same applies to the customer management servers 20 of other stores.

[0148] In a configuration that includes an electronic receipt member server 21, there are, for example, two ways for a store terminal 20 at store A (and other stores) to acquire customer information for a particular customer (customer K):

[0149] (1) If store terminal 20 of store A obtains customer identification information of customer K of store A from store A's membership card, it uses the customer identification information of customer K of store A to obtain customer information (excluding receipt setting information) of customer K from store A's customer management server 20, and similarly uses the customer identification information of customer K of store A to obtain customer K's receipt setting information from electronic receipt membership server 21. (2) When store terminal 20 of store A obtains customer K's electronic receipt member identification information from, for example, a membership card for electronic receipt members, it uses customer K's electronic receipt member identification information to obtain customer K's receipt setting information and store A's customer identification information for customer K from the electronic receipt member server 21, and uses store A's customer identification information for customer K obtained from the electronic receipt member server 21 to obtain customer K's customer information (other than receipt setting information) from store A's customer management server 20.

[0150] In the case of electronic receipt members, the electronic receipt file (Figure 2(B)) stored by the electronic receipt management server 40 stores electronic receipts from multiple stores (for example, an electronic receipt from store A and an electronic receipt from store B).

[0151] (Customer access to electronic receipts, etc.) Each customer can access the electronic receipt file on the electronic receipt management server 40 from their own device (e.g., customer terminal 50, personal computer, etc.) and view and manipulate their own electronic receipts. For example, a customer can display a list of their electronic receipts on the screen of their device, or display a specific electronic receipt of theirs (e.g., an electronic receipt selected from the list) on the screen of their device (see Figure 8(B)). In addition, customers can perform various operations on the above list (e.g., sorting, filtering, outputting (sending data to their device)). In other words, the electronic receipt management server 40 performs processing (e.g., sorting, filtering, outputting) in response to the customer's (customer's device's) requests.

[0152] The receipt output pattern can be changed (see, for example, Figures 10(A) and 10(B)). Therefore, the electronic receipt file stored by the electronic receipt management server 40 (Figure 2(B)) may contain a mix of invoice-compliant electronic receipts (electronic receipts with registration numbers) and non-invoice-compliant electronic receipts (electronic receipts without registration numbers) for a given customer. In such cases, the customer can display a list of invoice-compliant and non-invoice-compliant receipts on the screen of their device, or output them to their device separately.

[0153] Furthermore, as mentioned above, in the case of electronic receipt members, the electronic receipt file stored by the electronic receipt management server 40 stores electronic receipts from multiple stores. In such cases, the customer (electronic receipt member) can display or output to their device separate lists of invoice-enabled / non-invoice-enabled receipts, store-specific lists, and store-specific lists of invoice-enabled / non-invoice-enabled receipts.

[0154] (Sales data processing device, sales data processing system, receipt management system) The registration and settlement device 10 and settlement device 11 process (generate) transaction information related to the sale of goods, so they may also be called sales data processing devices. The transaction management server 30 receives transaction information from the registration and settlement device 10 and settlement device 11 and stores it in a transaction file, so it may also be called a sales data processing server (or sales data processing device). The customer management server 20 manages the output of receipts (electronic receipts, paper receipts) (for example, by storing receipt setting information), so it may also be called a receipt management server (or receipt management device). Since System 1 includes the registration and settlement device 10 (settlement device 11) and the transaction management server 30, System 1 may also be called a sales data processing system. Since System 1 includes the customer management server 20, System 1 may also be called a receipt management system.

[0155] As described above, System 1 of this embodiment allows electronic receipts to be suitably adapted to the invoice system.

[0156] For example, the registration and settlement device 10 can provide each customer with a receipt of a type appropriate to them (electronic receipt / paper receipt) based on their customer identification information (or electronic receipt member identification information), in a format suitable for each customer (invoice-compatible / invoice-incompatible).

[0157] Furthermore, the registration and settlement device 10 does not generate receipt data for invoice-compliant paper receipts when generating receipt data for invoice-compliant electronic receipts, and conversely, does not generate receipt data for invoice-compliant electronic receipts when generating receipt data for invoice-compliant paper receipts. This prevents a situation where two receipts exist, one for invoice-compliant electronic receipts and one for invoice-compliant paper receipts (a situation that could be problematic from a tax perspective).

[0158] (Variations, etc.) Although embodiments have been described above, the configuration of the equipment, the data configuration, the processing flow, the display and output modes, etc., can be changed as appropriate, for example, as shown in the following Modifications 1 to 11. Furthermore, Modifications 1 to 11 can be combined as appropriate.

[0159] (Modification 1) In the above embodiment, an example was described in which customer identification information is obtained from a membership card, etc. (membership card, device carried by the customer), and receipt setting information (Figure 2) is obtained based on the obtained customer identification information (specifically by querying the customer management server 20). However, receipt setting information may also be obtained directly from the membership card, etc. In other words, the registration and settlement device 10 may obtain receipt setting information by reading the barcode, IC chip, or magnetic stripe of the membership card, or it may obtain receipt setting information from the memory of a smartphone or wearable device carried by the customer.

[0160] (Modification 2) In the above embodiment, when the registration settlement device 10 outputs both an electronic receipt and a paper receipt and is invoice-compatible, an example was described in which it specifies, based on a setting, whether to output an invoice-compatible electronic receipt and a non-invoice-compatible paper receipt, or a non-invoice-compatible electronic receipt and an invoice-compatible paper receipt. However, it may also be specified based on a predetermined priority order. The priority order may be electronic receipt. In other words, output pattern 8 does not need to be provided.

[0161] Specifically, it is not necessary to specify a qualified invoice designation category in the receipt setting information shown in Figures 4(A) and 4(B).

[0162] In other words, the correspondence between the values ​​for each category in Figure 4(A) (no designated qualified invoice category) and the output patterns in Figure 3 (output patterns 1 to 7) is as follows. (1) Electronic receipt requirement "0 (not required)", paper receipt requirement "0 (not required)" → Output pattern 1 (2) Electronic receipt requirement "0 (not required)", paper receipt requirement "1 (required)", qualified invoice requirement "0 (not required)" → Output pattern 2 (3) Electronic receipt requirement category "0 (not required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "1 (required)" → Output pattern 3 (4) Electronic receipt requirement category "1 (required)", paper receipt requirement category "0 (not required)", qualified invoice requirement category "0 (not required)" → Output pattern 4 (5) Electronic receipt requirement category "1 (required)", paper receipt requirement category "0 (not required)", qualified invoice requirement category "1 (required)" → Output pattern 5 (6) Electronic receipt requirement category "1 (required)", paper receipt requirement category "1 (required)", qualified invoice requirement category "0 (required)" → Output pattern 6 (7) Electronic receipt requirement category "1 (Required)", Paper receipt requirement category "1 (Required)" → Output pattern 7 (Output pattern 7 will be used based on priority)

[0163] Furthermore, the correspondence between the values ​​for each category in Figure 4(B) (no designated qualified invoice category) and the output patterns in Figure 3 (output patterns 1 to 7) is as follows. (1) Output receipt category "0 (not required)" → Output pattern 1 (2) Output receipt category "2 (paper receipt)", qualified invoice requirement category "0 (not required)" → Output pattern 2 (3) Output receipt category "2 (paper receipt)", qualified invoice requirement category "1 (required)" → Output pattern 3 (4) Output receipt category "1 (electronic receipt)", qualified invoice requirement category "0 (not required)" → Output pattern 4 (5) Output receipt category "1 (electronic receipt)", qualified invoice requirement category "1 (required)" → Output pattern 5 (6) Output receipt category "3 (both)", qualified invoice requirement category "0 (required)" → Output pattern 6 (7) Output receipt category "3 (both)", qualified invoice requirement category "1 (required)" → Output pattern 7 (output pattern 7 based on priority)

[0164] (Modification 3) In the above embodiment, an example was described in which the output pattern of the customer's receipt is set to output pattern 2 when the read flag is not set (step S33 in Figure 6), but it may also be set to output pattern 3. In other words, if the registration settlement device 10 does not acquire customer identification information, it may issue a paper receipt that does not support invoices (output pattern 2), or it may issue a paper receipt that supports invoices (output pattern 3).

[0165] (Modification 4) In the above embodiment, eight types of output patterns, output patterns 1 to 8, have been described, but the number of output patterns may be seven or less. For example, as shown in (a) to (d) below, there may be seven or fewer types.

[0166] (a) For example, there may be seven types of output patterns, 2 to 8. In other words, at least one of either an electronic receipt or a paper receipt may be output.

[0167] (b) Alternatively, there may be five output patterns, 1 to 5. That is, when an electronic receipt is output, the output of a paper receipt may be prohibited, and when a paper receipt is output, the output of an electronic receipt may be prohibited (it may also be the case that neither an electronic receipt nor a paper receipt is output).

[0168] (c) Alternatively, there may be four types of output patterns, 2 to 5. In other words, either an electronic receipt is printed without a paper receipt, or a paper receipt is printed without an electronic receipt (it may also be the case that only one of them, either an electronic receipt or a paper receipt, is always printed).

[0169] (d) Alternatively, there may be seven types of output patterns, 1 to 5, 7, and 8 (seven types obtained by excluding output pattern 6 from the eight types of output patterns in the above embodiment), or six types of output patterns, 2 to 5, 7, and 8 (six types obtained by excluding output pattern 6 from the seven types of output patterns in (a) above). In other words, output pattern 6 is a pattern that outputs two receipts of the same type (both receipts that do not support invoices), so it may be excluded. This is similar to the reason why there is no output pattern that outputs both an invoice-compatible electronic receipt and an invoice-compatible paper receipt as receipts of the same type.

[0170] (Modification 5) In the above embodiment, as a supplementary explanation to step S34 in Figure 6, it was explained that when the registration settlement device 10 generates information for electronic receipts, and in the case of non-cash payments (such as electronic money payments or credit card payments), it generates not only information for electronic receipts but also slip data for electronic slips. In other words, it was explained that the timing for generating the slip data for electronic slips is the same timing as the timing for generating the electronic receipt information. However, the timing for generating the slip data for electronic slips may be at a different timing (a different timing from the timing for generating the electronic receipt information).

[0171] For example, the registration and settlement device 10 may generate electronic slip data before sending payment information (payment data; information necessary for electronic money payment, information necessary for credit payment) to the payment server (electronic money server, credit server, etc.). (If the slip data includes information to be obtained (received) from the payment server after the payment (processing) is successfully completed at the payment server (e.g., an approval number), the registration and settlement device 10 may generate other parts of the electronic slip data (parts other than the information obtained from the payment server after the payment is successfully completed). In other words, the registration and settlement device 10 may start generating electronic slip data before sending payment information to the payment server. The payment server may, upon successful completion of the payment, send a payment completion notification (information indicating that the payment has been successfully completed) including the approval number to the registration and settlement device 10, or it may send a payment completion notification along with the approval number to the registration and settlement device 10. Alternatively, the transmission of the approval number may serve as the payment completion notification.

[0172] If the settlement is completed successfully (if an approval number is received), the registered settlement device 10 sends the electronic slip data to the electronic receipt management server 40. If the approval number obtained from the settlement server is not included in the slip data, the registered settlement device 10, upon receiving the approval number, simply sends the electronic slip data that it had created in advance (before obtaining the approval number from the settlement server) to the electronic receipt management server 40. If the approval number obtained from the settlement server is included in the slip data, the registered settlement device 10, upon receiving the approval number, sets the approval number in the electronic slip data that it had created in advance and sends it to the electronic receipt management server 40.

[0173] If the settlement is terminated abnormally (failed) (for example, if the device does not receive information that the settlement was completed successfully, or if it receives information that the settlement was terminated abnormally), the registered settlement device 10 will not send the pre-created electronic slip data to the electronic receipt management server 40 (it may delete it, or it may keep it as history without deleting it).

[0174] (Modification 6) In the above embodiment, as a supplementary explanation to step S34 in Figure 6, it was explained that when generating information for paper receipts, in the case of non-cash payments (such as electronic money payments or credit card payments), in addition to the information for paper receipts, slip data for paper slips is also generated. In other words, it was explained that the timing for generating the slip data for paper slips is the same as the timing for generating the information for paper receipts. However, the timing for generating the slip data for paper slips may be at a different timing (a different timing from the timing for generating the information for paper receipts), similar to the slip data for electronic slips described in Modification 5. For example, similar to the slip data for electronic slips described in Modification 5, the registration settlement device 10 may start generating the slip data for paper slips before sending the settlement information to the settlement server.

[0175] (Modification 7) In the above embodiment, it was explained that when the registration settlement device 10 generates information for electronic receipts and in the case of non-cash payments, it generates electronic receipt information in addition to slip data for electronic slips, and when the device generates information for paper receipts and in the case of non-cash payments, it generates paper receipt information in addition to slip data for paper slips. However, the necessity of electronic slips may be managed (set) using classifications or the like.

[0176] For example, even when an electronic receipt is printed in a non-cash payment (when both an electronic and a paper receipt is printed, or when only an electronic receipt is printed without a paper receipt), if the setting indicates that an electronic slip is not required, then it is not necessary to print the slip data for the electronic slip. Also, for example, even when an electronic receipt is not printed in a non-cash payment (when neither an electronic nor a paper receipt is printed, or when only a paper receipt is printed without an electronic receipt), if the setting indicates that an electronic slip is required, then the slip data for the electronic slip may be generated and sent to the electronic receipt management server 40.

[0177] Alternatively, the necessity of paper slips may be managed using categories or other methods, either in lieu of or in addition to the necessity of electronic slips.

[0178] (Modification 8) In the above embodiment, the explanation was omitted, but the store clerk can refer to (confirm) the settings (values ​​for each category) and output patterns based on the settings of the receipt setting information (Figures 4(A) to 4(E)). For example, in the case of the receipt setting information in Figure 4(A), the store clerk can refer to the electronic receipt requirement category, paper receipt requirement category, and output patterns for each customer from a management terminal (personal computer, etc.). The store clerk may also specify a customer and refer to the contents of that customer's receipt setting information. Alternatively, or in addition to the store clerk, each customer may refer to the settings of their own receipt setting information and output patterns based on the settings from their own terminal (e.g., customer terminal 50, personal computer, etc.).

[0179] Receipt settings are set by the store staff. Alternatively, each customer may set their own receipt settings, either on behalf of or in addition to the store staff. The same applies to changes in the settings. For example, in the case of the receipt settings shown in Figure 4(A), the store staff may set / change each customer's electronic receipt requirement or paper receipt requirement from a management terminal, or each customer may set / change their own electronic receipt requirement or paper receipt requirement from their own terminal. The history of settings / changes (date and time of setting change, content of setting change, person who made the setting change, etc.) may also be stored.

[0180] Alternatively, store employees may not be given the authority to set or change receipt settings themselves, but only the authority to view (refer to) the settings (current settings) that have been set or changed by the customer.

[0181] (Modification 9) In the above embodiment, a registration and settlement device 10 that performs registration processing and settlement processing was described as a device installed in the store. However, instead of or in addition to the registration and settlement device 10, a settlement device 11 (not shown) that performs settlement processing may be installed in the store. The settlement device 11 performs settlement processing to settle the price of the goods registered by the registration device 12 (not shown). The settlement process to settle the payment will be executed.

[0182] The registration device 12 may be a stationary device used by store staff to register products, or it may be a registration terminal used by customers to register products themselves at the sales floor. The registration terminal used by customers to register products at the sales floor may be a terminal attached to a shopping cart, or a terminal integrated with the shopping cart.

[0183] The settlement device 11 operates similarly to the registration settlement device 10, except for the part that registers the products. For example, the settlement device 11 identifies an output pattern and generates receipt information according to the output pattern. In addition, the contents of "notification of information regarding receipt output," "confirmation of receipt output," "return processing," "reissuance of paper receipts," and "electronic receipt members" described in the embodiment can also be applied similarly to the settlement device 11.

[0184] When the payment device 11 reads a membership card, it uses the customer identification information obtained from the membership card to obtain customer information (receipt setting information) from the customer management server 20. When a membership card is read by the registration device 12, the payment device 11 receives customer identification information from the registration device 12 (either directly or via another device) and uses the customer identification information received from the registration device 12 to obtain customer information (receipt setting information) from the customer management server 20. In other words, the payment device 11 can identify an output pattern and generate receipt information according to the output pattern, whether the customer identification information is obtained by its own device or by another device (registration device 12).

[0185] Furthermore, if a member card is read by the registration device 12, the registration device 12 may identify an output pattern, and the payment device 11 may receive the output pattern identified by the registration device 12.

[0186] (Modification 10) In the above embodiment, multiple servers have been described, but the functions of two or more servers may be implemented in a single server. For example, the customer management server 20 and the transaction management server 30 may be implemented (integrated) as a single server. In other words, the same server may manage, for example, transaction information and receipt setting information. Alternatively, the customer management server 20 and the electronic receipt management server 40 may be implemented as a single server, or the electronic receipt member server 21 and the electronic receipt management server 40 may be implemented as a single server. In other words, the same server may manage, for example, electronic receipts and receipt setting information.

[0187] (Modification 11) In the above embodiment, the explanation was omitted, but the registration and settlement device 10 (and settlement device 11) is a so-called thin client specialized in input / output interfaces, etc., and may, for example, display a screen generated by another device (for example, a cloud server) through a browsing function.

[0188] <Summary of Embodiments> [Technical field] The present invention relates to a sales data processing device. [Background technology] Technologies for issuing electronic receipts are known (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2003-006738 [Overview of the prefecture] [Problems the invention aims to solve] However, there is room for improvement in electronic receipts, for example, in relation to the invoice system (qualified invoice preservation method). This invention has been made in view of these circumstances and aims to provide a technology that allows electronic receipts to be suitably adapted to the invoice system. [Means for solving the problem]

[0189] (1) One aspect of this embodiment is a sales data processing device that provides a customer with a receipt for a sales transaction, comprising: a receipt provision method identification means for identifying a method of providing a receipt to the customer; and a receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means, wherein the receipt data generation means does not generate receipt data for a paper receipt that will become a qualified invoice (for an invoice-compatible electronic receipt) when generating receipt data for an electronic receipt that will become a qualified invoice (for an invoice-compatible electronic receipt) (for example, in the case of output pattern 5 or output pattern 7). According to the configuration of (1), electronic receipts can be appropriately adapted to the invoice system. For example, a situation where there are two types of receipts, such as an invoice-compliant electronic receipt and an invoice-compliant paper receipt, will not occur.

[0190] (2) One aspect of this embodiment is a sales data processing device that provides a customer with a receipt for a sales transaction, comprising: a receipt provision method identification means for identifying a method of providing a receipt to the customer; and a receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means, wherein the receipt data generation means is capable of generating receipt data for paper receipts that do not constitute a qualified invoice (for paper receipts that do not constitute an invoice) when generating receipt data for electronic receipts that constitute a qualified invoice (for electronic receipts that are invoice-compatible) (for example, in the case of output pattern 7). According to the configuration of (2), electronic receipts can be made suitable for use with the invoice system. For example, it is possible to output paper receipts that are compatible with the invoice system and can coexist with electronic receipts that are compatible with the invoice system.

[0191] (3) One aspect of this embodiment is a sales data processing device that provides a customer with a receipt for a sales transaction, comprising: a receipt provision method identification means for identifying a method of providing a receipt to the customer; and a receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means, wherein the receipt data generation means does not generate receipt data for an electronic receipt that will become a qualified invoice (for an electronic receipt that will become According to the configuration of (3), electronic receipts can be appropriately adapted to the invoice system. For example, a situation where there are two types of receipts, such as an invoice-compliant electronic receipt and an invoice-compliant paper receipt, will not occur.

[0192] (4) One aspect of this embodiment is a sales data processing device that provides a customer with a receipt for a sales transaction, comprising: a receipt provision method identification means for identifying a method of providing a receipt to the customer; and a receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means, wherein the receipt provision method identification means can identify whether an electronic receipt is required, whether a paper receipt is required, and whether a qualified invoice is required as the provision method (see Figure 4(A)). According to the configuration of (4), electronic receipts can be suitably adapted to the invoice system. For example, the output of receipts can be suitably controlled according to specific results.

[0193] (5) The receipt data generation means is characterized in that, when the receipt provision method identification means identifies that an electronic receipt is required, a paper receipt is required, and a qualified invoice is required, it generates receipt data for an electronic receipt that will be a qualified invoice and receipt data for a paper receipt that will not be a qualified invoice (for example, generated in order of priority). According to the configuration of (5), electronic receipts can be appropriately adapted to the invoice system. For example, when both electronic and paper receipts are printed and a qualified invoice is required, priority can be given to the electronic receipt in relation to the qualified invoice, so that the electronic receipt that becomes a qualified invoice is printed and the paper receipt that does not become a qualified invoice is printed.

[0194] (6) A sales data processing device according to any one of (1) to (5), comprising a correction means for correcting a transaction, wherein the receipt data generation means does not generate receipt data for an electronic receipt that will be a qualified invoice after the correction by the correction means, even if the receipt data generation means had generated receipt data for an electronic receipt that will be a qualified invoice in the transaction before the correction by the correction means. According to the configuration of (6), electronic receipts can be appropriately adapted to the invoice system. In other words, a situation in which multiple invoice-compliant electronic receipts exist for the same transaction will not occur.

[0195] (7) A sales data processing device according to any one of (1) to (6), characterized in that it is equipped with a cashless settlement means for settling by a non-cash method, the receipt provision method identification means can identify whether or not an electronic receipt is required as the provision method, the receipt data generation means generates receipt data for an electronic receipt along with electronic slip data for cashless settlement for transactions settled by cashless settlement using the cashless settlement means when the receipt provision method identification means identifies that an electronic receipt is required, and generates receipt data for a paper receipt and slip data for a paper slip for cashless settlement for transactions settled by cashless settlement using the cashless settlement means when the receipt provision method identification means identifies that an electronic receipt is not required. According to the configuration of (7), a receipt can be preferably issued depending on whether it is an electronic receipt or a paper receipt.

[0196] Furthermore, the processing of each of the above-described devices (registration and settlement device 10, settlement device 11, customer management server 20, transaction management server 30, electronic receipt management server 40, customer terminal 50) may be performed by recording the program for realizing the functions of each device (registration and settlement device 10, settlement device 11, customer management server 20, transaction management server 30, electronic receipt management server 40, customer terminal 50) on a computer-readable recording medium, loading the program recorded on this recording medium into a computer system, and executing it. Here, "loading the program recorded on the recording medium into a computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. Also, the recording medium includes internal or external recording media that can be accessed from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in an executable format on the terminal device. In other words, as long as it can be downloaded from the distribution server and installed in an executable format on the terminal device, the format in which it is stored on the distribution server is irrelevant. Furthermore, the program may be divided into multiple parts, downloaded at different times and then combined on the terminal device, and each of the divided programs may be distributed by a different distribution server. In addition, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Moreover, the above program may be intended to implement only a part of the functions described above.Furthermore, the above-mentioned functions may be implemented in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of symbols]

[0197] 1...System, 10...Registration and settlement device, 11...Settlement device, 12...Registration device, 20...Customer management server, 21...Electronic receipt member server, 30...Transaction management server, 40...Electronic receipt management server, 50...Customer terminal

Claims

1. A sales data processing device that provides customers with receipts for sales transactions, A means for identifying the method of providing receipts to the customer in question, A receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means. Equipped with, The receipt data generation means is When generating receipt data for electronic receipts that qualify as eligible invoices, do not generate receipt data for paper receipts that qualify as eligible invoices. A sales data processing device characterized by the following features.

2. A sales data processing device that provides customers with receipts for sales transactions, A means for identifying the method of providing receipts to the customer in question, A receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means. Equipped with, The receipt data generation means is When generating receipt data for electronic receipts that qualify as eligible invoices, it is possible to generate receipt data for paper receipts that do not qualify as eligible invoices. A sales data processing device characterized by the following features.

3. A sales data processing device that provides customers with receipts for sales transactions, A means for identifying the method of providing receipts to the customer in question, A receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means. Equipped with, The receipt data generation means is When generating receipt data for paper receipts that qualify as eligible invoices, do not generate receipt data for electronic receipts that qualify as eligible invoices. A sales data processing device characterized by the following features.

4. A sales data processing device that provides customers with receipts for sales transactions, A means for identifying the method of providing receipts to the customer in question, A receipt data generation means for generating receipt data for a receipt to be provided to the customer in accordance with the provision method identified by the receipt provision method identification means. Equipped with, The means for specifying the method of providing the receipt is: The aforementioned method of provision allows for the specification of whether electronic receipts, paper receipts, and qualified invoices are required. A sales data processing device characterized by the following features.

5. The receipt data generation means is If the receipt provision method identification means identifies whether an electronic receipt is required, whether a paper receipt is required, and whether a qualified invoice is required, then receipt data for an electronic receipt that will be a qualified invoice and receipt data for a paper receipt that will not be a qualified invoice are generated. The sales data processing device according to feature 4.

6. Correction methods for correcting transactions Equipped with, The receipt data generation means is Even if receipt data for electronic receipts that qualify as invoices was generated in the transaction prior to correction by the correction means, receipt data for electronic receipts that qualify as invoices will not be generated after correction by the correction means. A sales data processing device according to any one of claims 1 to 5.

7. Non-cash payment methods that are settled in a non-cash manner. Equipped with, The means for specifying the method of providing the receipt is: The aforementioned method of provision allows for the determination of whether or not an electronic receipt is necessary. The receipt data generation means is If the receipt provision method identification means identifies that an electronic receipt is required, the non-cash settlement means generates receipt data for the electronic receipt along with electronic slip data for the non-cash settlement for transactions settled by non-cash settlement. If the receipt provision method identification means determines that an electronic receipt is not required, the non-cash settlement means generates receipt data for paper receipts and slip data for paper slips for non-cash settlements for transactions settled by non-cash means. A sales data processing device according to any one of claims 1 to 5.

Images