Information processing device, program, and information processing system
The system automates the creation and printing of receipt images by using QR codes to streamline the process of linking payment data and receipt images, reducing user effort and enhancing efficiency in expense application processing.
Patent Information
- Application Number
- JP2023065220
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-12
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2043-04-12
Smart Images

Figure 2024156236000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device, a program, and an information processing system. [Background technology]
[0002] In recent years, with the spread of cashless services, opportunities to use cashless payments via smartphones have increased. Cashless services are widely used in business settings, and it is essential for corporate accounting departments to efficiently and accurately process expenses not only for cash payments but also for cashless payments. However, there are cases where receipts are not issued for cashless payments. To prepare for such cases, companies that issue receipts provide a system that allows receipts to be issued from a web page. For example, a user who has stayed at a hotel can refer to their usage history on the hotel's web page and issue a receipt as an image.
[0003] Patent Document 1 describes a system that transmits payment data and receipt images together to an expense settlement service. By using this system, a user can upload an issued receipt image to a cashless service, which then appropriately links the payment data and receipt image and transmits them to the expense settlement service.
[0004] Patent Document 2 describes a system that embeds a character string including a file path of a printed matter into a two-dimensional code. Using this technology, a two-dimensional code with an embedded path of a receipt image can be created and displayed, and a multifunction device can read it and print a receipt image obtained from the path. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2021-196663 A [Patent Document 2] JP 2020-001253 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, since Patent Document 1 presupposes the existence of a receipt image, and Patent Document 2 presupposes the existence of an image to be printed, if there is no receipt image, the expense settlement service cannot be used and it cannot be output as a printed matter. For example, if a receipt is not issued for an expense paid through a cashless service, it is necessary to manually create a receipt image from a web page. Even if a receipt image has already been created, it is necessary to link the receipt image to the payment data of the cashless service. Thus, with conventional technology, printing a receipt image requires various efforts by the user, and there is a problem that printing for expense claims cannot be done efficiently.
[0007] SUMMARY OF THE PRESENT EMBODIMENT The present invention has been made in consideration of the above-mentioned conventional examples, and has an object to reduce the user's labor and efficiently print receipt images. [Means for solving the problem]
[0008] In order to achieve the above object, the present invention has the following configuration. That is, according to one aspect of the present invention, a list acquisition unit that acquires a data list from an external service; a determination means for determining whether an image is associated with data selected from the acquired data list; an acquisition means for acquiring an image to be associated with the selected data when it is determined that no image is associated with the selected data; a first storage means for storing the selected data and the acquired image in association with each other; A second storage means for generating and storing a two-dimensional code that encodes the storage destination of the image. The present invention provides an information processing apparatus comprising: Effect of the Invention
[0009] According to the present invention, it is possible to efficiently print receipt images while reducing the user's efforts. [Brief description of the drawings]
[0010] [Figure 1] Overall system diagram [Diagram 2] MFP hardware configuration diagram [Diagram 3] Client terminal hardware configuration diagram [Figure 4] Overall system software configuration diagram [Diagram 5] Flowchart showing the detailed process of creating a QR code [Figure 6] A diagram showing the client terminal screen [Figure 7] Sequence diagram showing the flow of printing processing [Figure 8] Flowchart showing the detailed process of creating a QR code DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.
[0012] Embodiment 1 [System Configuration] FIG. 1 shows the system configuration of an information processing system according to this embodiment. The client terminal 100 is a mobile terminal such as a smartphone or a tablet terminal. The MFP 110 is a multifunction device having multiple functions such as a scanner and a printer. The MFP 110 is also called an image forming device or a printing device. The cloud service 120 is a cashless service such as a mobile payment service. Although the term "service" is intangible, the term "service" used here includes servers that provide services using computers or information processing devices. Therefore, the cloud service 120 may also be called a cloud server 120.
[0013] 1, the client terminal 100 can refer to the usage history of the cloud service 120 and create a code, such as a QR code (registered trademark), that includes the storage destination of an image (receipt image) of a receipt (also called a receipt). The MFP 110 can obtain the receipt image from the client terminal 100 or the cloud service 120 and print the receipt by reading the QR code created by the client terminal 100.
[0014] In this embodiment, the client terminal 100 and the MFP 110 realize cooperation with the cloud service 120 by using an authentication and authorization mechanism such as OAuth.
[0015] The components in FIG. 1 are connected to each other via a network so that they can communicate with each other. For example, the network may be the Internet and an access line, such as a LAN, a WAN, or a telephone line. Alternatively, the network may be a communication network realized by a combination of these. Any network may be used as long as it is capable of transmitting and receiving data. The client terminal 100 and the MFP 110 are connected to, for example, a local area network (LAN) and can access the Internet via the LAN.
[0016] In this embodiment, a cashless service is given as an example of a cloud service, but the types of cloud services and the number of services that can be linked are not limited to those in this embodiment.
[0017] [Client terminal hardware configuration] 2 is a diagram showing the hardware configuration of the client terminal 100. The client terminal 100 includes a control unit 210 and an operation unit 220.
[0018] The control unit 210 includes the following units 211 to 215, and controls the operation of the entire client terminal 100. The CPU 211 reads out a program stored in the ROM 212 and executes various processes to control the operation of the entire terminal. The RAM 213 is used as a temporary storage area such as a main memory and a work area of the CPU 211. In this embodiment, one CPU 211 executes each process shown in a flowchart described later using one memory (RAM 213 or storage 214), but is not limited to this. For example, each process may be executed by cooperating multiple CPUs, multiple RAMs, or storages. The storage 214 is a large-capacity storage unit that stores image data and various programs. The network I / F 215 is an interface that connects the client terminal 100 to the Internet. The client terminal 100 communicates with other devices (such as the cloud service 120) via the network I / F 315, and transmits and receives various information.
[0019] The operation unit 220 includes a touch panel, and receives operations, inputs, or instructions from a user, and displays a screen according to the operations, inputs, or instructions.
[0020] [MFP hardware configuration] FIG. 3 is a hardware configuration diagram of the MFP 110. The MFP 110 includes a control unit 310, an operation unit 320, a printer unit 321, a scanner unit 322, a modem 323, and a QR code reader unit 324. The control unit 310 includes the following units 311 to 319, and controls the operation of the entire MFP 110. The CPU 311 reads out a program stored in the ROM 312, executes various functions of the MFP 110 such as image reading, printing, and communication, and controls the entire device. The RAM 313 is used as a temporary storage area such as the main memory and work area of the CPU 311. Note that in this embodiment, one CPU 311 executes each process shown in the flowchart described later using one memory (RAM 313 or storage 314), but is not limited to this. For example, each process may be executed by cooperating multiple CPUs and multiple RAMs or storages. The storage 314 is a large-capacity storage unit that stores image data and various programs. The network I / F 315 is an interface that connects the control unit 310 (MFP 110) to a LAN. The MFP 110 communicates with other devices (such as the cloud service 120) via the network I / F 315 to transmit and receive various types of information.
[0021] The operation unit 320 is equipped with a touch panel, buttons, etc., and accepts operations, inputs, or instructions from the user. The printer unit 321 prints image data for printing transferred from the control unit 310 onto a recording medium. The scanner unit 322 reads an original placed on a platen or an Auto Document Feeder, generates image data, and inputs the image data to the control unit 310. The MFP 110 can print (copy) the image data generated by the scanner unit 322 from the printer unit 331, as well as transmit the image data as a file or by e-mail. The modem 323 communicates image data by facsimile with a facsimile device on the PSTN.
[0022] The QR code reader 324 reads various text data included in the QR code and inputs it to the control unit 310. In this embodiment, the storage destination of the receipt image and the like are obtained based on the text data extracted by the QR code reader 324 of the MFP 110, the receipt image is downloaded from the client terminal 100 or cloud service 120 via the network I / F 315, and the receipt image is printed. Note that if the QR code reader is realized by software, the QR code reader 324 does not need to be provided as hardware.
[0023] [System-wide software configuration] 4 is a diagram showing the software configuration of the entire system according to this embodiment. The client terminal 100 has a request control unit 401, an image creation unit 402, a QR code generation unit 403, a data management unit 404, and a display control unit 405.
[0024] The request control unit 401 requests the cloud service 120 for various processes. For example, it requests logging in to the service and acquiring payment data. The payment data includes various information such as the issuer of the receipt, the date, the amount, the destination where the receipt image is saved, and the destination where the thumbnail image is saved. Note that if the receipt image is not linked to the payment data, the payment data does not include information related to images such as the destination where the receipt image is saved or the thumbnail image is saved. Protocols such as REST and SOAP are used for communication with the cloud service 120, but other communication means may also be used.
[0025] The image creation unit 402 creates a receipt image based on the issuer, date, amount, etc. of the receipt included in the payment data. In this embodiment, the client terminal 100 acquires a thumbnail image from the cloud service 120, but the method of acquiring the thumbnail image is not limited to this. For example, the request control unit 401 of the client terminal 100 may download a receipt image from the cloud service 120, and the image creation unit 402 of the client terminal 100 may generate a thumbnail image. Alternatively, the thumbnail image may be created based on the receipt image created by the image creation unit 402.
[0026] The QR code generation unit 403 creates a QR code that stores the receipt image storage destination, print settings, etc. The receipt image storage destination includes either the storage destination of the receipt image acquired by the request control unit 401 from the cloud service 120, or the storage destination of the receipt image created by the image creation unit 402. The print settings include general settings for printing on paper (color / monochrome, single-sided / double-sided, etc.).
[0027] The data management unit 404 stores in the storage 214 the receipt image created by the image creation unit 402, connection information for the cloud service 120 to which the client terminal 100 connects, temporary data used in various processes, and the like.
[0028] The display control unit 405 receives a request from an application running on the client terminal 100 and returns screen configuration information required for screen display. When the user operates the application screen (FIG. 6) and selects payment data for the cloud service 120, a QR code 613 storing that information and a thumbnail image 611 of the receipt are displayed. In addition, when payment data is selected, a receipt image can be uploaded to the cloud service 120 by pressing a receipt registration button 603 on the payment data list screen 600. This makes it possible to link and manage the payment data and the receipt image. In addition, print settings can be set via the UI screen (display control unit 404).
[0029] The MFP 110 includes a request control unit 411 , a QR code reading unit 412 , a data management unit 413 , a display control unit 414 , and a print control unit 415 .
[0030] The request control unit 411 requests various processes to the client terminal 100 and the cloud service 120. For example, it requests to log in to a service, download an image of a receipt, etc. Protocols such as REST and SOAP are used for communication with the client terminal 100 and the cloud service 120, but other communication means may also be used.
[0031] The QR code reading unit 412 analyzes the QR code and reads the storage destination and print settings of the receipt image contained in the QR code. More specifically, the QR code reading unit 412 extracts various text data contained in the optically read QR code and inputs it to the control unit 310. In this embodiment, the QR code reading unit 412 of the MFP 110 acquires the storage destination and print settings of the receipt image based on the text data extracted by the QR code reading unit 412. Furthermore, the receipt image is downloaded from the acquired storage destination, such as the client terminal 100 or cloud service 120, via the network I / F 315, and the receipt image is printed. The QR code reading unit 412 may be realized by hardware.
[0032] The data management unit 413 stores image data such as receipt images downloaded from the client terminal 100 or the cloud service 120 in the storage 314 .
[0033] A display control unit 414 displays the progress of the printing process on a liquid crystal display unit having a touch panel function of the operation unit 220 of the MFP 110, and displays a user interface (UI) screen for receiving operations by the user.
[0034] The print control unit 415 automatically prints the receipt image downloaded by the QR code reading unit 412 reading the QR code. In this embodiment, printing is started by setting print settings on the client terminal 100 and reading the QR code, but the printing method is not limited to this. For example, the print process may be executed by receiving instructions such as input of authentication information for accessing the cloud service 120, print settings, and an operation to start printing via the UI screen (display control unit 414) of the MFP 110.
[0035] The cloud service 120 includes a request control unit 421 , a data management unit 422 , and a display control unit 423 .
[0036] Request control unit 421 executes processing in response to a processing request from client terminal 100 or MFP 110, such as a payment data acquisition request, as appropriate, and responds with the result of the processing request.
[0037] Data management unit 422 holds image data of receipts and payment data stored in cloud service 130. These data may be stored in association with a user. For example, when cloud service 120 receives a download request for a receipt image from MFP 110, request control unit 421 acquires the specified receipt image from data management unit 422 and responds as the result of the processing request. Similarly, when cloud service 120 receives a request to acquire payment data, request control unit 421 acquires the specified payment data of the receipt from data management unit 422 and responds as the result of the processing request.
[0038] The display control unit 423 receives a request from a web browser running on the client terminal 100 and returns screen configuration information (HTML, CSS, etc.) required for screen display. The user can refer to image data, payment data, etc. stored in the cloud service 130 via the screen displayed by the web browser.
[0039] [Details of the MFP Collaboration Service Processing in the First Embodiment] Fig. 5 is a flowchart showing details of the process in which client terminal 100 creates a QR code. This QR code is used in the receipt printing process in the sequence in Fig. 7, and the details of the sequence will be described later. Note that the series of processes in this flowchart are realized by CPU 211 in control unit 210 of client terminal 100 executing a control program stored in storage 214. A detailed description will be given below.
[0040] In this embodiment, the process starts when the display control unit 404 of the client terminal 100 detects that an operation to display a list of payment data of the cloud service 120 has been accepted.
[0041] In S501, the request control unit 401 of the client terminal 100 sends a request to acquire a payment data list to the cloud service 120. The payment data includes the issuer of the receipt, the date, the amount, and the like. In response to the request to acquire the payment data list, the cloud service 120 sends the payment data list to the requester. When the payment data list is acquired, it is displayed as a payment data list 601 on the payment data list screen 600 in FIG. 6. The payment data list to be acquired may be, for example, a payment data list of transactions settled by a user logged in to the client terminal 100. In this case, the request to acquire the payment data list also includes the identification information of the user. For each payment, the payment data list includes a name related to the payment, such as the name of the issuer of the receipt, and link information to a receipt image linked to the payment data. For payment data that does not have an associated receipt image, link information to the receipt image may not be included.
[0042] In S502, the display control unit 404 of the client terminal 100 determines whether any payment data in the payment data list 601 on the payment data list screen 600 has been selected and the Next button 602 has been pressed. If the Next button has been pressed, the process proceeds to S503, and if the Next button has not been pressed, the process proceeds to S502 again.
[0043] In S503, the request control unit 401 of the client terminal 100 determines whether a receipt image is linked to the selected payment data. If a receipt image is linked, the process proceeds to S506, and if a receipt image is not linked, the process proceeds to S504.
[0044] In S504, the display control unit 404 of the client terminal 100 displays a message screen 620 for selecting how to link a receipt image to payment data. The message screen 620 includes, for example, payment data 623, a button 621 for instructing image generation, and a button 622 for instructing image upload. If "Generate receipt image from payment data" 621 is selected, the process proceeds to S505, and if "Upload receipt image to cloud service 120" 622 is selected, the process proceeds to S506.
[0045] In S505, the image creation unit 402 of the client terminal 100 creates a receipt image from the payment data. For example, the receipt image is created based on the issuer, date, amount, etc. included in the payment data, and is saved in the data management unit 403. The receipt image may be generated by applying the issuer, date, amount, etc. to a template. The template to be used may be selected from multiple candidates, or may be a predetermined template. The created receipt image may be linked to the payment data and saved in the client terminal 100. The saved destination is used in step S507.
[0046] In S506, the display control unit 404 of the client terminal 100 displays a UI for uploading a receipt image to the cloud service 120, and determines whether or not an upload operation has been accepted. If an upload operation has been accepted, the process proceeds to S507. If an upload operation has not been accepted (if the operation has been cancelled), the process proceeds to S502. When a user uploads a receipt image to the cloud service 120, the request control unit 401 transmits a receipt image upload request to the cloud service 120. In response to this upload request, the client terminal 100 can obtain a storage destination for the receipt image from the cloud service 120 after uploading the receipt image. The receipt image may be, for example, an image of a receipt created by the client terminal 100 using an accounting application or service of an external service. Alternatively, for a transaction in which a receipt has already been issued on paper, an image of the paper receipt may be uploaded in order to digitize the receipt.
[0047] In S507, the QR code creation unit 402 of the client terminal 100 creates a QR code that stores the storage destination and print settings of the receipt image. This QR code contains the encoded storage destination and print settings. In this embodiment, the storage destination of the receipt image differs depending on the executed process. For example, the storage destination of the receipt image obtained from the cloud service 120 or uploaded to the cloud service 120 in the process of S501, S502, or S506 is one of the directories of the cloud service 120. On the other hand, the storage destination of the receipt image obtained in the process of S505 is one of the directories of the client terminal 100. The created QR code is stored in association with the payment data.
[0048] The saved QR code can be read and displayed on the client terminal 100, for example, as shown on a display screen 610 in Fig. 6. By saving the display screen 610 as an image, the saved display screen 610 can be displayed, for example, using an application for displaying images.
[0049] In addition, the print settings included in the QR code include, for example, general settings when printing on paper (color / monochrome, single-sided / double-sided, etc.), and these settings can be set on a UI (not shown) of the client terminal 100.
[0050] The above describes the method for creating a QR code that includes information about a receipt image. In this embodiment, the receipt image created in step S505 is stored in the client terminal 100, but the receipt image created in the client terminal 100 may be uploaded to the cloud service 120 or an external cloud storage service.
[0051] [Processing flow between devices in embodiment 1] 7 is a sequence diagram showing the flow of processing between each device when a receipt image is printed by the MFP 110. Here, the explanation will be centered on the exchange between each device. This processing is started when the QR code reading unit 412 of the MFP 110 reads the QR code 612 displayed on the UI screen (QR code display screen 610) of the client terminal 100. This reading may be started, for example, when the user touches a read instruction button on the UI provided by the QR code reading unit 412. In the following explanation, the processing by each device is performed by a software module of the device. However, since the software module is realized by executing a program by the CPU of each device, the execution entity may be considered to be the CPU of each device.
[0052] In S701, the QR code reading unit 412 of the MFP 110 reads and acquires the QR code 612 displayed on the UI screen (QR code display screen 610) of the client terminal 100 with the scanner unit 321.
[0053] In S702, the QR code reading unit 412 of the MFP 110 analyzes the character string stored in the acquired QR code 612. For example, information obtained by the analysis includes the save destination and print settings of the receipt image.
[0054] In S703 and S704, the request control unit 411 of the MFP 110 specifies the storage destination of the receipt image acquired in S702 based on the analysis result and sends a request for downloading the image. If the receipt image was created in step S505, the storage destination is the client terminal 100. On the other hand, if the receipt image is linked to the payment data and stored in the cloud service 120, or if it is uploaded from the client terminal 100, the storage destination is the cloud service 120.
[0055] In step S703, if the receipt image is to be saved in the client terminal 100, the MFP 110 transmits a request to the client terminal 100 to download the image.
[0056] In step S704, if the receipt image is to be saved in the cloud service 120, the MFP 110 transmits a request to the cloud service 120 to download the image.
[0057] After transmitting the request according to the storage destination of the receipt image, the MFP 110 temporarily stores the image received from the cloud service 120 in the data management unit 413 .
[0058] In S705, the print control unit 415 of the MFP 110 prints the receipt image stored in the data management unit 413.
[0059] The above describes a printing method using a QR code. Conventional methods require a lot of work to print a receipt image, but the method of this embodiment makes it possible to print receipts in a simple manner. This makes it possible to efficiently print receipts for expense claims, for example.
[0060] Embodiment 2 [Details of the MFP Collaboration Service Processing in the Second Embodiment] In the above-mentioned embodiment 1 (FIG. 5), the receipt image was created on the client terminal 100, but the method of creating the receipt image is not limited to this. For example, if the receipt image can be created on an external system instead of the client terminal 100, it is possible to create the receipt image on the external system. Therefore, in embodiment 2 (FIG. 8), a method of creating the receipt image on an external system will be described. In this embodiment, the same explanation as in embodiment 1, such as the system configuration and application UI, will be omitted.
[0061] Fig. 8 is a flowchart showing details of the process in which client terminal 100 creates a QR code. This QR code is used in the receipt printing process in the sequence of Fig. 8, and the details of the sequence will be described later. Note that the series of processes in this flowchart are realized by CPU 211 in control unit 210 of client terminal 100 executing a control program stored in storage 214. A detailed description will be given below.
[0062] In this embodiment, the process starts when the display control unit 404 of the client terminal 100 detects that an operation to display a list of payment data of the cloud service 120 has been accepted.
[0063] In S805, the request control unit 401 of the client terminal 100 sends a request to create a receipt image to an external system such as the cloud service 120 or an external receipt image creation service together with the settlement data selected on the payment data list screen 600. The client terminal 100 receives the receipt image created by the external system as a response and stores it in the data management unit 403. In this embodiment, the data management unit 403 of the client terminal 100 is specified as the storage destination of the receipt image, but the acquired receipt image may be stored in another location, such as an arbitrary storage service. In addition, if the external system that created the receipt image also provides a function for saving image data, the receipt image does not need to be acquired by the client terminal 100. If the receipt image is saved in a location other than the client terminal 100, the storage destination of the receipt image stored in the QR code is the storage destination of the receipt image on the storage service or external system.
[0064] The above describes a method for creating a QR code that includes information about a receipt image. This allows the MFP 110 to obtain a receipt image from an external system, which makes it possible to efficiently print the receipt image.
[0065] In this embodiment, the client terminal 100 receives the receipt image created by the external system as a response (FIG. 8), and the MFP 110 further acquires the receipt image from the client terminal 100 (FIG. 7), resulting in two image data acquisition processes. Since it is not an efficient process to propagate the same receipt image through multiple systems, this problem may be solved by storing other information in the QR code instead of the receipt image storage destination. For example, a request to create a receipt image for the external system may be stored in the QR code, and the MFP 110 may read the QR code and execute a request to create a receipt image for the external system. This eliminates the need for the client terminal 100 to acquire the receipt image from the external system, and further enables the MFP 110 to acquire the receipt image directly from the external system, thereby realizing an efficient receipt image acquisition process.
[0066] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.
[0067] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention.
[0068] Summary of embodiments The above embodiments can be summarized as follows: (Item 1) A list acquisition means for acquiring a data list from an external service; a determination means for determining whether an image is associated with data selected from the acquired data list; an acquisition means for acquiring an image to be associated with the selected data when it is determined that no image is associated with the selected data; a first storage means for storing the selected data and the acquired image in association with each other; A second storage means for generating and storing a two-dimensional code that encodes the storage destination of the image. 23. An information processing apparatus comprising: (Item 2) Item 1. The information processing device according to item 1, The device further includes an output means for outputting the two-dimensional code stored by the second storage means as an image. 23. An information processing apparatus comprising: (Item 3) 3. The information processing device according to item 1 or 2, The acquisition means includes a generation means for generating the image in response to an instruction for image generation. 23. An information processing apparatus comprising: (Item 4) Item 3. The information processing device according to item 3, The generating means applies the data to a template to generate the image. 23. An information processing apparatus comprising: (Item 5) An information processing device according to any one of items 1 to 4, The acquiring means causes an external system to generate the image in response to an instruction to generate the image, and acquires the generated image. 23. An information processing apparatus comprising: (Item 6) 6. The information processing device according to any one of items 1 to 5, The acquiring means acquires an image in response to an upload instruction and uploads the image to the external service. 23. An information processing apparatus comprising: (Item 7) Item 6. The information processing device according to item 6, The acquiring means uploads an image generated by an external system. 23. An information processing apparatus comprising: (Item 8) 8. The information processing device according to any one of items 1 to 7, When it is determined that an image is associated with the selected data, the second storage means generates a two-dimensional code that encodes a storage destination of the image and stores the code. 23. An information processing apparatus comprising: (Item 9) Item 10. An information processing device according to any one of items 1 to 8, The data is payment data, and the image is a receipt image related to the payment data. 23. An information processing apparatus comprising: (Item 10) 10. A program for causing a computer to function as the information processing device according to any one of items 1 to 9. [Explanation of symbols]
[0069] 100 client terminal, 110 MFP, 120 cloud service, 411 request control unit, 412 QR code reader
Claims
1. A list acquisition means for acquiring a data list from an external service; a determination means for determining whether an image is associated with data selected from the acquired data list; an acquisition means for acquiring an image to be associated with the selected data when it is determined that no image is associated with the selected data; a first storage means for storing the selected data and the acquired image in association with each other; and a second storage means for generating and storing a two-dimensional code that encodes a storage destination of the image.
23. An information processing apparatus comprising:
2. 2. The information processing device according to claim 1, The apparatus further includes an output means for outputting the two-dimensional code stored by the second storage means as an image.
23. An information processing apparatus comprising:
3. 2. The information processing device according to claim 1, The acquisition means includes a generation means for generating the image in response to an instruction for image generation.
23. An information processing apparatus comprising:
4. 4. The information processing device according to claim 3, The generating means applies the data to a template to generate the image.
23. An information processing apparatus comprising:
5. 2. The information processing device according to claim 1, The acquiring means causes an external system to generate the image in response to an instruction to generate the image, and acquires the generated image.
23. An information processing apparatus comprising:
6. 2. The information processing device according to claim 1, The acquiring means acquires an image in response to an upload instruction and uploads the image to the external service.
23. An information processing apparatus comprising:
7. 7. The information processing device according to claim 6, The acquiring means uploads an image generated by an external system.
23. An information processing apparatus comprising:
8. 2. The information processing device according to claim 1, When it is determined that an image is associated with the selected data, the second storage means generates a two-dimensional code encoding a storage destination of the image and stores the two-dimensional code.
23. An information processing apparatus comprising:
9. 2. The information processing device according to claim 1, The data is payment data, and the image is a receipt image related to the payment data.
23. An information processing apparatus comprising:
10. A program for causing a computer to function as the information processing device according to any one of claims 1 to 9.
11. The information processing device according to claim 2 ; a printing device that reads the output two-dimensional code, acquires the image from the storage location of the image, and prints the acquired image. An information processing system comprising:
Citation Information
Patent Citations
Document management system
JP2005165795A
Evidence document issue device and database creation device for evidence document information
JP2006209588A
Electronic data issuing program, computer system, method and computer
JP2006227748A
Information processor, information processing method, and program
JP2014038561A
Accounting information processor, accounting information processing method, and program
JP2015210766A
