Signature Systems and Programs

Abstract

To provide a technology for improving a signature flow when exchanging a digital document to be signed is exchanged between a plurality of persons.SOLUTION: A signature system 1 includes an applicant device 10 and an approver device 30. An approval application 21 is installed on the applicant device 10. An applicant edits and generates, using the approval application 21, an expense report 80 including a signature field 85 and a QR code 86 for starting an approval mini application 31, and prints the report using a printer 40. An approver who receives the printed expense report 80 uses the approver device 30 to scan the QR code 86 of the expense report 80, thereby downloading the approval mini application 31 from an external server 70 to start the application. The approver uses the approval mini application 31 to execute processing for electronic signature on the expense report 80.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to a signature system for signing documents and a program used in the system. [Background technology]

[0002] Conventionally, there has been known a technology for electronically signing digital documents instead of signing paper documents by stamping them with a seal, etc. For example, Patent Document 1 discloses a system for electronically stamping digital documents and exchanging the stamped digital documents among multiple people, in which image information of the seal impression is stored in advance in a server device, and when the seal impression is to be displayed on digital data, the image information of the seal impression is downloaded from the server device and added to a specified position in the digital data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-352863 Summary of the Invention [Problem to be solved by the invention]

[0004] When digital documents requiring signatures are exchanged between multiple people, some signers may not be able to follow the signature flow, which is the entire process of electronic signatures. For example, when signing between different companies or organizations, some signers may not have the software installed to support the signature flow, or may have installation restrictions. In this case, the process may have to be abandoned, and the digital document may have to be printed out on paper, signed, and then digitized again after signing, which is a time-consuming process.

[0005] This specification discloses a technique for improving the signature flow when a digital document requiring signatures is exchanged between multiple people. [Means for solving the problem]

[0006] A signature system that has been made to solve the above-mentioned problems includes a first device that is an applicant device and a second device that is an approval device, a full application executable by a computer of the first device is installed on the first device, the full application being a program corresponding to a signature flow; The second device does not have the full app installed; The first device When the full app receives a print instruction for a digital document to be signed, the full app causes a printer to print the digital document, a signature field, and a mark for activating a mini app, wherein identification information for the digital document is printed on the printout of the digital document and information identifying the signer is printed on the printout of the signature field, the mini app is a program that provides some of the functions of the full app, does not require installation, and is deleted from the device onto which it is downloaded after a predetermined period of time has passed, and the mark for activating the mini app includes access information used to download the mini app; Furthermore, the first device When the print instruction is received, the full app uploads electronic data corresponding to the digital document to a server and stores it in the server, and the electronic data stored in the server includes identification information of the digital document and signature information indicating the signer and signature status of the digital document; The second device The mark printed by the first device is read, the access information included in the mark is used to download the mini app, and the downloaded mini app is launched, and the mini app is executed by the mini app. Identifying a user of the second device; reading the digital document printed by the first device and determining identification information of the digital document; reading the signature line printed by the first device to identify a signer of the digital document; determining whether approval of the user of the identified second device is required based on the identified signer of the digital document and the signature information included in the electronic data stored in the server that corresponds to identification information of the identified digital document; If it is determined that approval from the user of the second device is required, a signature from the user of the second device is requested, and if a digital signature is provided, the server is accessed and the signature information contained in the electronic data corresponding to the identification information of the identified digital document is updated.

[0007] According to the above configuration, the second device on the approving side signs the document using a mini-app that does not need to be installed. Therefore, signing can be performed even on a device that does not have the full app installed or where the device's usage permissions restrict installation of the full app.

[0008] The program for realizing the functions of the above device is also novel and useful. [Effects of the Invention]

[0009] The technology disclosed in this specification realizes a technology that improves the signature flow when a digital document requiring signatures is exchanged between multiple people. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is an explanatory diagram showing a schematic configuration of a signature system according to an embodiment; [Figure 2] FIG. 2 is an explanatory diagram showing the schematic configuration of an expense report. [Figure 3] FIG. 2 is an explanatory diagram showing a schematic configuration of an applicant device. [Figure 4]FIG. 2 is an explanatory diagram showing a schematic configuration of an approver device. [Figure 5] FIG. 2 is an explanatory diagram illustrating a schematic configuration of a management device. [Figure 6] FIG. 10 is a sequence diagram showing the procedure of an approval process. [Figure 7] FIG. 10 is a sequence diagram showing the procedure of an approval process. [Figure 8] FIG. 10 is an explanatory diagram showing a state in which a signature and seal section of an expense report is photographed using the camera of the approver device and displayed in AR. DETAILED DESCRIPTION OF THE INVENTION

[0011] A specific embodiment of the signature system according to the present invention will be described in detail below with reference to the drawings. Fig. 1 is an explanatory diagram showing the schematic configuration of the signature system according to the present embodiment.

[0012] That is, the signature system 1 is composed of an applicant device 10, an approver device 30, a printing device 40, and a management device 50. The applicant device 10 and the approver device 30 are composed of smartphones or the like. Furthermore, the applicant device 10 and the approver device 30 may be composed of, for example, a tablet computer or a desktop computer instead of a smartphone or the like. Furthermore, the approver device 30 may be composed of multiple devices depending on the number of approvers.

[0013] The applicant device 10, the approver device 30, the printing device 40, and the management device 50 can communicate with each other via an access point 61 of a local area network 60. The local area network 60 is also connected to an external server 70 via an Internet line 62. Note that multiple access points 61 of the local area network 60 may be installed as necessary. The management device 50 may also be connected via the Internet line 62. If at least one approver belongs to another organization, for example, another company, the approver device 30 of that approver may be configured to be connectable to the local area network 60 via an access point (not shown) of the company's local area network and the Internet line 62.

[0014] As will be described later, the applicant device 10, the approver device 30, the printing device 40, and the management device 50 may communicate directly with each other without going through the access point 61 of the local area network 60. The communication method is not limited to a wireless method and may be a wired method. The applicant device 10 is an example of a first device, the approver device 30 is an example of a second device, and the printing device 40 is an example of a printer.

[0015] The signature system 1 of this embodiment can perform a series of approval procedures, for example, for approving expense report 80 shown in Fig. 2, regardless of the signature method used by the approver, such as an electronic signature or a seal on a paper document. Note that the signature system 1 of this embodiment is not limited to approval procedures for expense report 80, but can be applied to any approval procedures, such as approval procedures for contracts related to the purchase of goods or for contracts related to joint development.

[0016] Expense report 80 has a number entry field 81, an applicant information entry field 82, a department information entry field 83, an expense entry field 84, a signature and seal field 85, and a QR code (registered trademark) 86. Furthermore, signature and seal field 85 has an applicant signature field 851, a signature and seal field for the primary approver 852, and a signature and seal field for the secondary approver 853. Note that expense report 80 is an example of a digital document, signature and seal field 85 is an example of a signature field, and QR code 86 is an example of a mark.

[0017] The number entry field 81 contains a statement number assigned to each expense report 80 in order to identify the expense report 80. The statement number is an example of identification information. The applicant information entry field 82 contains information about the applicant who is applying for the expense report 80. The department information entry field 83 contains information about the department to which the applicant belongs. The expense entry field 84 contains expenses related to the application. The applicant signature field 851 of the signature and seal field 85 contains the name of the applicant and the applicant's electronic signature. The primary approver signature and seal field 852 contains the name of the primary approver and the primary approver's seal or electronic signature. The secondary approver signature and seal field 853 contains the name of the secondary approver and the secondary approver's seal or electronic signature. The QR code 86 stores launch information for the approval mini app 31, which will be described later. The launch information also includes access information for the download source of the approved mini application 31, such as a URL (Uniform Resource Locator).

[0018] FIG. 3 is an explanatory diagram showing the schematic configuration of an applicant device. In the figure, the applicant device 10 has a control unit 11. The control unit 11 is responsible for central control of the applicant device 10. The control unit 11 includes a CPU 12, a ROM 13, and a RAM 14. The CPU 12 is a central processing unit that executes various control programs and is an example of a computer. The ROM 13 stores various control programs executed by the CPU 12 and permanent data. The RAM 14 temporarily stores the results of calculations performed by the CPU 12 based on the control programs. Note that the control unit 11 in FIG. 3 is a collective term for hardware and software used to control the applicant device 10, and does not necessarily represent a single piece of hardware actually present in the applicant device 10.

[0019] The applicant device 10 also has a communication interface (hereinafter referred to as "communication IF") 15, a camera 16, a user interface (hereinafter referred to as "user IF") 17, a GPS receiver 18, and the like.

[0020] The communication IF 15 includes hardware for communicating with devices such as the printing device 40 and the management device 50 via an access point 61 of the local area network 60. The communication method of the communication IF 15 may be wireless or wired, and may be any standard method such as Wi-Fi (registered trademark) or LAN. The communication IF 15 may also have a function for directly connecting to devices such as the printing device 40 and the management device 50 without going through the access point 61, such as Bluetooth (registered trademark) or USB.

[0021] Camera 16 is connected to control unit 11 and is capable of capturing an image of any subject. Camera 16 includes hardware with an imaging function and may be incorporated into the main body of applicant device 10, or may be a separate device connectable to applicant device 10.

[0022] The user IF 17 is configured with a touch panel having both a display function and an operation reception function, and is connected to the control unit 11. The user IF 17 is an example of a display unit and an example of an input interface. The user IF 17 may include a combination of a display, such as a liquid crystal display or an organic EL display, that displays information, and a keyboard, mouse, or the like that receives input operations by the user.

[0023] The GPS receiver 18 receives signals from satellites and provides functions such as detecting the current location of the applicant device 10 and obtaining accurate time information. Note that "GPS" is an abbreviation for "Global Positioning System."

[0024] The applicant device 10 also has a storage device 19. For example, a semiconductor memory such as a flash memory or an HDD (Hard Disk Drive) can be used as the storage device 19. The storage device 19 stores an operating system (hereinafter referred to as "OS") 20, an approval application program (hereinafter referred to as "approval app") 21, a payment application program (hereinafter referred to as "payment app") 22, etc.

[0025] The OS 20 is iOS (registered trademark), but may also be any of Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), and Android (registered trademark), for example.

[0026] The approval application 21 can be used by being downloaded and installed from an external server 70 via an internet connection, for example. Note that the download may be from the management device 50 instead of the external server 70.

[0027] The approval application 21 is a program that allows an applicant to create various approval forms, specifically, for example, an expense report 80, via the user IF 17. That is, the approval application 21 receives instructions from the applicant, such as for creating, editing, and printing the expense report 80, and displays the expense report 80 on the user IF 17 and sends a print job to the printing device 40 based on the received instructions.

[0028] Furthermore, when the approval application 21 prints the expense report 80 using the printing device 40, it prints a QR code 86 on the expense report 80. The QR code 86 contains launch information for the approval mini application 31, which is a mini application corresponding to the approval application 21, and the launch information contains access information for the download source of the approval mini application 31. Details of the mini application will be described later.

[0029] Furthermore, when the applicant uses the approval application 21 to create the expense report 80, the applicant may download a template for the expense report 80 from the management device 50 and then add or modify the necessary items to the downloaded template expense report 80 to create the expense report 80. Furthermore, the approval application 21 can accept instructions from the applicant and select the printing device 40 that will execute printing.

[0030] The approval application 21 is a program for providing the applicant with a series of approval procedures (signature flow) for the expense report 80. That is, the approval application 21 authenticates the approver, determines the approver's authority, and updates the approver's electronic signature or seal information. The approval application 21 also includes an Optical Character Recognition function (hereinafter referred to as "OCR function"). The OCR function is a function that extracts characters from image data and generates character information indicating the extracted characters.

[0031] The payment application 22 provides the user with so-called electronic payment services. That is, the payment application 22 has a function of performing payment processing for the amount indicated in a payment instruction in response to the receipt of the payment instruction.

[0032] 4 is an explanatory diagram showing the schematic configuration of the approver device 30. That is, the approver device 30 has almost the same configuration as the applicant device 10, and components that perform the same functions are assigned the same reference numerals and their explanations are omitted.

[0033] That is, the major difference in configuration between the approver device 30 and the applicant device 10 is that in the applicant device 10, the approval app 21 is installed in the storage device 19, whereas in the approver device 30, the approval mini-app 31 is stored in the storage device 19.

[0034] The approved mini app 31 is a mini app that has some of the functions of the approved app 21 and is software that provides a user with some of the functions of the approved app 21 in a simplified manner. A "mini app" is an application program that has some of the functions of an application program (also called a "full app") that requires installation on a device, but does not require installation on the device. Because installation is not required, even devices that restrict program installation can run the mini app. A mini app is a smaller program than a full app and can be downloaded in a short time. After being downloaded, a mini app is automatically deleted by the OS, for example, after a predetermined time has passed, so it places a small load on memory. Furthermore, information entered into a mini app does not remain in memory when the mini app is deleted, providing a high level of security. By downloading a mini app when necessary, a user can use some of the functions of a full app without having to download and install the full app.

[0035] Examples of mini-applis include AppClip (a program executed on iOS) by Apple (registered trademark) and InstantApps (a program executed on Android) by Google (registered trademark). In this embodiment, the approval app 21 is an example of a full app, and the approval mini-app 31 is an example of a mini-app corresponding to the approval app 21. Specifically, the approval mini-app 31 in this embodiment has, among the functions of the approval app 21, which is a full app, a function for providing the user with a series of approval procedures (signature flow) for the expense report 80 and an OCR function.

[0036] As described above, the approval mini app 31 can be used without being installed in the approver device 30. That is, when the approval mini app 31 is downloaded to the storage device 19 of the approver device 30, the control unit 11 executes the approval mini app 31 in response to a user operation. This allows the user (the approver) to try out the approval mini app 31 before installing the approval app 21, which is a full app, and to decide whether or not to download the approval app 21 based on the trial results. Note that when the approval app 21 is installed with the approval mini app 31 already stored, the previously stored approval mini app 31 is either incorporated into the approval app 21 as is, or deleted and replaced with the approval mini app 31 included in the approval app 21. Furthermore, the OS 20 automatically deletes the approval mini app 31 from the storage device 19 of the approver device 30 a predetermined time after it is downloaded.

[0037] The approval mini-app 31 can be used by being downloaded from an external server 70 via an internet connection, for example. Note that the download may be from the management device 50 instead of the external server 70.

[0038] In this embodiment, the QR code 86 printed on the expense report 80 is read by the camera 16, and the external server 70 from which the approval mini app 31 is downloaded is accessed based on the access information included in the startup information.

[0039] The printing device 40 shown in FIG. 1 is a multifunction peripheral equipped with a printing unit and a reading unit (neither of which are shown), and is connected to an access point 61 of a local area network 60 via its communication interface (not shown).

[0040] 1 is a server known as an XXX store, from which software can be downloaded for free or for a fee. In this embodiment, the applicant device 10 can download the approval application 21, and the approver device 30 can download the approval mini application 31. Note that the approver device 30 may be configured to be able to download the approval application 21.

[0041] 5 is an explanatory diagram showing a schematic configuration of a management device 50. That is, the management device 50 includes a control unit 51, a storage unit 52, an input interface (hereinafter referred to as "input IF") 53, a display interface (hereinafter referred to as "display IF") 54, and a communication interface (hereinafter referred to as "communication IF") 55.

[0042] The control unit 51 includes, for example, a CPU. The storage unit 52 includes, for example, a ROM, a RAM, an NVRAM, a HDD (Hard Disk Drive), or an SSD (Solid State Drive). That is, the management device 50 of this embodiment includes a microcomputer including a CPU and a semiconductor memory.

[0043] The control unit 51 realizes various functions by executing programs stored in the storage unit 52. Note that the various functions realized by the control unit 51 are not limited to being realized by executing programs (i.e., by software processing), and some or all of the functions may be realized using one or more pieces of hardware.

[0044] Various software and data are stored in the storage unit 52. In this embodiment, the software stored in the storage unit 52 is an OS 56 and user management software 57. The OS 56 and the user management software 57 are executed by a computer system including the control unit 51 to realize various functions.

[0045] In this embodiment, the storage unit 52 further stores a user database 58. The user database 58 stores template information 581, which is template data for an expense report 80, approver information 582 related to the applicant of the expense report 80, and application form information 583, which stores each expense report 80 applied for by the applicant. The approver information 582 can be searched based on information about the organization to which the applicant belongs. The approver information 582 also includes electronic certification information for the approver. The application form information 583 can also be used to search for expense reports 80 based on the statement number entered in the number entry field 81 of the expense report 80. The user database 58 is managed by the user management software 57 and is referenced, updated, added, and the like.

[0046] Next, the approval process (signature flow) executed by the applicant device 10 and the approver device 30 in the signature system 1 of this embodiment will be described in detail with reference to the sequence diagrams of the approval process shown in FIGS. 6 and 7. The approval process is performed by the CPU 12 of the applicant device 10 executing the approval application 21 and the CPU 12 of the approver device 30 executing the approval mini-application 31. This specification will omit the description of the OS 20 to describe the operation of each program. In other words, in the following description, a statement to the effect that "program B controls hardware C" may also mean that "program B controls hardware C using the API of the OS 41." Furthermore, the processing of the CPU 12 in accordance with instructions written in a program may be described in abbreviated terms. For example, it may be described as "performed by the CPU" or "performed by the program."

[0047] First, in FIG. 6, the applicant starts the approval application 21 on the applicant device 10, and then taps the user IF 17 of the applicant device 10 to instruct the creation of the expense report 80 (step 10 (hereinafter referred to as "T10")). The approval application 21 then accesses the management device 50, downloads template information 581, which is template data for the expense report 80 stored in the user database 58, and stores the template information 581 in the storage device 19 or RAM 14.

[0048] If the approval application 21 is not installed in the applicant device 10, the applicant can download the approval application 21 from the external server 70 via the Internet line 62. The approval application 21 may also be downloaded from the management device 50.

[0049] Next, the approval application 21 displays the downloaded template of the expense report 80 on the user IF 17 of the applicant device 10 and accepts editing by the applicant (T11). Accordingly, the applicant enters the required information in the applicant information entry field 82, department information entry field 83, and expense entry field 84 of the expense report 80 via the user IF 17. The applicant also performs electronic approval processing in the applicant signature field 851 of the expense report 80.

[0050] Next, when the applicant taps the user IF 17 of the applicant device 10 to instruct printing of the expense report 80 for which editing has been completed (T12), the approval application 21 accesses the management device 50, downloads information regarding the statement number, applicant, approver, and QR code 86 from the management device 50, and then stores the information in the storage device 19 or RAM 14. The procedure of T12 is an example of reception processing.

[0051] Thereafter, the approval application 21 inserts the downloaded statement number into the number entry field 81 of the expense report 80 edited by the applicant. Furthermore, the approval application 21 inserts the downloaded information of the applicant and approver, specifically the names of the applicant and approver, into the signature and seal field 85 of the expense report 80 edited by the applicant. Furthermore, the approval application 21 inserts the downloaded QR code 86 to the right of the signature and seal field 85 in FIG. 2 of the expense report 80 edited by the applicant (T13).

[0052] In this embodiment, the statement number is a serial number for managing the expense report 80, and therefore the management device 50 issues a new statement number based on the statement number of the application form information 583 that has already been issued and stored in the user database 58. The management device 50 also searches the approver information 582 stored in the user database 58 based on the entries in the applicant information entry field 82 and the department information entry field 83 of the expense report 80, and extracts the information of the approver required to approve the expense report 80. The management device 50 can also extract the expense report 80 corresponding to the statement number by searching the user database 58 using the issued statement number.

[0053] Next, the approval application 21 sends print data of the expense report 80, which has been edited by the applicant, with the itemized statement number entered in the number entry field 81, with the information of the applicant and approver entered in the signature and seal field 85, and with information of the QR code 86, to the printing device 40. The printing device 40 then prints the expense report 80 based on the received print data. The approval application 21 also sends information of the expense report 80, which has been edited by the applicant, with the itemized statement number entered in the number entry field 81, and with the information of the applicant and approver entered in the signature and seal field 85, to the management device 50. Therefore, the management device 50 stores the received expense report 80 in the user database 58 as application form information 583 indexed by the itemized statement number (T14). Note that the procedure of T14 is an example of printing processing and uploading processing, and the application form information 583 is an example of electronic data.

[0054] In this embodiment, the statement number is entered in the number entry field 81, the information of the applicant and approver is entered in the signature and seal field 85, and the expense report 80, which also contains the information of the QR code 86, is printed on a single sheet of paper, making the printed material easier to carry and avoiding the inconvenience of losing part of the printed material.

[0055] In this embodiment, the signature and seal field 85 and the QR code 86 are configured to be printed together with the expense report 80, but this is not limiting. For example, the signature and seal field 85 and the QR code 86 may be printed as a label using a label printer separately from the expense report 80, and the applicant may affix the printed label to the expense report 80. Alternatively, only the QR code 86 may be printed as a label using a label printer separately from the expense report 80, and the applicant may affix the printed label to the expense report 80.

[0056] With this configuration, the approval application 21 does not need to insert the names of the applicant and approver and the QR code 86 into the expense report 80, and the editing process of the expense report 80 by the approval application 21 can be reduced.

[0057] Next, the applicant sends the paper expense report 80 printed by the printer 40 to the primary approver (T15). At this time, the applicant may either bring the printed paper expense report 80 to the primary approver, or attach the expense report 80 to an email and send it to the primary approver.

[0058] Next, the primary approver who receives the paper expense report 80 scans the QR code 86 printed on the expense report 80 with the camera 16 of the approver device 30 (T16). After the approval mini application 31 is downloaded from the external server 70 via the Internet line 62, the approval mini application 31 is launched on the approver device 30 (T17).

[0059] Next, the approval mini app 31 displays a request to scan the entire expense report 80 on the user IF 17. The primary approver, seeing this, scans the entire expense report 80 using the camera 16 of the approver device 30, and the approval mini app 31 then uses the OCR function of the approver device 30 to acquire and identify the statement number entered in the number entry field 81 of the expense report 80 and the applicant and approver information entered in the signature and seal field 85. Furthermore, if the approval mini app 31 detects the impression of the approver's seal in the signature and seal field 85, it accesses the management device 50 and updates the approval status (T18). However, at the stage of the first approver, there is no impression of the approver's seal in the signature and seal field 85, so the approval mini app 31 does not update the approval status. The procedure of T18 is an example of document identification processing and signer identification processing.

[0060] In this embodiment, the camera 16 of the approver device 30 is used to scan the QR code 86 or the entire expense report 80, but this is not limiting. For example, the approver may use the reader of the printing device 40 to scan the entire expense report 80, and the approver device 30 may obtain the scan results from the printing device 40 via the local area network 60.

[0061] Furthermore, in this embodiment, the entire expense report 80 is scanned to obtain the information of the applicant and approver entered in the signature and seal field 85, but this is not limiting. For example, the approval mini app 31 may be configured to access the management device 50 to obtain the information of the applicant and approver entered in the signature and seal field 85. Alternatively, the information of the applicant and approver may be embedded in the QR code 86, and when the QR code 86 is scanned by the camera 16 of the approver device 30 in T16, the approval mini app 31 may obtain the information of the applicant and approver entered in the signature and seal field 85.

[0062] Next, the approval mini application 31 displays an authentication request on the user IF 17 to verify the identity of the primary approver, that is, the owner of the approver device 30 (T19).

[0063] Next, the approval mini application 31 verifies the identity of the approver by using the biometric authentication information stored in the approver device 30, the ID and password, and user information registered in other applications such as Wallet (T20).The approval mini application 31 may also verify the identity of the approver by scanning the My Number card using NFC (Near Field Communication), for example.

[0064] Next, the approval mini-app 31 determines the authority of the approver, who is the owner of the approver device 30, based on the result of the approver's identity verification in T20 and the information on the applicant and approver obtained in T18 (T21).

[0065] In this embodiment, the applicant and approver entered in the signature and seal field 85 are those authorized to display an electronic signature, but this is not limited to this. For example, the accounting staff and department manager may also be included. In this case, in T18, the approval mini app 31 needs to access the management device 50 to obtain information about the accounting staff and department manager. In this case, the parties involved in the expense report 80 can display information indicating the signature status as an overlay in T24, which will be described later, allowing the approval procedure to proceed smoothly.

[0066] Next, the approval mini app 31 determines whether the approver of the approver device 30 (i.e., the logged-in user of the approver device 30) has permission to read the electronic signature (T22). Here, if the result of the identity verification in T20 does not match the applicant and approver information acquired in T18, and the approval mini app 31 determines that the approver, who is the owner of the approver device 30, does not have permission to display the electronic signature (T22: NO), this processing ends. At this time, the approver may be notified by displaying a message on the user IF 17 of the approver device 30 stating that "you are not authorized to display the electronic signature." Note that this notification may also be made by other notification methods such as audio.

[0067] In this manner, in this embodiment, if the approver, who is the owner of the approver device 30, does not have the authority to display an electronic signature, the process terminates, so that the approval status information obtained from the management device 50 is not displayed to a third party, ensuring the security of the approval process.

[0068] On the other hand, if the result of the identity verification in T20 matches the applicant and approver information acquired in T18 and the approval mini app 31 determines that the approver, who is the owner of the approver device 30, has the authority to read the electronic signature (T22: YES), the approval mini app 31 accesses the management device 50 and acquires approval status information from the application form information 583 stored in the user database 58 of the management device 50 (T23). Next, the approval mini app 31 displays a message on the user IF 17 of the approver device 30 prompting the user to use the camera 16 to take a photo of the signature and seal field 85 of the expense report 80.

[0069] Next, when the approver follows the displayed message and takes a picture of the signature and seal section 85 of the expense report 80 using the camera 16 of the approver device 30, the approval mini app 31 displays information indicating the signature status by overlaying it on the captured image using AR (Augmented Reality) as shown in Fig. 8 (T24). The processing of T24 is an example of display processing.

[0070] In this manner, in this embodiment, by displaying the signature status of the expense report 80, the approver, who is the owner of the approver device 30, can easily understand whether his or her approval is required. In addition, the current progress of approval can also be easily understood.

[0071] Next, the approval mini app 31 determines whether the owner of the approver device 30, whose identity was verified in T20, has approval authority (T25). If the owner of the approver device 30, whose identity was verified in T20, does not match the approver entered in the signature and seal field 85, or if it is determined that approval has already been granted based on the approval status information acquired in T23, the approval mini app 31 determines that the owner does not have approval authority (T25: NO) and ends this processing. At this time, the approver may be notified by displaying a message that "approval authority is not granted" on the user IF 17 of the approver device 30. This notification may also be provided by other notification methods, such as audio. The processing in T25 is an example of a determination processing.

[0072] Furthermore, if the owner of the approver device 30 whose identity was confirmed in T20 matches the approver listed in the signature and seal field 85, and if it is determined that the approval is not authorized based on the approval status information acquired in T23, the approval mini app 31 determines that the approver has the authority to approve (T25: YES).

[0073] Next, the approval mini application 31 determines whether all the subordinate approvers have been approved (T26). This determination is made based on the approval status information that the approval mini application 31 obtained from the management device 50 in T23. If the approval mini application 31 determines that all the subordinate approvers have not been approved (T26: NO), the approval mini application 31 notifies the approver (the approver himself / herself) by displaying a message that "all the subordinate approvers have not been approved" on the user IF 17 of the approver device 30 (T27), and then ends this processing. Note that this notification may be made by other notification methods such as audio. Note that the processing of T27 is an example of notification processing.

[0074] In this manner, in this embodiment, if there is an approver who should sign before the approver who is the owner of the approver device 30, the approver cannot sign, thereby ensuring the reliability of the approval process.

[0075] On the other hand, if the approval mini application 31 determines that all subordinate approvers have already approved the request (T26: YES), the approval mini application 31 displays a "message requesting approval" on the user IF 17 of the approver device 30 (T28). The procedure of T28 is an example of signature request processing.

[0076] The approver, upon seeing the "message requesting approval" displayed on the user IF 17 of the approver device 30, displays the expense report 80 on the user IF 17 of the approver device 30, and then executes the electronic signature process in the primary approver signature stamp field 852 of the signature stamp field 85 (T29).

[0077] Next, the approval mini app 31 accesses the management device 50 and updates the current approval status (T30). Accordingly, the management device 50 updates the application form information 583 stored in the user database 58. The procedure of T30 is an example of update processing.

[0078] Next, the approval mini app 31 determines whether all approvers have signed (T31). Here, the secondary approver's signature remains, so the approval mini app 31 determines that not all approvers have signed (T31: NO). Next, the approval mini app 31 displays a "message requesting that the expense report 80 be sent to the secondary approver" on the user IF 17 of the approver device 30 (T32). Upon seeing this message, the primary approver sends a paper copy of the expense report 80 to the secondary approver. At this time, the primary approver may bring a printed copy of the expense report 80 to the secondary approver, or may attach the expense report 80 to an email and send it to the secondary approver.

[0079] In this manner, in this embodiment, the approval mini application 31 completes the approval process for the primary approver by proceeding with the steps from T18 to T30. Note that in this embodiment, if not all approvers have signed, a guide message is displayed, allowing the approval process to proceed smoothly.

[0080] Next, when the secondary approver receives the paper expense report 80, he or she scans the QR code 86 printed on the expense report 80 with the camera 16 of the approver's device 30 (T16), the approval mini app 31 is launched on the approver's device 30 of the secondary approver (T17). Thereafter, the approval mini app 31 proceeds with the process in steps T18 to T30, just like the primary approver, and the approval process for the secondary approver is completed.

[0081] Then, in T31, the approval mini app 31 determines that all approvers have been approved (T31: YES), and then the approval mini app 31 notifies the user IF 17 of the applicant device 10 by push notification that approval has been completed (T33). Note that this notification may be by other notification methods such as audio. The procedure in T33 is an example of notification processing.

[0082] In this manner, in this embodiment, the approver device 30 notifies the applicant device 10 of completion, so that the applicant can immediately know that all signatures have been completed, thereby improving convenience.

[0083] Next, when the applicant who has seen the push notification taps the user IF 17 of the applicant device 10 to instruct printing of the approved expense report 80 (T34), the approval application 21 accesses the management device 50, obtains the data of the fully signed expense report 80 from the user database 58 of the management device 50, and then transmits the data to the printing device 40 as print data (T35), after which the process ends. The procedure of T35 is an example of the completed print process.

[0084] Then, based on the received print data, printing device 40 prints approved expense report 80. Therefore, the applicant can obtain a printed copy of expense report 80 with the completed signature.

[0085] In this embodiment, the primary approver and secondary approver proceed with the approval procedure using electronic signatures. Next, we will explain the case where the secondary approver signs on behalf of the primary approver after the primary approver has completed the approval procedure by stamping their seal in primary approver signature seal field 852 of signature seal field 85 on paper expense report 80. Note that in this explanation, if the approval mini app 31 performs the same processing in the above-mentioned steps T18 to T35, the explanation will be omitted and the explanation will continue.

[0086] That is, the primary approver who receives the paper expense report 80 stamps the primary approver's signature and seal field 852 on the paper expense report 80 without scanning the QR code 86 included in the expense report 80 with the camera 16 of the approver device 30. The stamped paper expense report 80 is then sent to the secondary approver listed on the expense report 80. At this time, the applicant may bring the printed paper expense report 80 to the secondary approver, or may attach the expense report 80 to an email and send it to the secondary approver.

[0087] Next, the secondary approver who receives the paper expense report 80 scans the QR code 86 printed on the expense report 80 with the camera 16 of the approver device 30 (T16), which launches the approval mini-app 31 on the approver device 30 (T17).

[0088] Next, at T18, if the approval mini app 31 detects the impression of the approver's seal in the primary approver signature and seal field 852 of the signature and seal field 85, it accesses the management device 50 and updates the approval status. Accordingly, the management device 50 updates the application form information 583 stored in the user database 58.

[0089] Next, in T26, the approval mini application 31 determines that all subordinate approvers have already approved the request because the approval status was updated in T18 (T26: YES).

[0090] Next, at T28, the approval mini app 31 displays a "message requesting approval" on the user IF 17 of the approver device 30. Then, upon seeing the "message requesting approval" displayed on the user IF 17 of the approver device 30, the secondary approver displays the expense report 80 on the user IF 17 of the approver device 30, and then executes electronic signature processing in the secondary approver signature and seal field 853 of the signature and seal field 85. Furthermore, if the secondary approver confirms that the primary approver's seal is present in the primary approver signature and seal field 852 of the paper expense report 80, the secondary approver executes electronic signature processing on behalf of the primary approver in the primary approver signature and seal field 852.

[0091] Next, in T30, the approval mini application 31 accesses the management device 50 and updates the approval status, including the proxy signature. Accordingly, the management device 50 updates the application form information 583 stored in the user database 58.

[0092] Next, in T35, the approval application 21 obtains the approved expense report 80 data, including the proxy signature, from the user database 58 of the management device 50, and then sends this data to the printing device 40 as print data.

[0093] In this manner, in this embodiment, even if a lower-level primary approver stamps a paper expense report 80, a higher-level secondary approver can sign on their behalf. Therefore, even if an intermediate approver cannot handle electronic signatures and stamps a paper expense report 80, the approval processing flow (signature flow) in signature system 1 can be completed with an electronic signature.

[0094] As described above in detail, in this embodiment, a signature is generated by the approval mini-application 31, which does not need to be installed, in the approver device 30. Therefore, a signature can be generated even on a device on which the approval application 21, which is a full application, is not installed or on which the installation of the approval application 21 is restricted due to device usage authority.

[0095] Note that this embodiment is merely an example and does not limit the present invention in any way. Therefore, the present invention can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the applicant device 10, printing device 40, and management device 50 constituting the signature system 1 of this embodiment are not limited to one, and may be multiple.

[0096] In this embodiment, the approvers are two people, a primary approver and a secondary approver, but it is also possible to have three or more approvers. In that case, the number of approver devices 30 may be the same as the number of approvers.

[0097] Furthermore, in this embodiment, when the approval mini app 31 determines in T31 that all approvers have been approved (T31: YES), it sends a push notification to the user IF 17 of the applicant device 10 to notify that approval has been completed (T33), but this is not limiting. For example, when the approval mini app 31 accesses the management device 50 to update the current approval status (T30), the management device 50 may determine whether all approvers have been approved, and if it determines that all approvers have been approved, the management device 50 may send a push notification to the user IF 17 of the applicant device 10 to notify that approval has been completed.

[0098] Furthermore, in this embodiment, the QR code 86 is used as the mark containing the activation information of the approved mini application 31, but other marks such as a two-dimensional bar code may also be used.

[0099] Furthermore, in this embodiment, when the startup information for the approval mini app 31 is acquired, the approval mini app 31 is downloaded and started, but if the approval app 21 is already installed in the approver device 30, the approval app 21 is started without downloading the approval mini app 31. Since the approval app 21 has the functions that the approval mini app 31 has, the approval app 21 can execute all the processes on the approver's side instead of the approval mini app 31.

[0100] Furthermore, in any processing procedure disclosed in this embodiment, the execution order of multiple processes in any multiple steps can be changed or they can be executed in parallel as desired, as long as no contradictions occur in the processing content.

[0101] The processing procedures disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processing procedures disclosed in the embodiments may be realized in various ways, such as a recording medium on which a program for executing the processing is recorded, or a method. [Explanation of symbols]

[0102] 1 Signature System 10. Applicant Device 30 Approver Devices 40 Printing device 50 Management device 11 Control section 19 Storage device 21 Approval App 31 Approval Mini App 70 External Servers 80 Expense Report 81 Number entry field 85 Signature and Seal Area 86 QR Codes

Claims

1. A signature system including a first device that is an applicant device and a second device that is an approval device, a full application executable by a computer of the first device is installed on the first device, the full application being a program corresponding to a signature flow; The second device does not have the full app installed, The first device When the full app receives a print instruction for a digital document to be signed, the full app causes a printer to print the digital document, a signature field, and a mark for activating a mini app, wherein identification information for the digital document is printed on the printout of the digital document and information identifying the signer is printed on the printout of the signature field, the mini app is a program that provides some of the functions of the full app, does not require installation, and is deleted from the device onto which it is downloaded after a predetermined period of time has passed, and the mark for activating the mini app includes access information used to download the mini app; Furthermore, the first device When the print instruction is received, the full app uploads electronic data corresponding to the digital document to a server and stores it in the server, and the electronic data stored in the server includes identification information of the digital document and signature information indicating the signer and signature status of the digital document; The second device The mark printed by the first device is read, the mini app is downloaded using the access information included in the mark, and the downloaded mini app is launched, and Identifying a user of the second device; reading the digital document printed by the first device and determining identification information of the digital document; reading the signature panel printed by the first device to identify a signer of the digital document; determining whether approval of the user of the identified second device is required based on the signer of the identified digital document and the signature information included in the electronic data stored in the server that corresponds to identification information of the identified digital document; If it is determined that approval from the user of the second device is necessary, a signature from the user of the second device is requested, and if a digital signature is provided, the server is accessed and the signature information included in the electronic data corresponding to the identification information of the specified digital document is updated. A signature system characterized by:

2. an applicant-side program executable by a computer of a first device, the applicant-side program being a program corresponding to a signature flow; Furthermore, the program on the application side may include the following in the computer of the first device: an acceptance process for accepting a print instruction for the digital document to be signed; and executing a print process, when the print instruction is received, to cause a printer to print the digital document, a signature field, and a mark for activating a mini appli, wherein identification information of the digital document is printed on the printed matter of the digital document and information indicating the signer is printed on the printed matter of the signature field, the mini appli is a program that provides some of the functions of the requesting program, does not require installation, and is deleted from the device on which it is downloaded after a predetermined period of time has passed, the mark for activating the mini appli includes access information used to download the mini appli, and when the mini appli is downloaded to a second device using the access information included in the mark, the mini appli identifies the user of the second device, the identification information of the digital document by reading the digital document printed by the first device, and the signer of the digital document by reading the signature field printed by the first device; Furthermore, the program on the application side may include the following in the computer of the first device: When the print instruction is received, an upload process is executed to upload electronic data corresponding to the digital document to a server and store the data in the server, the electronic data stored in the server includes identification information of the digital document and signature information indicating a signer and a signature status for the digital document, the mini app determines whether approval from a user of the second device is required based on the signer of the digital document and the signature information included in the electronic data stored in the server that corresponds to the identification information of the digital document, and if it is determined that approval from the user of the second device is required, requests a signature from the user of the second device, and if a digital signature is performed, accesses the server and updates the signature information included in the electronic data that corresponds to the identified identification information of the digital document. A program characterized by:

3. The program according to claim 2, In the printing process, The digital document, the signature field, and the mark for launching the mini app are printed on the same sheet. A program characterized by:

4. The program according to claim 2, In the printing process, printing the digital document on a sheet separate from the signature field and the mark for activating the mini-app; A program characterized by:

5. In the program according to any one of claims 2 to 4, The program on the application side is installed in the computer of the first device. a completion print instruction that is received by the first device upon notification of completion of the signature flow, and when the completion print instruction instructing printing of the digital document is input to the first device, the mini app executes a completion print process that downloads the signed digital document from the server and prints it on the printer, and when all signatures for the digital document are completed, the mini app executes a process that notifies the first device of the completion of the signature flow corresponding to the electronic data. A program characterized by:

6. an approval-side program executable by a computer of a second device, the approval-side program being a program that provides some of the functions of a full app, that does not need to be installed, and that is deleted from the device to which it is downloaded after a predetermined period of time has passed, the full app being a program corresponding to a signature flow and being a program separate from the approval-side program; Furthermore, the program on the approving side may include the following in the computer of the second device: a user identification process for identifying a user of the second device; a document identification process for reading the digital document printed by the full application and identifying identification information of the digital document, and when the full application receives a print instruction for the digital document to be signed, causes a printer to print the digital document, a signature field, and a mark for launching the approval-side program, and the identification information of the digital document is printed on the printed matter of the digital document and information indicating the signer is printed on the printed matter of the signature field, and when the full application receives the print instruction, uploads electronic data corresponding to the digital document to a server and stores it on the server, and the electronic data stored on the server includes the identification information of the digital document and signature information indicating the signer and the signing status of the digital document, and the second device reads the mark printed by the full application, and the approval-side program is downloaded to the second device, thereby launching the approval-side program, Furthermore, the program on the approving side may include the following in the computer of the second device: a signer identification process for reading the signature field printed by the full app and identifying the signer of the digital document; a determination process for determining whether approval of the user of the identified second device is required based on the identified signer of the digital document and the signature information included in the electronic data stored in the server that corresponds to identification information of the identified digital document; a signature request process for requesting a signature from the user of the second device when it is determined in the determination process that approval from the user of the second device is required; and executing an update process for accessing the server and updating the signature information included in the electronic data corresponding to the identification information of the digital document identified in the document identification process, when a digital signature is made after the request made in the signature request process. A program characterized by:

7. 7. The program according to claim 6, The program on the approving side is installed in the computer of the second device. If the identified user of the second device does not have the authority to read the electronic data stored in the server, the determination process is not executed and a signature of the user of the second device is not requested. A program characterized by:

8. The program according to claim 7, The program on the approving side is installed in the computer of the second device. and if the identified user of the second device has the authority to read the electronic data stored in the server, executing a display process to display a signature status for the digital document based on the signature information included in the electronic data stored in the server. A program characterized by:

9. In the program according to any one of claims 6 to 8, In the determination process, If there are multiple approvers for the digital document and the identified user of the second device is unauthorized, but an approver lower in rank than the identified user of the second device is unauthorized, it is not determined that approval from the user of the second device is necessary. A program characterized by:

10. 10. The program according to claim 9, The program on the approving side is installed in the computer of the second device. When it is determined that approval from the user of the second device is not required because an approver lower than the identified user of the second device is not approved, a notification process is executed to notify that the lower approver is not approved. A program characterized by:

11. The program according to claim 9 or 10, In the determination process, Even if an approver lower than the user of the second device is not approved based on the signature information, if a seal impression of the lower approver is found in the result of reading the signature field, the lower approver is deemed to have approved the device, In the update process, If the lower-level approver has approved the document because of the presence of the seal imprint of the lower-level approver, when updating the signature information, the user of the second device is marked as signed, and the lower-level approver is marked as signed. A program characterized by:

Images