Information processing device, information processing method, program, and information processing system

Abstract

To improve the accuracy of information to be provided.SOLUTION: An information processing device includes: a display control unit that causes a display device to display business form management information containing business form information acquired on the basis of an embedded code contained in business form image data, and management information for managing the business form information; and an output unit that receives an operation commanding an output of the business form management information and outputs the business form management information to an external device.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, a program, and an information processing system. [Background technology]

[0002] A conventional technique is known in which a form input screen is displayed and form image data (e.g., a PDF file) is created based on the input form information. Another conventional technique is known in which character recognition, such as OCR (Optical Character Reader), is performed on the form image indicated by the form image data to extract character strings contained in the form image and allow the user to confirm the extraction results. Summary of the Invention [Problem to be solved by the invention]

[0003] The character recognition technology described above in the related art may not correctly extract character strings, making it difficult to obtain information contained in form images with high accuracy. For this reason, with the related art, it is difficult to provide highly accurate information, for example, when providing information obtained from form images to other systems.

[0004] The disclosed technology aims to improve the accuracy of the information provided. [Means for solving the problem]

[0005] The disclosed technology includes a display control unit that displays, on a display device, form management information including form information acquired based on an embedded code included in form image data and management information for managing the form information, and an output unit that receives an operation to instruct output of the form management information and outputs the form management information to an external device, the embedding code includes form identification information for identifying the form information, The display control unit Depending on whether or not form information whose form identification information matches the form identification information indicated by the embedding code exists in a storage unit that stores form information including form identification information,This information processing device determines whether the report information has been acquired based on the embedded code, and if it determines that the report information has been acquired based on the embedded code, displays the report management information on the display device while prohibiting editing of the report information. [Effects of the Invention]

[0006] The accuracy of the information provided can be improved. [Brief explanation of the drawings]

[0007] [Figure 1] 1 illustrates an example of a system configuration of a form management system according to a first embodiment; [Figure 2] FIG. 2 illustrates an example of a hardware configuration of an information processing device. [Figure 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 10 is a diagram illustrating an example of a customer management database. [Figure 5] FIG. 10 is a diagram illustrating an example of an invoice database. [Figure 6] FIG. 10 is a diagram illustrating an example of an embedding management database. [Figure 7] FIG. 10 is a diagram illustrating an example of an invoice management database. [Figure 8] FIG. 2 is a diagram illustrating the functions of each device included in the form management system of the first embodiment. [Figure 9] FIG. 2 is a first sequence diagram illustrating the operation of the form management system according to the first embodiment. [Figure 10] FIG. 10 is a second sequence diagram illustrating the operation of the form management system of the first embodiment. [Figure 11] 10 is a flowchart illustrating a process for displaying a confirmation screen. [Figure 12] FIG. 10 is a diagram showing an example of an invoice creation screen. [Figure 13] FIG. 10 is a diagram illustrating an example of a confirmation screen. [Figure 14]FIG. 10 is a diagram showing an example of an invoice. [Figure 15] FIG. 10 illustrates an example of a system configuration of a form management system according to a second embodiment. [Figure 16] FIG. 10 illustrates an example of a system configuration of a form management system according to a third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] (First embodiment) The first embodiment will be described below with reference to the drawings. Fig. 1 is a diagram showing an example of the system configuration of a form management system according to the first embodiment.

[0009] The document management system 100 of this embodiment includes a transaction management device 200, a document management device 300, and a terminal device 500. Both the transaction management device 200 and the document management device 300 are information processing devices and are capable of communicating via a network. The terminal device 500 may be, for example, a tablet terminal, and may be capable of communicating with both the transaction management device 200 and the document management device 300.

[0010] In the form management system 100 of this embodiment, when form information indicating the contents of a form is input from the terminal device 400, the transaction management device 200 generates and outputs form image data including the form information. The terminal device 400 is a terminal device that is mainly used by the issuer of the form.

[0011] At this time, the transaction management device 200 generates an embedded code indicating form identification information for identifying the form and includes it in the form image data. Therefore, in this embodiment, when the form image data generated by the transaction management device 200 is output as a form, this form becomes a form to which an embedded code indicating form identification information for identifying the form is added. In addition, the transaction management device 200 stores the form identification information in association with the form information.

[0012] In the form management system 100, when form image data is input from the terminal device 500, the form management device 300 reads form identification information from an embedded code included in the form image data. The terminal device 500 is a terminal device that is mainly used by the recipient of the form.

[0013] Next, the form management device 300 acquires form information stored in association with the read form identification information from the transaction management device 200. Then, the form management device 300 outputs form management information that associates the acquired form information with management information for managing the form information to the core system 600. The core system 600 is a system that executes various processes using the form management information.

[0014] In this way, when issuing a form, the form management system 100 of this embodiment generates an embed code including form identification information that identifies the form and embeds it in the form image data. Then, when form image data is input from the form recipient, the form management system 100 of this embodiment acquires form information that corresponds to the embed code included in the form image data.

[0015] Therefore, according to this embodiment, it is possible to obtain the form information entered when the form was issued without performing character recognition processing on the form image data entered by the recipient of the form. In other words, according to this embodiment, it is possible to improve the accuracy of information obtained from the form image.

[0016] Furthermore, in this embodiment, when providing information contained in a form image to the core system 600, which is an external system (external device), it is possible to provide the form information that was input when the form was issued. Therefore, according to this embodiment, it is possible to provide highly accurate information to the core system 600.

[0017] In the following description, an invoice will be used as an example of a form. Therefore, in the following description, the issuer of the form is the issuer of the invoice, and the recipient of the form is the billing destination to which the invoice is sent.

[0018] The issuer of the invoice is, for example, a business that conducts transactions with various business partners. Note that the business in this embodiment may be an individual or an organization such as a company or corporation. In the following description of the embodiment, the business may be referred to as Tenant A.

[0019] The billing destination of an invoice is the business partner of the issuer of the invoice. In other words, the billing destination of an invoice is the business partner of Tenant A. In the following description of the embodiment, the billing destination of an invoice may be referred to as Tenant B.

[0020] In the document management system 100 of this embodiment, the transaction management device 200 has a supplier management database 210 , an invoice database 220 , an embedded management database 230 , and a transaction management unit 240 , and communicates with a terminal device 400 .

[0021] The terminal device 400 is a terminal device that is mainly used by the issuer of the bill (tenant A). In the following description, the terminal device 400 may be referred to as the billing source terminal 400.

[0022] The business partner management database 210 stores business partner information related to business partners of tenant A. The invoice database 220 stores invoice information related to invoices entered by tenant A. The embedding management database 230 stores embedding management information that associates embedding codes generated when issuing an invoice with invoice information.

[0023] The transaction management unit 240 of this embodiment accepts input of invoice information from the terminal device 400, and generates and outputs form image data including an invoice (document) and an embedded code indicating document identification information that identifies the invoice.

[0024] The form management device 300 of this embodiment has an invoice management database 310 and a form management unit 320, and communicates with the transaction management device 200, the terminal device 500, and the core system 600.

[0025] The terminal device 500 is a terminal device that is mainly used by the billing destination of the invoice. In the following description, the terminal device 500 may be referred to as the billing destination terminal 500.

[0026] The core system 600 is, for example, a system that performs specific processing using invoice management information stored in the invoice management database 310. Specifically, the core system 600 may be, for example, an accounting system that transfers invoice amounts to financial institutions.

[0027] The invoice management database 310 of this embodiment stores form management information in which invoice information acquired from form image data input from the terminal device 500 is associated with management information for managing invoices. The invoice information of this embodiment is information indicating the contents of an invoice, and is an example of form information indicating the contents of a form.

[0028] When form image data is input from the terminal device 500, the form management unit 320 obtains invoice information corresponding to the embedded code included in the form image data from the transaction management device 200. If invoice information is not obtained from the transaction management device 200, the form management unit 320 performs form recognition on the form image indicated by the form image data and obtains invoice information as the recognition result. Furthermore, the form management unit 320 associates the management information input from the terminal device 500 with the invoice information, generates invoice management information, and stores it in the invoice management database 310. Furthermore, the form management unit 320 outputs the invoice management information to the core system 600 in response to a request from the terminal device 500.

[0029] 1 includes transaction management device 200, form management device 300, and billing destination terminal 500, but the devices included in form management device 100 are not limited to these. Form management device 100 may also include terminal device 400. Furthermore, form management system 100 may include transaction management device 200 and form management device 300, but may not include terminal devices 400 and 500.

[0030] In addition, in this embodiment, the transaction management device 200 and the document management device 300 are separate devices, but this is not limiting. The transaction management device 200 and the document management device 300 may be realized by one information processing device, or may be realized by three or more information processing devices.

[0031] The hardware configurations of the transaction management device 200 and the form management device 300 of this embodiment will be described below with reference to Fig. 2. Since the transaction management device 200 and the form management device 300 of this embodiment are general information processing devices, Fig. 2 describes the hardware configuration of the form management device 300 as an example of the hardware configuration of an information processing device.

[0032] Fig. 2 is a diagram showing an example of the hardware configuration of an information processing device, which is a form management device 300 that is a second information processing device.

[0033] The document management device 300 is constructed by a computer, and as shown in FIG. 2, includes a CPU 301, a ROM 302, a RAM 303, a HD 304, a HDD (Hard Disk Drive) controller 305, a display 306, an external device connection I / F (Interface) 308, a network I / F 309, a bus line B1, a keyboard 311, a pointing device 312, a DVD-RW (Digital Versatile Disk Rewritable) drive 314, and a media I / F 316.

[0034] Of these, the CPU 301 controls the overall operation of the form management device 300. The ROM 302 stores programs used to drive the CPU 301, such as an IPL. The RAM 303 is used as a work area for the CPU 301. The HDD 304 stores various data, such as programs. The HDD controller 305 controls the reading and writing of various data from and to the HDD 304 under the control of the CPU 301. The display 306 displays various information, such as a cursor, menu, window, text, or image. The external device connection I / F 308 is an interface for connecting various external devices. In this case, external devices include, for example, a USB (Universal Serial Bus) memory or a printer. The network I / F 309 is an interface for data communication using a communication network. The bus line B1 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 301, shown in FIG. 2.

[0035] The keyboard 311 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 312 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 314 controls reading and writing of various data from a DVD-RW 313, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 316 controls reading and writing (storing) of data from a recording medium 315, such as a flash memory.

[0036] Next, the hardware configurations of the terminal device (billing terminal) 400 and the terminal device (billing destination terminal) 500 of this embodiment will be described with reference to Fig. 3. Since the terminal device 400 and the terminal device 500 of this embodiment are general terminal devices, Fig. 3 describes the hardware configuration of the terminal device 500 as an example of the hardware configuration of a terminal device.

[0037] 3 is a diagram showing an example of the hardware configuration of a terminal device, and shows the hardware configuration of billing destination terminal 500 as an example.

[0038] The terminal device 500 of this embodiment includes a CPU 501 , a ROM 502 , a RAM 503 , an EEPROM 504 , a CMOS sensor 505 , an image sensor I / F 506 , an acceleration / direction sensor 507 , a media I / F 509 , and a GPS receiving unit 511 .

[0039] Of these, the CPU 501 is an arithmetic processing unit that controls the overall operation of the terminal device 500. The ROM 502 stores the CPU 501 and programs used to drive the CPU 501, such as the IPL. The RAM 503 is used as a work area for the CPU 501. The EEPROM 504 reads or writes various data, such as smartphone programs, under the control of the CPU 501. The ROM 502, RAM 503, and EEPROM 504 are examples of storage devices of the terminal device 500.

[0040] The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) and obtains image data under the control of the CPU 501. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

[0041] The imaging element I / F 506 is a circuit that controls the driving of the CMOS sensor 505. The acceleration / azimuth sensor 507 is a variety of sensors, such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 509 controls the reading and writing (storage) of data from and to a recording medium 508, such as a flash memory. The GPS receiver 511 receives GPS signals from GPS satellites.

[0042] The terminal device 500 also includes a long-distance communication circuit 512, an antenna 512a of the long-distance communication circuit 512, a CMOS sensor 513, an image sensor I / F 514, a microphone 515, a speaker 516, an audio input / output I / F 517, a display (display device) 518, an external device connection I / F (Interface) 519, a short-distance communication circuit 520, an antenna 520a of the short-distance communication circuit 520, and a touch panel 521.

[0043] Of these, the long-distance communication circuit 512 is a circuit that communicates with other devices via a communication network. The CMOS sensor 513 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 501. The image sensor I / F 514 is a circuit that controls the driving of the CMOS sensor 513. The microphone 515 is a built-in circuit that converts sound into an electrical signal. The speaker 516 is a built-in circuit that converts an electrical signal into physical vibrations to produce sound such as music or voice. The sound input / output I / F 517 is a circuit that processes the input and output of sound signals between the microphone 515 and the speaker 516 under the control of the CPU 501.

[0044] The display 518 is a type of display means such as a liquid crystal display or organic electroluminescence (EL) display that displays an image of a subject, various icons, etc. The external device connection I / F 519 is an interface for connecting various external devices. The short-range communication circuit 520 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 521 is a type of input means that allows a user to operate the terminal device 500 by pressing the display 518. The display 518 is an example of a display unit that the terminal device 500 has.

[0045] Next, each database of transaction management device 200 will be described with reference to Figures 4 to 6. Figure 4 is a diagram showing an example of a supplier management database.

[0046] The customer management database 210 of this embodiment is provided, for example, for each tenant A. The customer management database 210 of this embodiment includes information items such as name, address, telephone number, email address, and name of person in charge, and these items are associated with the tenant ID and tenant name of tenant A.

[0047] In this embodiment, information in the customer management database 210 that includes values ​​for items such as name, address, telephone number, email address, and person in charge may be referred to as customer information. The tenant ID and tenant name are information for identifying tenant A. The value of the item "name" indicates the name of the customer (billing party), and the values ​​of the items "address," "telephone number," "email address," and "person in charge" indicate the address, telephone number, email address, and name of the person in charge of the transaction of the billing party, respectively.

[0048] It should be noted that the information items included in the business partner information are not limited to the example shown in Fig. 4. The information items included in the business partner information do not have to include all the items shown in Fig. 4, and may include items other than those shown in Fig. 4.

[0049] In this embodiment, when transaction management device 200 receives input from billing terminal 400, the supplier information is stored in supplier management database 210.

[0050] 5 is a diagram showing an example of the invoice database 220. The invoice database 220 of this embodiment may be provided for each tenant A, similar to the supplier management database 210.

[0051] The invoice database 220 includes information items such as document ID, billing destination, billing amount, billing date, payment due date, detailed information, and transfer destination information, and each item is associated with tenant A's tenant ID and tenant name.

[0052] Furthermore, the item "form ID" is associated with other items in the invoice database 220. In this embodiment, information including the value of the item "form ID" and the values ​​of other items in the invoice database 220 is referred to as invoice information.

[0053] In other words, the invoice database 220 is an example of a form information storage unit in which information specifying the input source (tenant A) of invoice information (form information) is associated with form information.

[0054] In this embodiment, when values ​​of items other than the form ID are input from the terminal device 400, a form ID is generated and invoice information including the form ID is stored in the invoice database 220.

[0055] The value of the item "Form ID" is form identification information for identifying a form (invoice). In other words, the value of the item "Form ID" is form identification information for identifying form information.

[0056] The value of the "Billing address" field indicates the name of the billing address of the invoice identified by the report ID. The values ​​of the "Billing amount," "Billing date," and "Payment due date" fields indicate the billing amount, billing date, and payment due date, respectively, listed on the invoice.

[0057] The item "Detailed Information" corresponds to items that indicate the breakdown of the billing amount, such as the items "Product Code," "Product Name," and "Quantity," and the value of the item "Detailed Information" indicates the breakdown of the billing amount.

[0058] The item "Transfer destination information" corresponds to items indicating the transfer destination of the invoice amount, such as the items "Bank name," "Branch," "Account type," and "Account number," and the value of the item "Transfer destination information" indicates the transfer destination of the invoice amount.

[0059] It should be noted that the information items included in the invoice information are not limited to the example shown in Fig. 5. The information items included in the invoice information do not have to include all the items shown in Fig. 5, and may include items other than the items shown in Fig. 5.

[0060] 6 is a diagram showing an example of an embedding management database. The embedding management database 230 of this embodiment includes information items such as embedding position (upper left), embedding position (lower right), embedding type, embedding content, and encryption key. In the following description, information including the values ​​of each item in the embedding management database 230 may be referred to as embedding information. The embedding information is information that is stored in advance in the embedding management database 230 by tenant A, and is referenced when the form management device 300 embeds an embedding code.

[0061] The values ​​of the items "Embedding position (top left)" and "Embedding position (bottom right)" are information for specifying the position where the embedding code is embedded in the form image. Specifically, the values ​​of the items "Embedding position (top left)" and "Embedding position (bottom right)" indicate, for example, the coordinates indicating the position of the top left vertex of the QR code (registered trademark) in the form image and the coordinates indicating the position of the bottom right vertex of the QR code (registered trademark) in the form image.

[0062] The value of the item "embedded type" indicates the type of embedding code embedded in the form image. The value of the item "embedded content" indicates the information embedded in the embedding code. In this embodiment, the information indicated by the embedding code is the form ID.

[0063] The value of the item "encryption key" may be referenced when the form management device 300 reads the form ID from the embedded code.

[0064] The embedded information does not necessarily have to include the encryption key. The encryption key may be referenced, for example, when form image data showing an invoice is transmitted to the billing destination terminal 500 via a network or the like.

[0065] In addition, in this embodiment, the embedded management database 230 is provided in the transaction management device 200, but this is not limited to this.

[0066] The embedding management database 230 may be provided, for example, in both the transaction management device 200 and the form management device 300. Specifically, for example, when the form management device 300 receives form image data from the billing destination terminal 500 via a network, it may refer to the embedding management database 230 provided in the form management device 300 to identify the position of the embedding code in the form image and read the form ID.

[0067] Next, a description will be given of the invoice management database 310 of the form management device 300. Fig. 7 is a diagram showing an example of the invoice management database.

[0068] In this embodiment, the invoice management database 310 is provided for each tenant B. The invoice management database 310 also includes information items such as a form ID, billing source, billing amount, payment deadline, statement information, and journal information.

[0069] In other words, the invoice management database 310 includes, as information items, items included in invoice information, journal information, and the like.

[0070] The item "journalization information" is associated with various items related to journalization, and the value of the item "journalization information" includes various items related to journalization and the values ​​of those items. Journalization information is information input to the form management device 300 by the billing destination terminal 500, which is the terminal on the receiving side that receives the invoice, and is management information for managing the invoice. In other words, journalization information is management information input on the receiving side of the form for managing the form.

[0071] In this embodiment, information in which invoice information and management information are associated with each other in the invoice management database 310 may be referred to as invoice management information.

[0072] In other words, the invoice management information is an example of form management information in which form information indicating the contents of a form is associated with management information for managing the form.

[0073] 7, the management information for the invoice is shown as journal entry information, but the management information may include information other than journal entry information. Specifically, the management information may include payment information, such as account information for the transfer destination of the invoice amount and the date of transfer. Furthermore, if the document is a delivery note or the like, the management information may include, for example, purchase information.

[0074] In addition, the invoice management information of this embodiment may include an item indicating the status of invoice management as an information item.

[0075] The status of the invoice management information is, for example, the progress of the confirmation work of the invoice management information at the invoice destination.

[0076] In this embodiment, there are four states of invoice management information: unprocessed state, draft saved state, confirmed state, and externally output state. Each state is as follows.

[0077] Unprocessed state (state 1): This is the state immediately after the invoice information has been acquired, and no accounting information has been entered.

[0078] Draft saved state (state 2) This is the state when the invoice management information is being checked, etc., and the invoice management information has not yet been finalized.

[0079] Confirmed state (state 3) The state in which the confirmation of the invoice management information and other operations have been completed and the information has been stored in the invoice management database 310 as confirmed information. External output completed state (state 4) The state in which the output of invoice management information to the core system 600 has been completed.

[0080] Next, the functions of each device included in the form management system 100 of this embodiment will be described with reference to Fig. 8. Fig. 8 is a diagram illustrating the functions of each device included in the form management system of the first embodiment.

[0081] First, we will explain the functions of the transaction management device 200. The transaction management unit 240 of the transaction management device 200 of this embodiment has a communication unit 241, an input reception unit 242, a code generation unit 243, an image generation unit 244, an embedding unit 245, a report output unit 246, and an output control unit 247.

[0082] The communication unit 241 transmits and receives information between the transaction management device 200 and other devices. The input reception unit 242 receives various inputs to the transaction management device 200. Specifically, the input reception unit 242 receives various information inputs and requests from the billing terminal 400.

[0083] The code generation unit 243 generates a code to be embedded in a form image. In the following explanation, a QR code will be explained as an example of a code generated by the code generation unit 243, but the code generated by the code generation unit 243 is not limited to a QR code. The code generated by the code generation unit 243 may be any code as long as it indicates a form ID and can be embedded in a form image.

[0084] The image generating unit 244 generates image data (document image data) showing the invoice based on the invoice information input from the invoice source terminal 400.

[0085] The embedding unit 245 embeds the QR code generated by the code generating unit 243 into the form image data, and generates form image data including the embedded code.

[0086] The form output unit 246 outputs form image data including a QR code. The form output unit 246 of this embodiment may, for example, transmit the form image data including the QR code to an image forming device or the like, and output the form image data as a printed matter. The form output unit 246 may also transmit the form image data including the QR code to the billing destination terminal 500.

[0087] When the output control unit 247 receives a request to obtain invoice information from the document management device 300, it determines whether to output (send) the requested invoice information to the document management device 300, and if it determines that the invoice information should be output, it outputs the invoice to the document management device 300.

[0088] Next, we will explain the functions of the form management device 300. The form management unit 320 of the form management device 300 of this embodiment has a communication unit 321, an input reception unit 322, an authentication unit 323, a reading unit 324, an acquisition unit 325, a form recognition unit 326, a display control unit 327, and an output unit 328.

[0089] The communication unit 321 transmits and receives information between the form management device 300 and other devices. The input reception unit 322 receives various inputs to the form management device 300. Specifically, the input reception unit 322 receives various information inputs and requests from the billing destination terminal 500.

[0090] The authentication unit 323 authenticates the billing destination based on login information and the like input from the billing destination terminal 500. The authentication unit 323 may store the login information for authenticating the billing destination in association with information (tenant name) and the like that identifies the billing destination (tenant B).

[0091] When the input receiving unit 322 receives input of the form image data, the reading unit 324 reads the form ID from the QR code included in the form image data.

[0092] When the reading unit 324 of the document management device 300 reads the document ID, the communication unit 321 sends a request to the transaction management device 200 to obtain invoice information, which includes the read document ID and information identifying the billing destination of the invoice (tenant name, etc.).

[0093] The acquisition unit 325 requests the transaction management device 200 to acquire the invoice information corresponding to the form ID, and acquires the invoice information corresponding to the form ID read by the reading unit 324.

[0094] The document recognition unit 326 determines whether or not invoice information has been acquired by the acquisition unit 325, and if invoice information has not been acquired by the acquisition unit 325, performs document recognition on the input document image data and treats the recognition result as invoice information.

[0095] Cases where invoice information cannot be acquired include when the form image data is created by a system other than the form management system 100 and does not include a QR code, or when reading the QR code fails.

[0096] In addition, form recognition in this embodiment is a process of extracting the names (item names) of items contained in the form image represented by the form image data and the values ​​(item values) of these items, converting the items and item values ​​into text data, and associating them.

[0097] The display control unit 327 controls the display on the billing destination terminal 500. Specifically, the display control unit 327 causes the billing destination terminal 500 to display a screen including either the invoice information acquired from the transaction management device 200 or the invoice information extracted as a result of form recognition by the form recognition unit 326, and an input field for management information.

[0098] The output unit 328 outputs the invoice management information stored in the invoice management database 310 to the core system 600 or the like.

[0099] Next, the functions of the billing terminal 400 and the billing destination terminal 500 will be described. The billing terminal 400 of this embodiment has a display unit 430 and a communication unit 440. The display unit 430 displays information on the display of the billing terminal 400. The communication unit 440 transmits and receives information between the billing terminal 400 and other devices.

[0100] The billing destination terminal 500 of this embodiment has a display unit 530 and a communication unit 540. The display unit 530 displays information on the display of the billing destination terminal 500. The communication unit 540 transmits and receives information between the billing destination terminal 500 and other devices.

[0101] Next, the operation of the form management system 100 of this embodiment will be described with reference to Figures 9 to 11. Figure 9 is a first sequence diagram illustrating the operation of the form management system of the first embodiment. Figure 9 shows the operation up to the issuance of an invoice in the form management system 100.

[0102] In the form management system 100 of this embodiment, the billing terminal 400 transmits a bill creation request to the transaction management device 200 in response to an operation from tenant A (step S901).

[0103] When the transaction management device 200 receives an invoice creation request via the input receiving unit 242, it sends an instruction to display an invoice creation screen to the billing terminal 400 (step S903). When the billing terminal 400 receives the instruction to display the creation screen, it causes the display unit 430 to display the invoice creation screen on the display (step S903). Details of the creation screen will be described later.

[0104] Next, the billing terminal 400 accepts input of bill information from tenant A (step S904). Next, the billing terminal 400 accepts input of an instruction to issue a bill from tenant A (step S905).

[0105] When the billing terminal 400 receives the instruction to issue an invoice, it transmits the input invoice information and an invoice issuance request including the invoice information to the transaction management device 200 (step S906). Note that this issuance request may include information identifying tenant A who uses the billing terminal 400. The information identifying tenant A is, for example, the tenant ID or tenant name.

[0106] When the transaction management device 200 receives the issuance request and invoice information through the input receiving unit 242, the code generating unit 243 generates a QR code indicating the form ID to be included in the invoice information (step S907). At this time, the code generating unit 243 includes the generated form ID in the invoice information received from the invoice source terminal 400 and stores it in the invoice database 220.

[0107] Next, the transaction management device 200 generates image data showing the invoice based on the received invoice information using the image generation unit 244 (step S908). In other words, the image generation unit 244 generates form image data.

[0108] Next, the transaction management device 200 causes the embedding unit 245 and the code generating unit 243 to refer to the embedding management database 230 and embed a QR code in the form image at the position indicated by the embedding management information (step S909).

[0109] Next, transaction management device 200 issues an invoice including a QR code using form output unit 246 (step S910). In other words, transaction management device 200 causes form output unit 246 to output form image data including a QR code.

[0110] 10 is a second sequence diagram illustrating the operation of the form management system of the first embodiment. In FIG. 10, the operation up to the output of the invoice management information to the core system 600 in the form management system 100 is shown.

[0111] In the form management system 100, when the billing destination terminal 500 receives input of login information from the bill recipient (step S1001), it transmits a login request to the form management device 300 (step S1002).

[0112] The login request includes the entered login information.

[0113] When the input receiving unit 322 receives a login request, the document management device 300 performs authentication using the authentication unit 323, and based on the login information received together with the login request, identifies, for example, the tenant name of the billing destination (tenant B) corresponding to the login information (step S1003).

[0114] Next, the billing destination terminal 500 accepts an upload operation of the form image data from the billing destination (step S1004), and uploads (transmits) the form image data to the form management device 300 (step S1005).

[0115] The form image data uploaded from the billing destination terminal 500 may be form image data including a QR code transmitted from the billing source terminal 400 to the billing destination terminal 500. The form image data uploaded from the billing destination terminal 500 may also be form image data generated by scanning or the like an invoice output as a printout in response to a request for issuance of an invoice from the billing source terminal 400.

[0116] Next, when the form management device 300 receives the form image data, the reading unit 324 reads the QR code included in the form image data and acquires the form ID indicated by the QR code (step S1006).

[0117] Next, the document management device 300 causes the acquisition unit 325 to send a request to acquire invoice information including the document ID and the tenant name of tenant B to the transaction management device 200 (step S1007).

[0118] When the transaction management device 200 receives the document ID and the tenant name of tenant B, the output control unit 247 determines whether there is invoice information in the invoice database 220 whose value in the item "document ID" matches the received document ID and whose value in the item "billing destination" matches the received tenant name (step S1008).

[0119] The example in Figure 10 shows the operation when there is invoice information in the invoice database 220 where the value of the item "Report ID" matches the received report ID and the value of the item "Billing destination" matches the received tenant name.

[0120] Following step S1008, the transaction management device 200, via the output control unit 247, extracts from the invoice database 220 invoice information whose values ​​in the item "document ID" and the item "billing destination" match the received document ID and tenant name, and outputs the information to the document management device 300 (step S1009).

[0121] If the invoice database 220 does not contain the corresponding invoice information, the output control unit 247 may send an error notification or the like to the document management device 300.

[0122] Also, in step S1007, the acquisition request sent by the form management device 300 to the transaction management device 200 does not have to include the tenant name of tenant B. In this case, in step S1008, the transaction management device 200 determines whether there is invoice information whose value in the item "form ID" matches the received form ID, and in step S1009, extracts the invoice information determined to match and outputs it to the form management device 300.

[0123] Next, the document management device 300 may perform processing from step S1011 onwards based on the acquired invoice information, or may determine whether the value of the item "billing destination" included in the acquired invoice information matches the tenant name of tenant B identified by the authentication unit 323, and if they match, may perform processing from step S1011 onwards, or if they do not match, may control the display of an error screen or the like.

[0124] Furthermore, if the form management device 300 does not acquire a form ID from the form image data in step S1006, the form recognition unit 326 performs form recognition on the form image data and stores the recognition result as invoice information (step S1010). Note that if the form management device 300 receives an error notification or the like from the transaction management device, or if the value of the item "billing destination" included in the acquired invoice information does not match the tenant name of tenant B identified by the authentication unit 323, the form management device 300 may perform form recognition on the form image data by the form recognition unit 326 in the same way as when the form ID is not acquired from the form image data, and store the recognition result as invoice information.

[0125] Next, when the acquisition unit 325 of the form management device 300 acquires the invoice information, the display control unit 327 transmits information for displaying a confirmation screen including the invoice information to the billing destination terminal 500 (step S1011).

[0126] The billing destination terminal 500 receives this information and displays a confirmation screen (step S1012). The display control unit 327 may change the display mode of the invoice information on the confirmation screen depending on how the invoice information is acquired. Details of the processing of the display control unit 327 and the confirmation screen will be described later.

[0127] The billing destination terminal 500 accepts input of journalization information (management information) for managing the bill on the confirmation screen (step S1013).

[0128] Next, the billing destination terminal 500 transmits the input journal information to the document management device 300 (step S1014).

[0129] When the form management device 300 receives the journalization information, it stores the invoice information and the journalization information in association with each other as invoice management information in the invoice management database 310 (step S1015).

[0130] Next, when the billing destination terminal 500 receives an operation to change the state of the invoice management information to "confirmed state" (step S1016), it transmits an instruction to the form management device 300 to confirm the invoice management information (step S1017).

[0131] When the form management device 300 receives the instruction to confirm the invoice management information, it sets the state of the invoice management information stored in the invoice management database 310 to "confirmed state" (step S1018).

[0132] Next, the output unit 328 of the form management device 300 outputs the confirmed invoice management information to the core system 600 (step S1019).

[0133] The confirmed invoice management information may also be output to the billing destination terminal 500, which is an external system (external device), as data in a predetermined format such as CSV data or XML data, and the billing destination terminal 500 may then output the output data to the core system 600 based on a user operation. Either the invoice information or management information contained in the confirmed invoice management information may be output to the core system 600 or the billing destination terminal 500.

[0134] In this way, in this embodiment, invoice information is obtained based on the QR code included in the form image data input from the billing destination terminal 500, and this invoice information is included in the invoice management information. Therefore, in this embodiment, the information included in the form image can be obtained with high accuracy, and highly accurate information can be provided to the core system 600, which is an external system.

[0135] 10, the input of journal information (management information) and the operation of setting the status of the invoice management information to "confirmed" are described as a series of operations, but this is not limiting. The input of journal information and the operation of confirming the invoice management information may be performed at independent times.

[0136] 10, the operation of outputting the invoice management information to the core system 600 after the state of the invoice management information has been set to "confirmed" has been described as a series of operations, but this is not limiting. After the state of the invoice management information has been set to "confirmed," the output unit 328 of the form management device 300 may receive an instruction from the billing destination terminal 500 to output the invoice management information to the core system 600.

[0137] Next, the display processing of the confirmation screen by the display control unit 327 of the form management device 300 will be described with reference to Fig. 11. Fig. 11 is a flowchart illustrating the processing of displaying the confirmation screen. Fig. 11 shows details of the processing of the display control unit 237 in step S1011 of Fig. 10.

[0138] In the form management device 300 of this embodiment, the display control unit 327 determines whether or not a form ID has been acquired from the form image data (step S1101). If a form ID has not been acquired in step S1101, the process proceeds to step S1104, which will be described later. Note that a case in which a form ID has not been acquired may occur, for example, when reading of the QR code has failed.

[0139] In step S1101, if the form ID is acquired, the display control unit 327 determines whether or not the invoice information associated with the form ID has been acquired by the acquisition unit 325 (step S1102). In step S1102, if the invoice information associated with the form ID has been acquired, the display control unit 327 generates information for displaying a confirmation screen in which editing of the invoice information is prohibited (step S1103), and transmits the information to the billing destination terminal 500.

[0140] In step S1102, if the invoice information corresponding to the document ID has not been obtained, the display control unit 327 performs document recognition using the document recognition unit 326, generates information for displaying a confirmation screen including the invoice information obtained as the recognition result (step S1104), and transmits the information to the billing destination terminal 500.

[0141] A case where invoice information corresponding to the form ID has not been acquired means that invoice information matching the requested form ID and tenant name does not exist in the invoice database 220.

[0142] In this embodiment, the invoice information acquired from the invoice database 220 is displayed on the confirmation screen in a state where editing is prohibited only if invoice information matching the requested report ID and tenant name exists in the invoice database 220.

[0143] Display examples of this embodiment will be described below with reference to Figures 12 and 13. Figure 12 is a diagram showing an example of an invoice creation screen.

[0144] A screen 121 shown in FIG. 12 is an example of a creation screen displayed on the request source terminal 400 in step S902 of FIG.

[0145] Screen 121 includes a display area 122 and operation buttons 123. Display area 122 includes input fields for inputting values ​​of items included in the invoice information. Operation button 123 is an operation button for sending an invoice issuance request to transaction management device 200.

[0146] In this embodiment, when a value is entered in an input field displayed in a display area 122 on a screen 121 and an operation button 123 is operated, form image data showing an invoice image 125 is generated. The invoice image 125 includes invoice information 126 and a QR code 127.

[0147] The position of the QR code 127 in the invoice image 125 is determined by the embedding management information stored in the embedding management database 230 .

[0148] In this embodiment, by embedding a QR code 127 indicating a document ID that identifies the invoice image 125 in the invoice image 125, the invoice information 126 and the document image data indicating the invoice image 125 can be associated based on the document ID.

[0149] Fig. 13 is a diagram showing an example of a confirmation screen. Screen 131 shown in Fig. 13 is an example of a screen displayed on billing destination terminal 500 in step S1011 of Fig. 10. Therefore, billing destination terminal 500 can be said to be an example of a display device that displays invoice management information output from form management device 300.

[0150] The example in FIG. 13 shows an example of a confirmation screen when a form ID is read from the QR code of the form image data, and invoice information corresponding to the read form ID is acquired from the transaction management device 200.

[0151] Screen 131 includes display fields 132 and 133, and operation buttons 137, 138, and 139. A form image indicated by the form image data is displayed in display field 132. In the example of Fig. 13, the form is an invoice, and the form image includes invoice information 126 and a QR code 127.

[0152] Display field 133 displays invoice information corresponding to the form ID read from QR code 127 included in the form image displayed in display field 132, and an input field for journal information.

[0153] Display field 133 includes display fields 134, 135, 136, and 140. Display field 134 displays invoice information 126. Invoice information 126 is information obtained from invoice database 220 based on the form ID read from the QR code. In other words, invoice information 126 is information entered into transaction management device 200 from billing source terminal 400 when creating the invoice. Therefore, in the example of FIG. 13, invoice information 126 is displayed in display field 134 in a state where editing is prohibited.

[0154] 13, the display field 134 is grayed out so that it is easy to understand that editing is prohibited. Note that when editing of the invoice information 126 is prohibited, the display mode of the display field 134 may be any display mode other than grayed out, as long as it is different from the display mode of the other display fields.

[0155] In this embodiment, by changing the display mode of the invoice information depending on how the invoice information displayed on the confirmation screen is acquired, the user of the billing destination terminal 500 can visually understand the accuracy of the invoice information. Therefore, when the user of the billing destination terminal 500 checks, for example, the invoice image displayed in display field 132 with the invoice information displayed in display field 134, the user can easily determine whether or not they need to carefully compare the two.

[0156] Display field 135 displays an input field for journal information. Display field 136 displays the status of invoice confirmation information. In the example of Figure 13, the display in display field 136 indicates that the status of the invoice management information is "draft saved state."

[0157] Display field 140 displays the accuracy rate when comparing invoice information 126 displayed in display field 134 with invoice information stored in invoice database 220. In the example of FIG. 13, invoice information 126 is information stored in invoice database 220 of transaction management device 200. In other words, invoice information 126 is invoice information entered from billing terminal 400. Therefore, in this embodiment, display field 140 displays "100%."

[0158] The operation button 137 is an operation button for enabling editing of the invoice information 126 displayed in the display field 134. In this embodiment, when the operation button 137 is operated on the screen 131, the invoice information 126 displayed in the display field 134 becomes editable.

[0159] Operation button 138 is an operation button for changing the state of the invoice management information from an unprocessed state to a draft saved state. When operation button 138 is operated, the display in display field 136 changes from "unprocessed" to "draft saved."

[0160] Operation button 139 is an operation button for changing the state of the invoice management information to a confirmed state. In this embodiment, when operation button 139 is operated, the display in display field 136 changes from "Save as Draft" to "Confirmed."

[0161] In this embodiment, the invoice management information that has been set to the confirmed state is converted by the output unit 328 into data in a format compatible with the core system 600 and sent to the core system 600.

[0162] In this manner, in this embodiment, the invoice image including the QR code 27, the invoice information acquired based on the QR code 27, and the invoice management information are displayed on one screen.

[0163] In this embodiment, for example, if reading of the QR code 27 fails or if acquisition of invoice information from the invoice database 220 fails, the display field 134 displays the results of the form recognition performed by the form recognition unit 326. At this time, editing of the invoice information displayed in the display field 134 is displayed in a permitted state. In this case, the display field 140 and the operation button 137 do not have to be displayed.

[0164] Furthermore, screen 131 is displayed on billing destination terminal 500, but is not limited to this. Screen 131 may be displayed on the display of form management device 300, for example, and in such a case, screen 131 may be displayed on the display of form management device 300 by the recipient of the invoice operating form management device 300.

[0165] Next, an example of an embedded code according to this embodiment will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of an invoice.

[0166] The invoices 141 to 144 shown in FIGS. 14(A) to 14(D) may be, for example, printed matter or invoice images.

[0167] In the invoice 141 shown in FIG. 14(A), a QR code 141a is added as one of the embedded codes in the lower left area.

[0168] In the invoice 142 shown in Fig. 14(B), a barcode 142a is provided as one of the embedded codes in the lower left area. In the invoice 143 shown in Fig. 14(C), a form ID 1432a is provided as one of the embedded codes in the lower left area. In the invoice 144 shown in Fig. 14(D), a URL (Uniform Resource Locator) 144a indicating the storage location of the form ID is provided as one of the embedded codes in the bottom area.

[0169] In this embodiment, a QR code or a barcode may be included in the invoice image as the embedded code. Also, in this embodiment, a form ID or a URL indicating the storage location of the form ID may be included in the invoice image as the embedded code. Furthermore, a hard-to-see or invisible digital watermark, such as a background pattern watermark or a font watermark, may be included in the invoice image as the embedded code.

[0170] Furthermore, in this embodiment, the information read from the embedded code is the form ID, but this is not limiting. In this embodiment, information other than the form ID may be read from the embedded code. In other words, the embedded code may include information other than the form ID. Specifically, for example, the embedded code may include part or all of the invoice information.

[0171] The embedded code may include the tenant ID or tenant name of the billing destination (tenant B) of the invoice. In this case, in step 1006 of FIG. 10, the reading unit 324 of the form management device 300 reads the embedded code and acquires the tenant ID or tenant name of the billing destination (tenant B) indicated by the embedded code. The acquisition unit 325 of the form management device 300 then compares the acquired tenant ID or tenant name of the billing destination (tenant B) with the tenant ID or tenant name of tenant B identified by the authentication unit 323. If they match, the acquisition unit 325 may send an acquisition request for invoice information including the form ID to the transaction management device 200 (step S1007). If they do not match, the acquisition request may not be sent.

[0172] In this way, in this embodiment, when generating an invoice image, the input invoice information and the invoice image are associated with each other by the form ID, so that when invoice image data representing this invoice image is obtained, the invoice information corresponding to the invoice image can be obtained. Therefore, according to this embodiment, the accuracy of information obtained from the form image can be improved.

[0173] (Second embodiment) The second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that the transaction management device 200 and the form management device 300 are implemented in a single information processing device. Therefore, in the following description of the second embodiment, components having the same functional configuration as those in the first embodiment will be assigned the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

[0174] 15 is a diagram showing an example of the system configuration of a form management system according to the second embodiment. The form management system 100A according to this embodiment includes a form management device 300A and a billing destination terminal 500.

[0175] The form management device 300A includes a supplier management database 210, an invoice database 220, an embedded management database 230, a transaction management unit 240, an invoice management database 310, and a form management unit 320.

[0176] In this embodiment, by implementing the transaction management device 200 and the form management device 300 in a single information processing device, the communication load in the form management system 100A can be reduced.

[0177] (Third embodiment) The third embodiment will be described below with reference to the drawings. The third embodiment differs from the second embodiment in that the document management system 100 includes a billing terminal 400. Therefore, in the following description of the third embodiment, components having the same functional configuration as those in the second embodiment will be assigned the same reference numerals as those used in the description of the second embodiment, and their description will be omitted.

[0178] 16 is a diagram showing an example of the system configuration of a form management system according to the third embodiment. The form management system 100B according to this embodiment includes a form management device 300A, a billing terminal 400, and a billing destination terminal 500. In the form management system 100B, the billing terminal 400 is a first terminal device included in the form management system 100B, and the billing destination terminal 500 is a second terminal device included in the form management system 100B.

[0179] In this embodiment, by including the billing terminal 400 in the document management system 100B, all invoice images based on the invoice information input from the billing terminal 400 are created by the transaction management device 200, and the invoice images contain embedded codes.

[0180] Therefore, all invoices received by the invoice recipient from Tenant A will contain the embedded code, and the form management device 300A can acquire invoice information based on the embedded code from the invoice database 220. Therefore, in this embodiment, the accuracy of information acquired from the form image can be improved.

[0181] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to perform each function described above.

[0182] Additionally, the devices described in the embodiments are merely representative of one of several computing environments for implementing the embodiments disclosed herein.

[0183] In one embodiment, the document management device 300 includes multiple computing devices, such as a server cluster, configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein. Similarly, the document management device 300 may include multiple computing devices configured to communicate with each other.

[0184] Furthermore, the form management device 300 can be configured to share the disclosed processing steps in various combinations. For example, the processes executed by the form management device 300 can be executed by another server device. Similarly, the functions of the form management device 300 can be executed by another server device. Furthermore, the server device and the elements of the other server devices can be integrated into a single server device or can be separated into multiple devices.

[0185] The correspondence table in the statement may be generated by the learning effect of machine learning. Also, by classifying keywords and items that may be included in the description of transaction details using machine learning, it is not necessary to use a correspondence table.

[0186] Here, machine learning is a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates the algorithms necessary for judgments such as data classification from training data that is input in advance, and applies these to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods; the learning method for machine learning is not important.

[0187] Although the present invention has been described above based on the embodiments, the present invention is not limited to the requirements shown in the above embodiments. These requirements can be changed without departing from the spirit of the present invention, and can be appropriately determined depending on the application form. [Explanation of symbols]

[0188] 100, 100A, 100B document management system 200 Transaction Management Device 210 Customer Management Database 220 Invoice Database 230 Embedded Management Database 240 Transaction Management Department 241 Communications Department 242 Input reception section 243 Code Generation Unit 244 Image Generation Unit 245 Embedded part 246 Report Output Unit 247 Output control section 300, 300A document management device 310 Invoice Management Database 320 Document Management Department 321 Communications Department 322 Input reception section 323 Authentication Department 324 Reading unit 325 Acquisition Department 326 Document Recognition Unit 327 Display control unit 328 Output Section 400 Billing terminal (terminal device) 500 Billing terminal (terminal device) 600 Core Systems [Prior art documents] [Patent documents]

[0189] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-051339

Claims

1. a display control unit that displays, on a display device, form management information including form information acquired based on an embedding code included in the form image data and management information for managing the form information; an output unit that receives an instruction to output the form management information and outputs the form management information to an external device; the embedding code includes form identification information for identifying the form information, The display control unit is An information processing device that determines whether or not the document information has been obtained based on the embedded code depending on whether or not document information whose document identification information matches the document identification information indicated by the embedded code exists in a memory unit that stores document information including document identification information, and if it is determined that the document information has been obtained based on the embedded code, displays the document management information on the display device while prohibiting editing of the document information.

2. 2. An information processing device as described in claim 1, further comprising an acquisition unit that refers to a report information storage unit that stores information identifying an input source of report information in association with the report information input by the input source, and acquires the report information corresponding to the information contained in the embedded code.

3. an input receiving unit that receives input of the form information; a code generating unit for generating the embedding code; The information processing apparatus according to claim 1 , further comprising: an embedding unit that embeds the embedding code into form image data generated by using the form information.

4. The display control unit The information processing apparatus according to claim 1 , further comprising: a display unit configured to display the form management information and a form image including the embedded code on the display unit.

5. a form recognition unit that performs form recognition on the form image data, the form recognition unit performs form recognition on the form image data when the form information based on the embedded code is not acquired; The information processing apparatus according to claim 1 , wherein the display control unit causes the display device to display information acquired as a result of the form recognition as form information.

6. The display control unit is 6. The information processing apparatus according to claim 5, wherein a display mode of the form information read from the embedded code is made different from a display mode of the form information acquired as a result of the form recognition.

7. The display control unit is 2 . The information processing apparatus according to claim 1 , wherein, when it is determined that the form information has not been acquired based on the embedded code, the form management information is displayed on the display device in a state in which editing of the form information is permitted.

8. a code generating unit that stores the form information including the embedded code indicating form identification information in a storage unit based on an issuance request from a first terminal device; 2. An information processing device as described in claim 1, which accepts document identification information and a request to obtain document information, determines whether document information whose document identification information matches the document identification information is present in the memory unit, and if document information whose document identification information matches the document identification information is present, determines that document information whose document identification information matches the document identification information based on the embedded code has been obtained.

9. an authentication unit that identifies tenant information associated with a second terminal device based on a login request from the second terminal device; An information processing device as described in claim 8, wherein the memory unit determines whether or not there is document information whose document identification information matches the document identification information and includes item values ​​that match the tenant information, and if there is document information whose document identification information matches the document identification information and includes item values ​​that match the tenant information, it is determined that document information whose document identification information matches the document identification information based on the embedded code has been acquired.

10. An information processing method by an information processing device, comprising: A step of displaying, on a display device, form management information including form information acquired based on an embedding code included in the form image data and management information for managing the form information; receiving an instruction to output the form management information, and outputting the form management information to an external device; the embedding code includes form identification information for identifying the form information, The procedure for displaying the above-mentioned information includes: An information processing method including a step of determining whether or not the document information has been obtained based on the embedded code depending on whether or not document information whose document identification information matches the document identification information indicated by the embedded code is present in a memory unit that stores document information including document identification information, and if it is determined that the document information has been obtained based on the embedded code, displaying the document management information on the display device while prohibiting editing of the document information.

11. A process of displaying, on a display device, form management information including form information acquired based on an embedded code included in the form image data and management information for managing the form information; receiving an instruction to output the form management information, and outputting the form management information to an external device; the embedding code includes form identification information for identifying the form information, The display process includes: A program that causes an information processing device to execute a process that determines whether or not the report information has been obtained based on the embedded code based on whether or not report information whose report identification information matches the report identification information indicated by the embedded code is present in a memory unit that stores report information including report identification information, and if it is determined that the report information has been obtained based on the embedded code, displays the report management information on the display device while prohibiting editing of the report information.

12. An information processing system including an information processing device and a terminal device, The information processing device includes: a display control unit that displays, on the terminal device, form management information including form information acquired based on an embedding code included in the form image data and management information for managing the form information; an output unit that receives an instruction to output the form management information and outputs the form management information to an external device; the embedding code includes form identification information for identifying the form information, The display control unit is determining whether or not the form information has been acquired based on the embedding code depending on whether or not form information whose form identification information matches the form identification information indicated by the embedding code exists in a storage unit that stores form information including form identification information; if it is determined that the form information has been acquired based on the embedding code, displaying the form management information on the terminal device in a state in which editing of the form information is prohibited; The terminal device The information processing system further comprises a display unit that displays form management information in a state in which editing of the form information is prohibited.

13. An information processing system including an information processing device, a first terminal device, and a second terminal device, The first terminal device is A display unit that displays a form information input screen; a communication unit that transmits the form information input on the input screen to the information processing device, The information processing device includes: an input receiving unit that receives input of the form information; a form information storage unit that stores information identifying an input source of form information and form information input by the input source in association with each other; a display control unit that displays, on the second terminal device, form management information including form information acquired from the form information storage unit based on an embedding code included in the form image data input from the second terminal device and management information for managing the form information; an output unit that receives an instruction to output the form management information and outputs the form management information to an external device; the embedding code includes form identification information for identifying the form information, The display control unit is determining whether or not the form information has been acquired based on the embedding code, depending on whether or not form information whose form identification information matches the form identification information indicated by the embedding code exists in a storage unit that stores form information including form identification information; if it is determined that the form information has been acquired based on the embedding code, displaying the form management information on the second terminal device in a state in which editing of the form information is prohibited; The second terminal device The information processing system further comprises a display unit that displays form management information in a state in which editing of the form information is prohibited.

14. An information processing system including a transaction management device, a document management device, a first terminal device, and a second terminal device, The first terminal device is a display unit that displays an input screen for inputting form information included in the form image; a communication unit that transmits the form information input on the input screen to the transaction management device, The transaction management device includes: an input receiving unit that receives input of the form information; a form information storage unit that stores information specifying an input source of form information and form information input by the input source in association with each other; The document management device includes: a display control unit that displays, on the second terminal device, form management information including form information acquired from the form information storage unit based on an embedding code included in the form image data input from the second terminal device and management information for managing the form information; an output unit that receives an instruction to output the form management information and outputs the form management information to an external device; the embedding code includes form identification information for identifying the form information, The display control unit is determining whether or not the form information has been acquired based on the embedding code, depending on whether or not form information whose form identification information matches the form identification information indicated by the embedding code exists in a storage unit that stores form information including form identification information; if it is determined that the form information has been acquired based on the embedding code, displaying the form management information on the second terminal device in a state in which editing of the form information is prohibited; The second terminal device The information processing system further comprises a display unit that displays form management information in a state in which editing of the form information is prohibited.

Images