Information processing device, information processing method, program, and information process 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 apparatus, an information processing method, a program, and an information processing system.

Background Art

[0002] Conventionally, there has been known a technique of displaying an input screen for a form and creating form image data (such as a PDF file) based on the information of the input form. Conventionally, there has also been known a technique of performing character recognition such as OCR (Optical Character Reader) on a form image indicated by form image data, extracting a character string included in the form image, and allowing a user to confirm the extraction result.

Summary of the Invention

Problems to be Solved by the Invention

[0003] In the character recognition of the above-described conventional technology, there are cases where a character string is not correctly extracted, and it is difficult to obtain information included in a form image with high accuracy. For this reason, in the conventional technology, for example, when providing information obtained from a form image to another system, it is difficult to provide highly accurate information.

[0004] The disclosed technology aims to improve the accuracy of the information to be provided.

Means for Solving the Problems

[0005] The disclosed technology is an information processing apparatus including: a display control unit that causes a display device to display form management information including form information obtained 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 instructing output of the form management information and outputs the form management information to an external device.

Effects of the Invention

[0006] The accuracy of the information to be provided can be improved.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

MODE FOR CARRYING OUT THE INVENTION

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

[0009] The form management system 100 of the present embodiment includes a transaction management device 200, a form management device 300, and a terminal device 500. Both the transaction management device 200 and the form management device 300 are information processing devices and can communicate via a network. Further, the terminal device 500 may be, for example, a tablet terminal or the like and may be able to communicate with both the transaction management device 200 and the form management device 300.

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

[0011] At this time, the transaction management device 200 generates an embedding code indicating form identification information for identifying the form and includes it in the form image data. Therefore, in the present 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 embedding code indicating form identification information for identifying the form is attached. Further, the transaction management device 200 holds the form identification information and the form information in association with each other.

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

[0013] Next, the form management device 300 acquires form information that is held in association with the read form identification information from the transaction management device 200. Then, the form management device 300 outputs form management information in which the acquired form information is associated 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] As described above, in the form management system 100 of the present embodiment, when issuing a form, an embedded code including form identification information for identifying the form is generated and embedded in the form image data. Then, when form image data is input from the receiving side of the form, the form management system 100 of the present embodiment acquires form information corresponding to the embedded code included in the form image data.

[0015] Therefore, according to the present embodiment, it is possible to acquire the form information input at the time of form issuance without performing character recognition processing on the form image data input from the receiving side of the form. That is, according to the present embodiment, the accuracy of the information acquired from the form image can be improved.

[0016] Further, in the present embodiment, when providing information included in a form image to the core system 600, which is an external system (external device), it is possible to provide the form information input at the time of form issuance. Therefore, according to the present embodiment, it is possible to provide highly accurate information to the core system 600.

[0017] In the following description, a claim will be described as an example of a form. Therefore, in the following description, the form issuer is the claim issuer, and the receiving side of the form is the claim destination to which the claim is sent.

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

[0019] The billing recipient in the invoice is the trading partner of the invoice issuer. In other words, the billing recipient in the invoice is the trading partner of Tenant A. In the following description of the embodiments, the billing recipient in the invoice may be expressed as Tenant B.

[0020] In the form management system 100 of the present embodiment, the transaction management device 200 includes a trading partner management database 210, an invoice database 220, an embedding management database 230, and a transaction management unit 240, and communicates with the terminal device 400.

[0021] The terminal device 400 is mainly a terminal device used by the invoice issuer (Tenant A). In the following description, the terminal device 400 may be expressed as the claimant terminal 400.

[0022] The trading partner management database 210 stores trading partner information regarding the trading partners of Tenant A. The invoice database 220 stores invoice information regarding the invoices input by Tenant A. The embedding management database 230 stores embedding management information associating the embedding code generated when issuing an invoice with the invoice information.

[0023] The transaction management unit 240 of the present embodiment receives the input of invoice information from the terminal device 400, and generates and outputs form image data including an invoice (form) and an embedding code indicating form identification information for identifying the invoice.

[0024] The form management device 300 of the present embodiment includes 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 mainly a terminal device used by the billing recipient of the invoice. In the following description, the terminal device 500 may be expressed as the recipient terminal 500.

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

[0027] The invoice management database 310 of the present embodiment stores invoice management information in which invoice information obtained from the form image data input from the terminal device 500 is associated with management information for managing the invoice. The invoice information of the present embodiment is information indicating the content of the invoice and is an example of form information indicating the content of the form.

[0028] When form image data is input from the terminal device 500, the form management unit 320 acquires the invoice information corresponding to the embedded code included in the form image data from the transaction management device 200. Further, when the invoice information is not acquired 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 acquires the 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. In addition, 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] Note that the form management system 100 shown in FIG. 1 includes the transaction management device 200, the form management device 300, and the billing destination terminal 500, but the devices included in the form management system 100 are not limited to this. The form management system 100 may include the terminal device 400. Further, the form management system 100 may include the transaction management device 200 and the form management device 300 and may not include the terminal devices 400 and 500.

[0030] Also, in this embodiment, the transaction management device 200 and the form management device 300 are each separate devices, but the present invention is not limited to this. The transaction management device 200 and the form management device 300 may be realized by a single information processing device, or may be realized by three or more information processing devices.

[0031] Hereinafter, with reference to FIG. 2, the hardware configurations of the transaction management device 200 and the form management device 300 of this embodiment will be described. Since the transaction management device 200 and the form management device 300 of this embodiment are general information processing devices, in FIG. 2, the hardware configuration of the form management device 300 will be described 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. In FIG. 2, the hardware configuration of the form management device 300, which is a second information processing device, is shown as an example.

[0033] The form management device 300 is constructed by a computer, and as shown in FIG. 2, includes a CPU 301, a ROM 302, a RAM 303, an HD 304, an 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] Among these, the CPU 301 controls the operation of the entire form management device 300. The ROM 302 stores programs used to drive the CPU 301 such as IPL. The RAM 303 is used as the work area of the CPU 301. The HD 04 stores various data such as programs. The HDD controller 305 controls the reading or writing of various data to and from the HD 304 according to the control of the CPU 301. The display 306 displays various information such as a cursor, menu, window, characters, or images. The external device connection I / F 308 is an interface for connecting various external devices. The external devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, etc. The network I / F 309 is an interface for performing data communication using a communication network. The bus line B1 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 301 shown in FIG. 2.

[0035] Also, the keyboard 311 is a type of input means having a plurality of keys for inputting characters, numerical values, 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 the reading or writing of various data to and from the DVD-RW 313 as an example of a removable recording medium. Note that it is not limited to DVD-RW, and it may be DVD-R or the like. The media I / F 316 controls the reading or writing (storage) of data to and from the recording medium 315 such as a flash memory.

[0036] Next, with reference to FIG. 3, the hardware configurations of the terminal device (claim source terminal) 400 and the terminal device (claim destination terminal) 500 of the present embodiment will be described. Since the terminal device 400 and the terminal device 500 of the present embodiment are general terminal devices, in FIG. 3, the hardware configuration of the terminal device 500 will be described as an example of the hardware configuration of the terminal device.

[0037] FIG. 3 is a diagram showing an example of the hardware configuration of the terminal device. In FIG. 3, the hardware configuration of the destination terminal 500 is shown 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 imaging device I / F 506, an acceleration / azimuth sensor 507, a media I / F 509, and a GPS receiver 511.

[0039] Among these, the CPU 501 is an arithmetic processing unit that controls the operation of the entire terminal device 500. The ROM 502 stores programs used for driving the CPU 501 such as the CPU 501 and IPL. The RAM 503 is used as a work area for the CPU 501. The EEPROM 504 reads or writes (stores) various data such as smartphone programs according to the control of the CPU 501. The ROM 502, the RAM 503, and the EEPROM 504 are an example of the storage device of the terminal device 500.

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

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

[0042] In addition, the terminal device 500 includes a long-distance communication circuit 512, an antenna 512a of the long-distance communication circuit 512, a CMOS sensor 513, an imaging device 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] Among 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 a subject according to the control of the CPU 501 to obtain image data. The imaging device 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 sounds such as music and voices. The audio input / output I / F 517 is a circuit that processes the input / output of audio signals between the microphone 515 and the speaker 516 according to the control of the CPU 501.

[0044] The display 518 is a type of display means such as liquid crystal or organic EL (Electro Luminescence) 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-distance 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 for operating the terminal device 500 when the user presses the display 518. The display 518 is an example of the display unit of the terminal device 500.

[0045] Next, with reference to FIGS. 4 to 6, each database of the transaction management device 200 will be described. FIG. 4 is a diagram showing an example of a business partner management database.

[0046] The business partner management database 210 of this embodiment is provided, for example, for each tenant A. Further, the business partner management database 210 of this embodiment includes items of information 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, in the business partner management database 210, information including the values of items such as name, address, telephone number, email address, and name of person in charge may be expressed as business partner information. The tenant ID and tenant name are information for identifying tenant A. The value of the item "name" indicates the name of the business partner (claimant), and the values of the items "address", "telephone number", "email address", and "name of person in charge" respectively indicate the address, telephone number, email address of the claimant, and the name of the person in charge responsible for the transaction.

[0048] Note that the items of information included in the business partner information are not limited to the example shown in FIG. 4. The items of information included in the business partner information may not include all the items shown in FIG. 4, or may include items other than those shown in FIG. 4.

[0049] The business partner information of this embodiment is stored in the business partner management database 210 when the transaction management device 200 receives an input from the claimant terminal 400.

[0050] FIG. 5 is a diagram showing an example of the invoice database. The invoice database 220 of this embodiment may be provided for each tenant A in the same manner as the business partner management database 210.

[0051] The invoice database 220 includes items of information such as invoice ID, claimant, amount billed, billing date, payment due date, details information, transfer destination information, etc., and each item is associated with the tenant ID and tenant name of tenant A.

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

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

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

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

[0056] The value of the item "billing destination" indicates the name of the billing destination of the invoice specified by the invoice ID. The values of the items "billing amount", "billing date", and "payment due date" respectively indicate the billing amount, billing date, and payment due date described in the invoice.

[0057] The item "detail information" is associated with items indicating the breakdown of the billing amount, such as the items "product code", "product name", "quantity", etc. The value of the item "detail information" indicates the breakdown of the billing amount.

[0058] The item "transfer destination information" is associated with items indicating the transfer destination of the billing amount, such as the items "bank name", "branch", "account type", "account number", etc. The value of the item "transfer destination information" indicates the transfer destination of the billing amount.

[0059] Note that the items of the information included in the invoice information are not limited to the example shown in FIG. 5. The items of the information included in the invoice information may not include all the items shown in FIG. 5, or may include items other than those shown in FIG. 5.

[0060] FIG. 6 is a diagram showing an example of an embedded management database. The embedded management database 230 of the present embodiment includes, as information items, an embedding position (upper left), an embedding position (lower right), an embedding type, embedding content, an encryption key, and the like. In the following description, information including the values of each item in the embedded management database 230 may be expressed as embedded information. The embedded information is information that has been stored in the embedded management database 230 in advance by Tenant A and is referred to when the form management apparatus 300 embeds an embedded code.

[0061] The values of each of the item “embedding position (upper left)” and the item “embedding position (lower right)” are information for specifying the position in the form image where the embedded code is embedded. Specifically, the values of each of the item “embedding position (upper left)” and the item “embedding position (lower right)” indicate, for example, the coordinates indicating the position of the upper left vertex of the QR code (registered trademark) in the form image and the coordinates indicating the position of the lower right vertex of the QR code (registered trademark) in the form image.

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

[0063] The value of the item “encryption key” may be referred to when the form management apparatus 300 reads the form ID from the embedded code.

[0064] Note that the embedded information may not include an encryption key. The encryption key may be referred to, for example, when form image data indicating a bill is transmitted to the bill terminal 500 via a network or the like.

[0065] Also, in the present embodiment, the embedded management database 230 is provided in the transaction management apparatus 200, but is not limited thereto.

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

[0067] Next, the invoice management database 310 of the document management device 300 will be described. FIG. 7 is a diagram showing an example of the invoice management database.

[0068] The invoice management database 310 of the present embodiment is provided for each tenant B. Further, the invoice management database 310 includes, as information items, a document ID, a billing source, a billing amount, a payment due date, details information, journal information, etc.

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

[0070] The item "journal information" is associated with various items related to journal entries, and the value of the item "journal information" includes various items related to journal entries and the values of those items. The journal information is information input to the document management device 300 by the billing terminal 500, which is the receiving-side terminal that has received the invoice, and is management information for managing the invoice. In other words, the journal information is management information for managing the invoice, which is input on the receiving side of the document.

[0071] In the present embodiment, in the invoice management database 310, the information in which the invoice information and the management information are associated may be expressed as invoice management information.

[0072] In other words, the invoice management information is an example of document management information in which the document information indicating the content of the document and the management information for managing the document are associated.

[0073] In the example of FIG. 7, journal information is shown as the management information of the invoice, but the management information may include information other than the journal information. Specifically, for example, the management information may include information related to payment, such as account information of the transfer destination of the invoice amount and the date of executing the transfer. Also, when the document is a delivery note or the like, the management information may include, for example, purchase information or the like.

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

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

[0076] In this embodiment, as the state of the invoice management information, there are four states: an unprocessed state, a draft save state, a finalized state, and an externally output state. Each state is as follows.

[0077] · Unprocessed state (state 1) Immediately after the invoice information is acquired, and the state where the input of journal information or the like has not been performed.

[0078] · Draft save state (state 2) In the middle of operations such as confirmation of the invoice management information, and the state before the invoice management information is finalized.

[0079] · Finalized state (state 3) The state where the operations such as confirmation of the invoice management information are completed and the information is stored in the invoice management database 310 as finalized information. · Externally output state (state 4) The state where the output of the invoice management information to the core system 600 is completed.

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

[0081] First, the functions of the transaction management device 200 will be described. The transaction management unit 240 of the transaction management device 200 in this embodiment includes a communication unit 241, an input reception unit 242, a code generation unit 243, an image generation unit 244, an embedding unit 245, an invoice 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 claimant terminal 400.

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

[0084] The image generation unit 244 generates image data (invoice image data) indicating the invoice based on the invoice information input from the claimant terminal 400.

[0085] The embedding unit 245 embeds the QR code generated by the code generation unit 243 into the invoice image data to generate invoice image data including the embedded code.

[0086] The invoice output unit 246 outputs the invoice image data including the QR code. The invoice output unit 246 in this embodiment may, for example, transmit the invoice image data including the QR code to an image forming device or the like and output the invoice image data as a printed matter. Further, the invoice output unit 246 may transmit the invoice image data including the QR code to the respondent terminal 500.

[0087] When the output control unit 247 receives a request to acquire invoice information from the form management device 300, it determines whether to output (transmit) the received invoice information to the form management device 300. If it determines to output, it outputs the invoice to the form management device 300.

[0088] Next, the functions of the form management device 300 will be described. The form management unit 320 of the form management device 300 in this embodiment includes 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 terminal 500.

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

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

[0092] When the reading unit 324 of the form management device 300 reads the form ID, the communication unit 321 transmits a request to acquire invoice information including the read form ID and information (tenant name) for specifying the billing destination of the invoice to the transaction management device 200.

[0093] The acquisition unit 325 requests the transaction management device 200 to acquire 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 form recognition unit 326 determines whether the invoice information has been acquired by the acquisition unit 325. When the acquisition unit 325 fails to acquire the invoice information, the form recognition unit 326 performs form recognition on the input form image data and uses the recognition result as the invoice information.

[0095] The case where the invoice information is not acquired includes cases where the form image data is created by a system other than the form management system 100 and does not include a QR code, or cases where the QR code reading fails.

[0096] In addition, the form recognition in this embodiment is a process of extracting the name (item name) of an item included in the form image indicated by the form image data and the value (item value) of this item, converting the item and the item value into text data, and associating them.

[0097] The display control unit 327 controls the display on the billing terminal 500. Specifically, the display control unit 327 causes the billing 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 backbone system 600 or the like.

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

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

[0101] Next, with reference to FIGS. 9 to 11, the operation of the form management system 100 of the present embodiment will be described. FIG. 9 is a first sequence diagram for explaining the operation of the form management system of the first embodiment. In FIG. 9, the operation of the form management system 100 until an invoice is issued is shown.

[0102] In the form management system 100 of the present embodiment, in response to an operation from Tenant A, the claimant terminal 400 transmits an invoice creation request to the transaction management device 200 (step S901).

[0103] When the transaction management device 200 receives the invoice creation request by the input reception unit 242, it transmits a display instruction for the invoice creation screen to the claimant terminal 400 (step S903). When the claimant terminal 400 receives the display instruction for the creation screen, the display unit 430 displays the invoice creation screen on the display (step S903). The details of the creation screen will be described later.

[0104] Subsequently, the claimant terminal 400 receives the input of invoice information from Tenant A (step S904). Subsequently, the claimant terminal 400 receives the input of an invoice issuance instruction from Tenant A (step S905).

[0105] When the claimant terminal 400 receives the invoice issuance instruction, 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 for identifying Tenant A that uses the claimant terminal 400. The information for identifying Tenant A is, for example, a tenant ID, a tenant name, or the like.

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

[0107] Subsequently, the transaction management device 200 generates image data of an invoice indicating the invoice based on the received invoice information by the image generation unit 244 (step S908). In other words, the image generation unit 244 generates form image data.

[0108] Subsequently, the transaction management device 200 refers to the embedding management database 230 by the embedding unit 245 and the code generation unit 243, and embeds a QR code at the position indicated by the embedding management information in the form image (step S909).

[0109] Subsequently, the transaction management device 200 issues an invoice including the QR code by the form output unit 246 (step S910). In other words, the transaction management device 200 outputs form image data including the QR code by the form output unit 246.

[0110] FIG. 10 is a second sequence diagram for explaining the operation of the form management system according to the first embodiment. FIG. 10 shows the operation until the invoice management information is output to the core system 600 in the form management system 100.

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

[0112] The login request includes the input login information and the like.

[0113] When the form management device 300 receives the login request by the input reception unit 322, the authentication unit 323 performs authentication, and based on the login information and the like received together with the login request, for example, identifies the tenant name of the invoice recipient (tenant B) corresponding to the login information (step S1003).

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

[0115] Note that the invoice image data uploaded from the claimant terminal 500 may be invoice image data including a QR code transmitted from the claimant terminal 400 to the claimant terminal 500. Further, the invoice image data uploaded from the claimant terminal 500 may be invoice image data generated by reading, by scanning or the like, an invoice output as a printed matter in response to a request for issuing an invoice from the claimant terminal 400.

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

[0117] Subsequently, the invoice management device 300 transmits, by the acquisition unit 325, a request for acquiring invoice information including the invoice 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 invoice ID and the tenant name of tenant B, the output control unit 247 determines whether there is invoice information in the invoice database 220 in which the value of the item "invoice ID" matches the received invoice ID and the value of the item "claimant" matches the received tenant name (step S1008).

[0119] In the example of FIG. 10, the operation when there is invoice information in the invoice database 220 in which the value of the item "invoice ID" matches the received invoice ID and the value of the item "claimant" matches the received tenant name is shown.

[0120] Subsequent to step S1008, the transaction management device 200 extracts, by the output control unit 247, invoice information that matches the received invoice ID and tenant name from the invoice database 220 in terms of the values of the item "form ID" and the item "invoice recipient", and outputs it to the form management device 300 (step S1009).

[0121] In addition, when there is no invoice information corresponding to the invoice database 220, the output control unit 247 may send an error notification or the like to the form management device 300.

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

[0123] Subsequently, the form management device 300 may perform the processing after step S1011 based on the acquired invoice information, or determine whether the value of the item "invoice recipient" included in the acquired invoice information matches the tenant name of tenant B specified by the authentication unit 323. If they match, the processing after step S1011 is executed; if they do not match, control may be performed to display an error screen or the like.

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

[0125] Next, when the invoice management device 300 acquires the invoice information by the acquisition unit 325, 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). Note that the display control unit 327 may vary the display mode of the invoice information on the confirmation screen according to the way the invoice information is acquired. The processing of the display control unit 327 and the details of the confirmation screen will be described later.

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

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

[0129] When the invoice management device 300 receives the journal information, it stores it in the invoice management database 310 as invoice management information associating the invoice information and the journal information (step S1015).

[0130] Subsequently, when the billing destination terminal 500 receives an operation to set the status of the billing statement management information to the "confirmed status" (step S1016), it sends a confirmation instruction for the billing statement management information to the form management device 300 (step S1017).

[0131] When the form management device 300 receives the confirmation instruction for the billing statement management information, it sets the status of the billing statement management information stored in the billing statement management database 310 to the "confirmed status" (step S1018).

[0132] Subsequently, the form management device 300 outputs the confirmed billing statement management information to the core system 600 through the output unit 328 (step S1019).

[0133] Alternatively, the confirmed billing statement management information may be output as data in a predetermined format such as CSV data or XML data to the billing destination terminal 500, which is an external system (external device), and the billing destination terminal 500 may cause the output data to be output to the core system 600 based on a user operation. Note that either the billing statement information or the management information included in the confirmed billing statement management information may be output to the core system 600 or the billing destination terminal 500.

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

[0135] Note that in the example of FIG. 10, the input of the journal information (management information) and the operation to set the status of the billing statement management information to the "confirmed status" have been described as a series of operations, but the present invention is not limited thereto. The input of the journal information and the operation to confirm the billing statement management information may be performed at independent timings.

[0136] Also, in the example of FIG. 10, after the status of the claim management information is set to the "confirmed status", the operation of outputting this claim management information to the core system 600 has been described as a series of operations, but it is not limited to this. The output unit 328 of the form management device 300 may receive an operation instruction to output the claim management information from the claim terminal 500 after the status of the claim management information is set to the "confirmed status", and then output the claim management information to the core system 600.

[0137] Next, with reference to FIG. 11, the display process of the confirmation screen by the display control unit 327 of the form management device 300 will be described. FIG. 11 is a flowchart for explaining the process of displaying the confirmation screen. In FIG. 11, the details of the process of the display control unit 237 in step S1011 of FIG. 10 are shown.

[0138] In the form management device 300 of the present embodiment, the display control unit 327 determines whether a form ID has been acquired from the form image data (step S1101). In step S1101, if the form ID has not been acquired, the process proceeds to step S1104 described later. Note that the case where the form ID is not acquired is, for example, a case where the reading of the QR code fails.

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

[0140] In step S1102, if the claim information corresponding to the form ID has not been acquired, the display control unit 327 performs form recognition by the form recognition unit 326, and generates information for displaying a confirmation screen including the claim information acquired as the recognition result (step S1104), and transmits it to the claim terminal 500.

[0141] The case where the invoice information corresponding to the form ID has not been acquired means that there is no invoice information in the invoice database 220 that matches the acquired form ID and tenant name.

[0142] In this embodiment, as described above, only when there is invoice information in the invoice database 220 that matches the acquired form ID and tenant name, the invoice information acquired from the invoice database 220 is displayed on the confirmation screen in a state where editing is prohibited.

[0143] Hereinafter, with reference to FIGS. 12 and 13, a display example of this embodiment will be described. FIG. 12 is a diagram showing an example of an invoice creation screen.

[0144] The screen 121 shown in FIG. 12 is an example of a creation screen displayed on the claimant terminal 400 in step S902 of FIG. 9.

[0145] The screen 121 includes a display area 122 and operation buttons 123. The display area 122 includes input fields for inputting values of items included in the invoice information. The operation buttons 123 are operation buttons for sending an invoice issuance request to the transaction management device 200.

[0146] In this embodiment, on the screen 121, when a value is input into the input field displayed in the display area 122 and the operation buttons 123 are operated, form image data showing the 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, in this way, by embedding the QR code 127 indicating the form ID for specifying the invoice image 125 in the invoice image 125, the invoice information 126 and the form image data showing the invoice image 125 can be associated based on the form ID.

[0149] FIG. 13 is a diagram showing an example of a confirmation screen. The screen 131 shown in FIG. 13 shows an example of the screen displayed on the claimant terminal 500 in step S1011 of FIG. 10. Therefore, it can be said that the claimant terminal 500 is an example of a display device that displays the bill management information output from the bill management device 300.

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

[0151] The screen 131 includes a display column 132, a display column 133, and operation buttons 137, 138, and 139. A bill image indicated by the bill image data is displayed in the display column 132. In the example of FIG. 13, the bill is a bill, and the bill image includes bill information 126 and a QR code 127.

[0152] The display column 133 displays the bill information corresponding to the bill ID read from the QR code 127 included in the bill image displayed in the display column 132 and an input column for journal entry information.

[0153] The display column 133 includes display columns 134, 135, 136, and 140. The bill information 126 is displayed in the display column 134. The bill information 126 is information acquired from the bill database 220 based on the bill ID read from the QR code. In other words, the bill information 126 is information input from the claimant terminal 400 to the transaction management device 200 at the time of creating the bill. Therefore, in the example of FIG. 13, in the display column 134, the bill information 126 is displayed in a state where editing is prohibited.

[0154] Specifically, in FIG. 13, the display column 134 is grayed out so that it can be easily grasped that editing is prohibited. Incidentally, the display mode of the display column 134 only needs to be different from that of other display columns when editing of the bill information 126 is prohibited, and may be a display mode other than graying out.

[0155] In this embodiment, in this way, by varying the display mode of the invoice information displayed on the confirmation screen according to the method of acquiring the invoice information, the user of the billing terminal 500 can visually grasp the accuracy of the invoice information. Therefore, the user of the billing terminal 500 can easily determine whether it is necessary to carefully compare the invoice image displayed in the display column 132 and the invoice information displayed in the display column 134 when comparing them.

[0156] The display column 135 displays an input column for journal entry information. The display column 136 displays the status of the invoice confirmation information. In the example of FIG. 13, it can be seen from the display in the display column 136 that the status of the invoice management information is the "draft saved state".

[0157] The display column 140 displays the correct rate when the invoice information 126 displayed in the display column 134 is compared with the invoice information stored in the invoice database 220. In the example of FIG. 13, the invoice information 126 is the information stored in the invoice database 220 of the transaction management device 200. In other words, the invoice information 126 is the invoice information input from the billing source terminal 400. Therefore, in this embodiment, "100%" is displayed in the display column 140.

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

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

[0160] The operation button 139 is an operation button for setting the status of the claim management information to the finalized status. In the present embodiment, when the operation button 139 is operated, the display in the display column 136 changes from "Draft Save" to "Finalize".

[0161] In addition, in the present embodiment, the claim management information that has been set to the finalized status is converted by the output unit 328 into data in a format corresponding to the core system 600 and transmitted to the core system 600.

[0162] As described above, in the present embodiment, the claim image including the QR code 27, the claim information obtained based on the QR code 27, and the management information of the claim are displayed on one screen.

[0163] In addition, in the present embodiment, for example, when the reading of the QR code 27 fails or when the acquisition of the claim information from the claim database 220 fails, the result of the form recognition performed by the form recognition unit 326 is displayed in the display column 134. At this time, the editing of the claim information displayed in the display column 134 is displayed in a permitted state. Also, at this time, the display column 140 and the operation button 137 may not be displayed.

[0164] Also, although the screen 131 is shown as being displayed on the claim terminal 500, it is not limited thereto. The screen 131 may be displayed, for example, on a display of the form management device 300 or the like. In this case, the receiving side of the claim may operate the form management device 300 so that the screen 131 is displayed on the display of the form management device 300.

[0165] Next, with reference to FIG. 14, an example of the embedded code in the present embodiment will be described. FIG. 14 is a diagram showing an example of a claim.

[0166] The claims 141 to 144 shown in FIGS. 14(A) to 14(D) may be, for example, those output as a printed matter or may be a claim image.

[0167] The claim form 141 shown in FIG. 14(A) has a QR code 141a assigned as one of the embedded codes in the lower left region.

[0168] Also, in the claim form 142 shown in FIG. 14(B), a barcode 142a is assigned as one of the embedded codes in the lower left region. In the claim form 143 shown in FIG. 14(C), a form ID 1432a is assigned as one of the embedded codes in the lower left region. In the claim form 144 shown in FIG. 14(D), a URL (Uniform Resource Locator) 144a indicating the storage destination of the form ID is assigned as one of the embedded codes in the lower end region.

[0169] In this embodiment, as described above, a QR code or a barcode may be included in the claim form image as an embedded code. Also, in this embodiment, a form ID or a URL indicating the storage destination of the form ID may be included in the claim form image as an embedded code. Furthermore, as an embedded code, an invisible or semi-invisible electronic watermark such as a pattern watermark or a font watermark may be included in the claim form image.

[0170] Moreover, in this embodiment, the information read from the embedded code is taken as the form ID, but it is not limited to this. 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 claim form information.

[0171] The embedded code may also include the tenant ID or tenant name of the billing destination (tenant B) in the claim form. 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. Then, the acquisition unit 325 of the form management device 300 compares the acquired tenant ID or tenant name of the billing destination (tenant B) with the tenant ID or tenant name of tenant B specified by the authentication unit 323. When they match, a request to acquire claim form information including the claim form ID is sent to the transaction management device 200 (step S1007). When they do not match, control may be performed so that the acquisition request is not sent.

[0172] In this way, in the present embodiment, when generating the claim form image, by associating the input claim form information with the claim form image using the claim form ID, when acquiring the claim form image data indicating this claim form image, the claim form information corresponding to the claim form image can be acquired. Therefore, according to the present embodiment, the accuracy of the information acquired from the form image can be improved.

[0173] (Second Embodiment) Hereinafter, with reference to the drawings, the second embodiment will be described. The second embodiment is different from the first embodiment in that the transaction management device 200 and the form management device 300 are realized by one information processing device. Therefore, in the following description of the second embodiment, those having the same functional configuration as in the first embodiment are given the same reference numerals as those used in the description of the first embodiment, and the description thereof is omitted.

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

[0175] The form management device 300A has a business partner management database 210, a claim form database 220, an embedded management database 230, a transaction management unit 240, a claim form management database 310, and a form management unit 320.

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

[0177] (Third Embodiment) Hereinafter, with reference to the drawings, the third embodiment will be described. The third embodiment is different from the second embodiment in that the claimer terminal 400 is included in the document management system 100. Therefore, in the following description of the third embodiment, components having the same functional configuration as those in the second embodiment are given the same reference numerals as those used in the description of the second embodiment, and the description thereof is omitted.

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

[0179] In this embodiment, by including the claimer terminal 400 in the document management system 100B, all the claim form images based on the claim form information input from the claimer terminal 400 will be created by the transaction management device 200, and the claim form images will include embedded codes.

[0180] Therefore, all the claim forms received by the recipient of the claim form from Tenant A will include embedded codes, and the document management device 300A can obtain the claim form information based on the embedded codes from the claim form database 220. Therefore, in this embodiment, the accuracy of the information obtained from the document image can be improved.

[0181] Each function of the embodiments described above can be realized by one or more processing circuits. Here, the "processing circuit" in this specification refers to a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit) designed to execute each function described above, a DSP (digital signal processor), an FPGA (field programmable gate array), and devices such as conventional circuit modules.

[0182] Also, the device groups described in the embodiments merely represent one of the multiple computing environments for implementing the embodiments disclosed in this specification.

[0183] In one embodiment, the form management device 300 includes a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link including a network or a shared memory, and implement the processes disclosed in this specification. Similarly, the form management device 300 can include a plurality of 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 process executed by the form management device 300 can be executed by other server devices. Similarly, the functions of the form management device 300 can be executed by other server devices. Also, the elements of the server device and other server devices may be combined into one server device or divided into multiple devices.

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

[0186] Here, machine learning is a technology for enabling a computer to acquire learning capabilities similar to those of humans. It refers to a technology in which a computer autonomously generates algorithms necessary for judgments such as data identification from pre-loaded learning data and applies this to new data for prediction. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning. Furthermore, a learning method combining these learning methods may also be used, and the learning method for machine learning is not limited.

[0187] As described above, the present invention has been described based on each embodiment, but the present invention is not limited to the requirements shown in the above embodiments. Regarding these points, it can be changed within the range that does not deviate from the gist of the present invention, and can be appropriately determined according to its application form.

Explanation of Reference Numerals

[0188] 100, 100A, 100B Form Management System 200 Transaction Management Device 210 Customer Management Database 220 Invoice Database 230 Embedding Management Database 240 Transaction Management Unit 241 Communication Unit 242 Input Reception Unit 243 Code Generation Unit 244 Image Generation Unit 245 Embedding Unit 246 Form Output Unit 247 Output Control Unit 300, 300A Form Management Device 310 Invoice Management Database 320 Form Management Unit 321 Communication Unit 322 Input Reception Unit 323 Authentication Unit 324 Reading Unit 325 Acquisition Unit 326 Form Recognition Unit 327 represents the control unit 328 represents the output unit 400 represents the claimant terminal (terminal device) 500 represents the respondent terminal (terminal device) 600 represents the backbone system

Prior Art Documents

Patent Documents

[0189]

Patent Document 1

Claims

1. A display control unit that causes a display device to display invoice management information including invoice information acquired based on an embedded code included in invoice image data and management information for managing the invoice information; An information processing apparatus comprising: an output unit that receives an operation instructing output of the invoice management information and outputs the invoice management information to an external device.

2. The information processing apparatus according to claim 1, further comprising: an acquisition unit that refers to an invoice information storage unit that stores, in association with each other, information identifying the input source of invoice information and the invoice information input by the input source, and acquires the invoice information corresponding to the information included in the embedded code.

3. An input reception unit that receives input of the invoice information; A code generation unit that generates the embedded code; An embedding unit that embeds the embedded code in invoice image data generated using the invoice information, wherein the embedded code includes invoice identification information for identifying the invoice information, according to the information processing apparatus according to claim 1 or 2.

4. The display control unit causes the display device to display the invoice management information and an invoice image including the embedded code, according to the information processing apparatus according to any one of claims 1 to 3.

5. An invoice recognition unit that performs invoice recognition on the invoice image data, wherein the invoice recognition unit performs invoice recognition on the invoice image data when the invoice information based on the embedded code is not acquired, and the display control unit causes the display device to display, as invoice information, the information acquired as a result of the invoice recognition, according to the information processing apparatus according to any one of claims 1 to 4.

6. The display control unit causes the display device to display the invoice information read from the embedded code and the invoice information acquired as a result of the invoice recognition in different display modes, according to the information processing apparatus according to claim 5.

7. The display control unit causes the display device to display the invoice information acquired based on the embedded code in a state where editing of the invoice information is prohibited, according to the information processing apparatus according to any one of claims 1 to 6.

8. An information processing method by an information processing apparatus, the information processing apparatus causing a display device to display invoice management information including invoice information acquired based on an embedded code included in invoice image data and management information for managing the invoice information, and receiving an operation instructing output of the invoice management information and outputting the invoice management information to an external device.

9. Causing a display device to display form management information including form information obtained based on an embedded code included in form image data and management information for managing the form information. A program that causes an information processing device to execute a process of receiving an operation instruction to output the form management information and outputting the form management information to an external device.

10. An information processing system including an information processing device and a terminal device, wherein the information processing device has a display control unit that causes the terminal device to display form management information including form information obtained 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 instruction to output the form management information and outputs the form management information to an external device. The terminal device has a display unit that displays the form management information.

11. An information processing system including an information processing device, a first terminal device, and a second terminal device, wherein the first terminal device has a display unit that displays an input screen for form information; and a communication unit that transmits the form information input to the input screen to the information processing device. The information processing device has an input reception unit that receives the input of the form information; a form information storage unit that stores, in association with each other, information identifying the input source of the form information and the form information input by the input source; a display control unit that causes the second terminal device to display form management information including form information obtained from the form information storage unit based on an embedded code included in form image data input from the second terminal device and management information for managing the form information; and an output unit that receives an operation instruction to output the form management information and outputs the form management information to an external device. The second terminal device has a display unit that displays the form management information.

12. An information processing system including a transaction management device, a form management device, a first terminal device, and a second terminal device, wherein the first terminal device has a display unit that displays an input screen for form information included in a form image; and a communication unit that transmits the form information input to the input screen to the transaction management device. The transaction management device has an input reception unit that receives the input of the form information; and a form information storage unit that stores, in association with each other, information identifying the input source of the form information and the form information input by the input source. The invoice management device A display control unit that causes the second terminal device to display invoice management information including invoice information acquired from the invoice information storage unit and management information for managing the invoice information, based on an embedded code included in the invoice image data input from the second terminal device; An output unit that receives an operation instruction to output the invoice management information and outputs the invoice management information to an external device; The second terminal device An information processing system having a display unit that displays the invoice management information.

Images