JP7542857B2 - Receipt data management system - Google Patents

Description

The present invention relates to a receipt data management system that electronically manages receipt data.

Receipts are issued to prove receipt of payment in a transaction. In recent years, receipts have been digitized. For example, Patent Document 1 discloses a technology that can issue receipts electronically. This technology makes it possible to issue either an electronic receipt or a paper receipt, or both, depending on the customer's preference.

Patent Document 2 also discloses a system for managing receipt data that includes information about transaction receipts. In this system, the store's terminal device transmits receipt data to a provision server device, and displays a two-dimensional code for identifying the receipt data on the customer's terminal device. The customer's terminal device can read the displayed two-dimensional code, and based on the results, make a request to the provision server device for access to the receipt data.

JP 2004-151838 A Patent No. 6467565

The invoice system will be introduced from October 1, 2023. This invoice system refers to the method of storing qualified invoices, etc., and as one of the requirements for the input tax credit of consumption tax, it will be necessary to store "qualified invoices" issued by qualified invoice issuers. The information to be written on a qualified invoice is specified, and invoices, receipts, invoices, etc. must be issued in accordance with these regulations, but there is an issue in that the existing technology for digitizing receipts, etc. is not compatible with this invoice system.

In order to solve the above problems, the present invention provides the following receipt data management system. That is, the receipt data management system is composed of an issuing terminal that issues receipt data including information on the receipt content of a transaction to a customer, a customer terminal that receives receipt data from the issuing terminal, and a receipt data management server that manages the receipt data. The receipt data management server has a receipt data receiving unit that receives receipt data for each transaction from the issuing terminal, a receipt data storage unit that stores the received receipt data in association with the qualified invoice issuing business registration number of the business that issued the receipt data, a receipt data identification information generating unit that generates receipt data identification information that uniquely identifies the stored receipt data, and a receipt data identification information transmitting unit that transmits the generated receipt data identification information to the issuing terminal.

In addition to the above features, the issuing terminal provides a receipt data management system having a receipt data acquisition unit that acquires receipt data for each transaction, a receipt data transmission unit that transmits the acquired receipt data to the receipt data management server, a receipt data identification information receiving unit that receives from the receipt data management server the receipt data identification information generated based on the transmitted receipt data, and a receipt data identification information output unit that outputs the received receipt data identification information to a customer terminal.

In addition to the above features, the customer terminal has a receipt data identification information acquisition unit that acquires the receipt data identification information output by the receipt data identification information output unit, and a presentation request unit that requests the receipt data management server to present the receipt data identified by the acquired receipt data identification information, and the receipt data management server has a presentation request acceptance unit that accepts the presentation request, and a receipt data presentation unit that presents the receipt data to the customer terminal in response to the accepted presentation request.

In addition to the above features, the receipt data management system further provides a receipt data management system in which the receipt data management server has a format output unit that outputs the stored receipt data according to a specified format.

In addition to the above features, the receipt data management server provides a receipt data management system having a declaration information acquisition unit that acquires tax-related declaration information, a consistency check unit that checks the consistency of the acquired declaration information by referring to the receipt data stored in the receipt data storage unit, and a check result output unit that outputs the check result by the consistency check unit.

This invention provides a receipt data management system that electronically manages receipt data in accordance with the invoice system.

Conceptual diagram showing the overview of the receipt data management system A block diagram showing an example of the functional configuration of a receipt data management system. FIG. 13 is a diagram showing an example of receipt data stored in a receipt data storage unit; FIG. 13 is a conceptual diagram showing an example of displaying receipt data related to a request on a customer terminal. A flow chart showing an example of the flow of information processing in the receipt data management system. Conceptual diagram showing an example of the hardware configuration for realizing the receipt data management system

The following describes embodiments of the present invention with reference to the accompanying drawings. Note that the present invention should not be limited to these embodiments, and may be implemented in various forms without departing from the spirit of the present invention.

The relationships between the embodiments and the claims are as follows: embodiment 1 mainly relates to claims 1 to 3, 6 to 11, and 14 to 16, embodiment 2 mainly relates to claims 4, 6 to 8, 12, and 17, and embodiment 3 mainly relates to claims 5 to 8, 13, and 18.
Example 1
＜Overview＞

Figure 1 is a conceptual diagram showing an overview of the receipt data management system. For example, when an issuing terminal, such as a store's POS register, receives payment for a product or other item provided to a customer, it sends the transaction details as receipt data to a receipt data management server. In response, the receipt data management server sends a two-dimensional code to the issuing terminal as information for identifying the receipt data. The issuing terminal displays the received two-dimensional code on a display, and the customer can access the receipt data by reading the two-dimensional code displayed by their own terminal and requesting the receipt data management server to present the receipt data identified by the read two-dimensional code based on the reading result. This receipt data is then associated with the registration number of the issuer's qualified invoice issuing business. As a result, the receipt data in the receipt data management system is adapted to the invoice system, which is beneficial to issuing businesses and customers who use this system.

The following describes the functions and processing flow of the receipt data management system, as well as the contents of the hardware. The functional blocks of the system described below can be realized as a combination of hardware and software. Specifically, if a computer is used, the hardware components include a CPU (Central Processing Unit), main memory, bus, or secondary storage device (hard disk drive, non-volatile memory, storage media such as CDs and DVDs, and drives to read these media, etc.), input devices used to input information, printers, display devices, and other external peripheral devices, as well as interfaces for these external peripheral devices, communication interfaces, driver programs and other application programs for controlling these hardware, and user interface applications. Then, by the calculation processing of the CPU according to the program deployed on the main memory, data input from input devices and other interfaces and stored in memory or hard disk is processed and stored, and commands for controlling the above hardware and software are generated. Alternatively, the functional blocks of the system can be realized by dedicated hardware.

This invention can be realized not only as a system, but also as a method. A part of such an invention can be configured as software. Furthermore, a program used to cause a computer to execute such software, and a recording medium on which the program is fixed, are naturally included in the technical scope of this invention (the same applies throughout this specification).
<Functional configuration>

2 is a block diagram showing an example of the functional configuration of the receipt data management system. As shown in FIG. 2, the receipt data management system includes a receipt data management server 200, an issuing terminal 210, and a customer terminal 220.
(Receipt data management server)

The receipt data management server 200 is a server that manages receipt data, and has a receipt data receiving unit 201, a receipt data storage unit 202, a receipt data identification information generating unit 203, a receipt data identification information transmitting unit 204, a presentation request receiving unit 205, and a receipt data presentation unit 206.

The receipt data receiving unit 201 has a function to receive receipt data for each transaction from the issuing terminal. The receipt data is data that includes information on the receipt content of the transaction. The information included in the receipt data includes information identifying each transaction, the date of the transaction, the content of the product or service related to the transaction, the total amount and applicable tax rate of the tax-excluded or tax-inclusive price of the product or service related to the transaction categorized by tax rate, the amount of consumption tax categorized by tax rate, the name or title of the person receiving the transaction voucher, the name or title of the business issuing the receipt data, the payment method, etc.

The receipt data storage unit 202 has the function of storing the received receipt data in association with the qualified invoice issuer registration number of the business that issued the receipt data. The qualified invoice issuer registration number is a number that is assigned when a business applies by submitting an application form for registration as a qualified invoice issuer, and businesses with a corporate number are assigned "T + corporate number", while sole proprietors without a corporate number are assigned "T + 13-digit number".

Figure 3 is a diagram showing an example of receipt data stored in the receipt data storage unit. The receipt data shown is receipt data issued by "XxX Store" and is stored in association with the name of XxX Store and the store's registration number for the qualified invoice issuer "T3012345678901". The receipt data consists of the following fields: "Identification ID", "Item (unit price) x number", "Price excluding tax", "Tax rate", "Tax amount", "Total", "Payment method", and "Addressee". A "Notes" field may also be provided.

The receipt data stored in the receipt data storage unit may already contain the qualified invoice issuing business registration number of the business etc. to which the receipt data pertains.

In addition, the receipt data stored in the receipt data storage unit may be assigned a timestamp of when the receipt data was received. Since the time when the receipt data was issued by the issuing terminal and the time when the receipt data was received by the receipt data management server do not necessarily coincide, it is preferable to assign a timestamp of when the receipt data was received in order to manage the stored receipt data.

The receipt data stored may be stored as receipt data for the issuing business, or as receipt data for the recipient. In the example of Figure 3, the data is stored as receipt data for the issuing business, "XxX Store."

It is also possible to configure the system to discard or modify the received receipt data or stored receipt data. There may be an error in the receipt data issued by the issuing terminal, or the transaction related to that receipt data may be canceled. Therefore, it is preferable to configure the system to discard or modify the received or stored receipt data depending on the situation. Receipt data can be discarded or modified in response to a request from the issuing terminal or the customer terminal, but from the perspective of preventing unauthorized use of receipt data, it is preferable to configure the system to discard or modify only when certain conditions are met, such as an agreement between the issuing business, which is the party to the transaction related to the receipt data, and the receiving customer. It is also preferable to configure the system to store a history of receipt data being discarded or modified.

The receipt data identification information generating unit 203 has a function of generating receipt data identification information that uniquely identifies the stored receipt data. Examples of receipt data identification information include barcodes and two-dimensional codes. Examples of two-dimensional codes include matrix-type QR codes (registered trademark) and stack-type PDF417.

The receipt data identification information transmission unit 204 has a function of transmitting the generated receipt data identification information to the issuing terminal. The generated receipt data identification information is transmitted to the issuing terminal that issued the receipt data on which the generated receipt data identification information is based.

The presentation request receiving unit 205 has a function of receiving a presentation request. A presentation request is a request made by a customer terminal (described later) to the receipt data management server to present receipt data identified by the acquired receipt data identification information.

The receipt data presentation unit 206 has a function of presenting receipt data to the customer terminal in response to the received presentation request. Here, presentation means, for example, sending receipt data to the customer terminal or allowing the receipt data to be viewed, and the customer terminal can display the receipt data related to the presentation request on its own display or download it and store it in a storage device.
(Issuing terminal) Issues receipt data including transaction receipt details to the customer.

The issuing terminal 210 has a receipt data acquisition unit 211, a receipt data transmission unit 212, a receipt data identification information receiving unit 213, and a receipt data identification information output unit 214. The issuing terminal 210 issues receipt data including information on the receipt details of the transaction. This receipt data is the receipt data in the description of the receipt data management server. The issuing terminal is specifically a device used in a store or business where a transaction is performed, such as a POS register device, a tablet terminal, a smartphone, or a personal computer.

The receipt data acquisition unit 211 has a function to acquire receipt data for each transaction. By inputting various details about the transaction (product, quantity, etc.) into the issuing terminal, receipt data such as that shown in FIG. 3 can be acquired.

The receipt data transmission unit 212 has a function of transmitting the acquired receipt data to the receipt data management server. The receipt data may be transmitted by associating the registration number of the qualified invoice issuing business of the business related to the issuing terminal with the receipt data, or may be configured to transmit the receipt data including the registration number of the qualified invoice issuing business of the business that is the trading entity that issued the receipt data.

The receipt data identification information receiving unit 213 has a function of receiving the receipt data identification information generated based on the transmitted receipt data from the data management server. The receipt data management server generates receipt data identification information that identifies the receipt data transmitted from the issuing terminal and transmits the generated receipt data identification information to the issuing terminal, and the receipt data identification information receiving unit receives the transmitted receipt data identification information.

The receipt data identification information output unit 214 has a function of outputting the received receipt data identification information to the customer terminal. The receipt data identification information is output, for example, by displaying a two-dimensional code on a display provided in the issuing terminal or on a display connected to the issuing terminal via a network or the like so that it can be read by the customer terminal. The two-dimensional code may also be printed, in which case only the two-dimensional code may be printed, or receipt data identified by the two-dimensional code may be printed like a receipt, and the two-dimensional code may be printed together with the two-dimensional code. If the output of the receipt data identification information output unit is printing, the date and time of printing may be recorded.
(Customer terminal)

The customer terminal 220 has a receipt data specific information acquisition unit 221 and a presentation request unit 222. The customer terminal 220 receives receipt data from the issuing terminal. This receipt data is the receipt data described in the receipt data management server. The customer terminal is specifically a device used by a customer, such as a smartphone or tablet terminal.

The receipt data identification information acquisition unit 221 has a function of acquiring the receipt data identification information output by the receipt data identification information output unit. Specifically, the customer terminal acquires the receipt data identification information by photographing and decoding a two-dimensional code or the like that is the receipt data identification information displayed on the display of the issuing terminal. It can also be configured to acquire the receipt data identification information by reading a two-dimensional code printed by the issuing terminal.

The receipt data identification information is not limited to information that can be displayed on the issuing terminal so that it can be read by optical means on the customer terminal (such as a two-dimensional code), but may also be information that can be transmitted from the issuing terminal to the customer terminal via short-range wireless or a network.

The presentation request unit 222 has a function of requesting the receipt data management server to present receipt data identified by the receipt data identification information acquired by the receipt data identification information acquisition unit. By requesting presentation, as described above, the receipt data management server transmits receipt data identified by the receipt data identification information related to the request to the customer terminal, or allows the receipt data to be viewed, etc. Then, the customer terminal can display the requested receipt data on its own display.

Figure 4 is a conceptual diagram showing an example of displaying requested receipt data on a customer terminal. As shown in the figure, a receipt 402 is displayed on a display 401 of a smartphone 400, which is the customer terminal. This receipt lists the transaction date and time, the product involved in the transaction, the quantity, the applicable tax rate, the total price, etc., and also lists a registration number along with the address of the "XX store" that is the issuer of the receipt data (403). In addition to storing the displayed receipt data (404), requests to discard (405) or modify (406) the data can be accepted, as explained for the receipt data storage unit of the receipt data management server.

In addition, by associating receipt data with identification information of the customer terminal, the receipt data management server can be configured to collectively store and manage receipt data associated with the identification information of the customer terminal. In addition, the personal number (My Number) of the user of the customer terminal may be used as the identification information.

In addition, the receipt data can be configured to include information about the account items of the transaction. By configuring in this way, it becomes possible to easily perform journal entry when using the receipt data to prepare documents such as tax returns.
<Processing flow>

Figure 5 is a flow diagram showing an example of the flow of information processing in the receipt data management system. Note that dashed arrows indicate the flow of information. As shown in the figure, the issuing terminal acquires receipt data for each transaction (step S311). Then, the acquired receipt data is sent to the receipt data management server (step S312). Then, receipt data identification information generated based on the sent receipt data is received from the data management server (step S313). Then, the received receipt data identification information is output to the customer terminal (step S314).

The receipt data management server receives receipt data for each transaction from the issuing terminal (step S301). The received receipt data is then stored in association with the qualified invoice issuing business registration number of the business that issued the receipt data (step S302). Receipt data identification information that uniquely identifies the stored receipt data is then generated (step S303). The generated receipt data identification information is then sent to the issuing terminal (step S304). A request to present receipt data is then accepted from the customer terminal device (step S305). The receipt data is then presented to the customer terminal in response to the accepted presentation request (step S306).

The customer terminal acquires the receipt data identification information output in step S314 at the issuing terminal (S321), and then requests the receipt data management server to present the receipt data identified by the acquired receipt data identification information (step S322).
<Hardware configuration>

Figure 6 is a conceptual diagram showing an example of the configuration of hardware that realizes the receipt data management system. As shown in the figure, the receipt data management system is composed of a receipt data management server 500, an issuing terminal 510, and a customer terminal 520, each of which has a CPU 501, 511, 521 that performs various calculation processing, a RAM 502, 512, 522 that is a volatile storage medium, a storage 503, 513, 523 such as a flash memory or HDD that is a non-volatile storage medium, a communication interface 504, 514, 524, and an input/output interface 505, 515, 525 such as a display or a printer, and the customer terminal has a camera 526. The RAM 502, 512, 522 reads out programs that perform various calculation processing to have the CPU 501, 511, 521 execute them, and provides a work area (working area) for the programs. Additionally, RAM 502, 512, and 522 are assigned multiple addresses, and programs executed by CPUs 501, 511, and 521 can exchange data and perform processing by identifying and accessing those addresses (this is true throughout this specification).

The functions of the receipt data receiving unit 201, receipt data identification information transmitting unit 204, presentation request accepting unit 205, and receipt data presenting unit 206 of the receipt data management server 200 in FIG. 2 are mainly realized by the CPU 501, RAM 502, communication interface 504, and input/output interface 505 in FIG. 6. The functions of the receipt data storage unit 202 and receipt data identification information generating unit 203 in FIG. 2 are mainly realized by the CPU 501, RAM 502, and storage 503 in FIG. 6.

The functions of the receipt data acquisition unit 211 and receipt data identification information output unit 214 of the issuing terminal 210 in FIG. 2 are mainly realized by the CPU 511, RAM 512, and input/output interface 515 in FIG. 6. The functions of the receipt data transmission unit 212 and receipt data identification information reception unit 213 in FIG. 2 are mainly realized by the CPU 511, RAM 512, and communication interface 514 in FIG. 6.

The functions of the receipt data identification information acquisition unit 221 of the customer terminal 220 in Fig. 2 are mainly realized by the CPU 521, RAM 522, communication interface 524, and camera 526 in Fig. 6. The presentation request unit 222 in Fig. 2 is mainly realized by the CPU 521, RAM 522, and communication interface 524 in Fig. 6.
＜Effects＞

According to this embodiment, it is possible to provide a receipt data management system that electronically manages receipt data in accordance with the invoice system.
Example 2
＜Overview＞

The receipt data management system of this embodiment is based on the first embodiment, and has a feature in that receipt data is output in accordance with a predetermined format such as a financial statement or a final tax return.
<Functional configuration>

The functional configuration of this embodiment is the receipt data management server of embodiment 1, which further includes a format output section.

The format output unit has a function of outputting the stored receipt data according to a prescribed format. Prescribed formats include financial statements and tax returns, and the items to be recorded and the layout are specified for each format. The format output unit outputs the stored receipt data according to these specifications, and can create financial statements, tax returns, etc. The output may be in the form of a printout, or may be in the form of generating an electronic file in a prescribed format.

As described in the first embodiment, the stored receipt data can be accumulated and managed as receipt data related to the issuing terminal, or as receipt data related to the customer terminal that receives the receipt data. The format output unit, for example, reads out the stored receipt data related to the issuing terminal in response to a request from the issuing terminal, performs calculations as necessary, and outputs the data in a specified format by writing (arranging) the data in a specified layout. For example, when outputting in the form of a monthly financial statement, information to be written, such as sales amount, purchase amount, and borrowing amount, is extracted from the receipt data for that month, calculated, and output. When outputting a final tax return in response to a request from a customer terminal, the expenditure for each account item shown in the receipt data related to the customer terminal is calculated and written in the necessary expenses column, and output as a final tax return. When outputting according to a specified format, if there is information that should be written in the format but is not included in the receipt data, the format output unit can be configured to include a means for requesting and accepting input of the information.
<Processing flow>

The process flow of the receipt data management system of this embodiment is basically the same as the process flow of the receipt data management system of embodiment 1. In the receipt data management system of this embodiment, the receipt data management server further includes a step of outputting stored receipt data in a predetermined format in response to an output request from the issuing terminal or the customer terminal.
<Hardware configuration>

The receipt data management system of this embodiment can be realized by the hardware configuration shown in Fig. 6, similar to that of embodiment 1. The functions of the format output unit of the receipt data management system of this embodiment are mainly realized by the CPU 501, RAM 502, communication interface 504, and input/output interface 505 in Fig. 6.
＜Effects＞

According to this embodiment, the accumulated receipt data can be used to create documents in a specified format, which can be useful in reducing the amount of paperwork required.
Example 3
＜Overview＞

The receipt data management system of this embodiment is based on the first or second embodiment, and is characterized in that the receipt data management server checks the consistency of tax-related reporting information.
<Functional configuration>

The functional configuration of this embodiment is the receipt data management server of embodiment 1 or embodiment 2, further including a declaration information acquisition unit, a consistency check unit, and a check result output unit.

The tax return information acquisition unit has a function of acquiring tax-related tax return information. Tax-related tax return information is, for example, information about expenses and deductions to be entered in a tax return. The tax return information can be acquired by receiving it from an issuer terminal or a customer terminal. It may also be acquired from a terminal other than an issuer terminal or a customer terminal (for example, a terminal at an accountant's office, a tax accountant's office, a tax office, or the like).

The consistency check unit has a function of checking the consistency of the acquired declaration information by referring to the receipt data stored in the receipt data storage unit. The consistency check (etc.) may be in the form of confirming the accuracy of various information such as the transaction date and time and the amount received in the receipt data related to a transaction, or, for example, may be in the form of searching and extracting receipt data associated with identification information that identifies the filer of the final tax return, using the amount of utility expenses in a final tax return as declaration information, calculating the amount of utility expenses from the receipt data, and comparing this with the amount of utility expenses related to the declaration information to check the consistency.

As a mode of acquiring tax-related reporting information, the system may be configured to acquire tax returns and other documents by reading them with a scanner or the like. It may be configured to determine whether the acquired document conforms to a specified format, and if so, to read the details written on the document and check the consistency of the details by referring to the receipt data stored in the receipt data storage unit.

The receipt data management server obtains tax-related declaration information and returns the results of checking the consistency of that declaration information to a terminal other than the issuing terminal and the customer terminal as described above, but it is preferable to set certain conditions and processes for granting authorization to use this receipt data management system to these other terminals.

The check result output unit has a function of outputting the check result by the consistency check unit. The check result may be output in the form of a printout or may be output as an electronic file in a predetermined format.
<Processing flow>

The process flow of the receipt data management system of this embodiment is basically the same as the process flow of the receipt data management system of embodiment 1 or embodiment 2. The receipt data management server of this embodiment further includes a declaration information acquisition step for acquiring declaration information related to tax, a consistency check step for checking the consistency of the acquired declaration information by referring to receipt data stored in the receipt data storage unit, and a check result output step for outputting the check result obtained by the consistency check step.
<Hardware configuration>

The receipt data management system of this embodiment can be realized by the hardware configuration shown in Fig. 6 according to embodiment 1 or embodiment 2. The functions of the declaration information acquisition unit of the receipt data management server of this embodiment are mainly realized by CPU 501, RAM 502, communication interface 504, and input/output interface 505 in Fig. 6. The functions of the consistency check unit are mainly realized by CPU 501, RAM 502, and storage 503 in Fig. 6. The functions of the consistency check unit are mainly realized by CPU 501, RAM 502, communication interface 504, and input/output interface 505 in Fig. 6.
＜Effects＞

According to this embodiment, the accumulated receipt data can be referenced to check the consistency of the declaration information.

200, 500: Receipt data management server 210, 510: Issuer terminal 220, 520: Customer terminal 201: Receipt data receiving unit 202: Receipt data storage unit 203: Receipt data identification information generating unit 204: Receipt data identification information transmitting unit 205: Presentation request receiving unit 206: Receipt data presenting unit 211: Receipt data acquiring unit 212: Receipt data transmitting unit 213: Receipt data identification information receiving unit 214: Receipt data identification information output unit 221: Receipt data identification information acquiring unit 222: Presentation request unit 501, 511, 521: CPU
502, 512, 522: RAM
503, 513, 523: Storage 504, 514, 524: Communication interface 505, 515, 525: Input/output interface 526: Camera

Claims (18)

A receipt data management system comprising an issuing terminal which issues receipt data including information on receipt details of a transaction to a customer, a customer terminal which receives receipt data from the issuing terminal, and a receipt data management server which manages the receipt data,
The receipt data management server includes:
a receipt data receiving unit for receiving receipt data for each transaction from the issuing terminal;
a receipt data storage unit that stores the received receipt data in association with the qualified invoice issuing business registration number of the business that issued the receipt data;
a receipt data identification information generating unit that generates receipt data identification information that uniquely identifies the stored receipt data;
a receipt data identification information transmitting unit that transmits the generated receipt data identification information to the issuing terminal;
A receipt data management system having: The issuing terminal,
A receipt data acquisition unit that acquires receipt data for each transaction;
a receipt data transmission unit that transmits the acquired receipt data to the receipt data management server;
a receipt data identification information receiving unit that receives the receipt data identification information generated based on the transmitted receipt data from a receipt data management server;
a receipt data identification information output unit that outputs the received receipt data identification information to a customer side terminal;
The receipt data management system according to claim 1 , further comprising: The customer side terminal is
a receipt data identification information acquisition unit that acquires the receipt data identification information output by the receipt data identification information output unit;
a presentation request unit that requests the receipt data management server to present the receipt data identified by the acquired receipt data identification information;
The receipt data management server includes:
a presentation request receiving unit that receives the presentation request;
3. The receipt data management system according to claim 2, further comprising a receipt data presentation unit which presents the receipt data to a customer terminal in response to the received presentation request. The receipt data management server includes:
4. The receipt data management system according to claim 1, further comprising a format output unit that outputs the stored receipt data in accordance with a predetermined format. The receipt data management server includes:
A tax return information acquisition unit that acquires tax return information;
a consistency check unit that checks the consistency of the acquired declaration information by referring to the receipt data stored in the receipt data storage unit;
a check result output unit that outputs a check result by the consistency check unit;
The receipt data management system according to any one of claims 1 to 4, further comprising: A receipt data management server according to any one of claims 1 to 5. An issuing terminal that issues receipt data including information on transaction receipts to a customer,
A receipt data acquisition unit that acquires receipt data for each transaction;
a receipt data transmission unit that transmits the acquired receipt data to a receipt data management server that manages receipt data by associating the receipt data with the registration number of the qualified invoice issuing business of the business that issues the receipt data, or by including the registration number of the qualified invoice issuing business of the business that issues the receipt data;
a receipt data identification information receiving unit that receives, from the receipt data management server, receipt data identification information that is information that uniquely identifies the receipt data stored in association with the qualified invoice issuing business registration number of the business that issued the receipt data, based on the transmitted receipt data;
and a receipt data identification information output unit that outputs the received receipt data identification information to a customer terminal. A customer terminal that receives receipt data from the issuing terminal,
a receipt data identification information acquisition unit that acquires receipt data identification information, which is information that uniquely identifies the receipt data stored in association with the qualified invoice issuing business registration number of the business that issued the receipt data, from a receipt data management server that manages the receipt data;
a presentation request unit that requests the receipt data management server to present the receipt data identified by the acquired receipt data identification information,
A customer terminal displays the receipt data related to the request together with the registration number of the qualified invoice issuing business of the business that issued the receipt data. A method for operating a receipt data management system comprising an issuing terminal that issues receipt data including information on transaction receipts to a customer, a customer terminal that receives receipt data from the issuing terminal, and a receipt data management server that manages the receipt data, comprising:
A step executed by the receipt data management server,
a receipt data receiving step of receiving receipt data for each transaction from the issuing terminal;
a receipt data storage step of storing the received receipt data in association with the qualified invoice issuing business registration number of the business that issued the receipt data;
a receipt data identification information generating step of generating receipt data identification information that uniquely identifies the stored receipt data;
a receipt data identification information transmission step of transmitting the generated receipt data identification information to the issuing terminal;
A method of operating a receipt data management system comprising: A step performed by the issuing terminal,
A receipt data acquisition step for acquiring receipt data for each transaction;
a receipt data transmission step of transmitting the acquired receipt data to a receipt data management server;
a receipt data identification information receiving step of receiving, from a data management server, the receipt data identification information generated based on the transmitted receipt data;
a receipt data identification information output step of outputting the received receipt data identification information to a customer side terminal;
10. The method of claim 9, further comprising: A step executed by the customer terminal,
a receipt data identification information acquiring step of acquiring the receipt data identification information outputted in the receipt data identification information outputting step;
a presentation request step of requesting a receipt data management server to present receipt data identified by the acquired receipt data identification information;
A step executed by the receipt data management server,
a presentation request receiving step of receiving the presentation request;
a receipt data presentation step of presenting receipt data to a customer terminal in response to the received presentation request;
11. The method of claim 10, further comprising: A step executed by the receipt data management server,
a format output step of outputting the stored receipt data in accordance with a predetermined format;
A method for operating a receipt data management system according to any one of claims 9 to 11. A step executed by the receipt data management server,
A tax return information acquisition step for acquiring tax return information;
a consistency check step of checking the consistency of the acquired declaration information by referring to the receipt data stored in the receipt data storage step;
a check result output step for outputting a check result obtained by the consistency check step;
A method for operating the receipt data management system according to any one of claims 9 to 12. An operation program for a receipt data management system comprising an issuing terminal that issues receipt data including information on receipt details of a transaction to a customer, a customer terminal that receives receipt data from the issuing terminal, and a receipt data management server that manages the receipt data,
On the receipt data management server,
a receipt data receiving step of receiving receipt data for each transaction from the issuing terminal;
a receipt data storage step of storing the received receipt data in association with the qualified invoice issuing business registration number of the business that issued the receipt data;
a receipt data identification information generating step of generating receipt data identification information that uniquely identifies the stored receipt data;
a receipt data identification information transmission step of transmitting the generated receipt data identification information to the issuing terminal;
An operating program for a receipt data management system for causing a computer to execute the above. At the issuing terminal,
A receipt data acquisition step for acquiring receipt data for each transaction;
a receipt data transmission step of transmitting the acquired receipt data to a receipt data management server;
a receipt data identification information receiving step of receiving, from a data management server, the receipt data identification information generated based on the transmitted receipt data;
a receipt data identification information output step of outputting the received receipt data identification information to a customer side terminal;
15. An operation program for the receipt data management system according to claim 14, for causing an electronic computer to execute the above steps. At the customer side terminal,
a receipt data identification information acquiring step of acquiring the receipt data identification information outputted in the receipt data identification information outputting step;
a presentation request step of requesting a receipt data management server to present receipt data identified by the acquired receipt data identification information;
In the receipt data management server,
a presentation request receiving step of receiving the presentation request;
a receipt data presentation step of presenting receipt data to a customer terminal in response to the received presentation request;
16. An operation program for the receipt data management system according to claim 15, for causing an electronic computer to execute the above steps. In the receipt data management server,
a format output step of outputting the stored receipt data in accordance with a predetermined format;
17. An operation program for the receipt data management system according to any one of claims 14 to 16, which is executed by an electronic computer. In the receipt data management server,
A tax return information acquisition step for acquiring tax return information;
a consistency check step of checking the consistency of the acquired declaration information by referring to the receipt data stored in the receipt data storage step;
a check result output step for outputting a check result obtained by the consistency check step;
18. An operation program for the receipt data management system according to claim 14, which causes an electronic computer to execute the steps of:

Images