Transaction management system, transaction management method, document management device, document management program

Abstract

To facilitate the management of information.MEANS FOR SOLVING THE PROBLEM: A transaction management system includes a transaction management device, a document management device, and a terminal device, in which the transaction management device, the document management device, and the terminal device are connected via a network. The transaction management device has: a display control unit that displays a work screen on the terminal device for performing work using ledger sheet information described on a ledger sheet; and an output unit that outputs at least part of the ledger sheet information and ledger sheet image data which is an image of the ledger sheet, to the document management device when an operation to complete the work using the ledger sheet information is received on the work screen. The document management device has a storage control unit that stores the at least part of the ledger sheet information and the ledger sheet image data, received from the transaction management device in a document management storage unit.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present invention relates to a transaction management system, a transaction management method, Document a management device, Document and a management program.

Background Art

[0002] Conventionally, a technique for extracting and managing form information described in a form from a form image has been known.

Summary of the Invention

Problems to be Solved by the Invention

[0003] When managing a form as electronic form information, for example, it is necessary to store the form information so as to satisfy predetermined requirements such as legal requirements stipulated in the Electronic Bookkeeping Law, and the management is laborious.

[0004] The disclosed technique has been made in view of the above circumstances, and aims to facilitate information management.

Means for Solving the Problems

[0005] The disclosed technique is a transaction management system including a transaction management device and a document management device and including aims at The transaction management device has a display control unit that causes a terminal device to display a work screen for performing work using form information described in a form, and when an operation for completing work using the form information is received on the work screen, at least a part of the form information at the edge and form image data that is an image of the form and includes at least a part of the form information including item values of specific items required as predetermined requirements are output to the document management device. The document management device has a storage control unit that stores at least a part of the form information received from the transaction management device and the form image data in a document management storage unit 、 having and the storage control unit stores, in the document management storage unit, document management information that associates at least a part of the form information with history information indicating a history of the form being handled, and includes identification information for identifying the document management information this.

Effects of the Invention

[0006] Information management can be facilitated.

Brief Description of 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

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

MODE FOR CARRYING OUT THE INVENTION

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

[0009] The transaction management system 100 of this embodiment includes a transaction management device 200, a document management device 300, and terminal devices 400-1, 400-2, ···, 400-n. In the following description, when not distinguishing each of the terminal devices 400-1, 400-2, ···, 400-n, they are represented as the terminal device 400.

[0010] In the transaction management system 100 of this embodiment, the transaction management device 200, the document management device 300, and the terminal device 400 are connected via a network.

[0011] In the transaction management system 100, the transaction management device 200 may be connected to a backbone system via a network, for example. The backbone system is, for example, a system that performs processing corresponding to a specific application using the information processed by the transaction management device 200 of this embodiment. Note that the backbone system may be, for example, software that executes processing corresponding to a specific application.

[0012] Further, the transaction management device 200 of this embodiment includes a transaction management database 240 and a transaction management unit 250, and acquires, for example, image data scanned by an image forming device or the like, or image data uploaded from the terminal device 400.

[0013] Here, the image data acquired by the transaction management device 200 may be image data of a form. In the following description, an image of a form is referred to as a form image, and image data indicating the form image is referred to as form image data.

[0014] In addition, when the transaction management device 200 acquires the form image data, the transaction management unit 250 performs form recognition processing on the form image data and extracts the information contained in the form. In the following description, the information extracted from the form is referred to as form information.

[0015] Also, when the transaction management device 200 receives form management information, which is information for managing form information, from the terminal device 400, the transaction management unit 250 associates the form information with the form management information to obtain transaction management information and stores it in the transaction management database 240.

[0016] Further, in the transaction management device 200 of the present embodiment, at the timing when the content of the transaction management information is determined by the transaction management unit 250, information including a part of the transaction management information is transmitted to the document management device 300.

[0017] Here, the information including a part of the transaction management information is information that satisfies the legal requirements stipulated by the Electronic Book Preservation Law.

[0018] The document management device 300 of the present embodiment includes a document management database 340 and a document management unit 350. When the document management device 300 receives information including a part of the transaction management information from the transaction management device 200, the document management unit 350 associates history information for managing the history of handling the form corresponding to the received information with the information including a part of the transaction management information to manage the document information. Then, the document management unit 350 stores the document information in the document management database 340.

[0019] Thereby, in the document management device 300 of the present embodiment, the form information is stored in a format that satisfies the legal requirements stipulated by the Electronic Book Preservation Law.

[0020] The terminal device 400 of the present embodiment is a terminal device used by the user of the transaction management system 100.

[0021] More specifically, for example, the terminal device 400 may be mainly used for the operation of storing the form information acquired by the transaction management device 200 in the transaction management database 240 as transaction management information. Further, an operation for determining the content of the transaction management information stored in the transaction management database 240 may be performed on the terminal device 400. In other words, the operation for determining the content of the transaction management information is an operation for determining the content of the form information.

[0022] In addition, the terminal device 400 may be used for the operation of storing, in the document management database 340 as document management information, information including a part of the transaction management information acquired by the document management device 300.

[0023] In the transaction management device 200 of the present embodiment, when an operation for determining the content of the transaction management information stored in the transaction management database 240 is performed on the terminal device 400, the transaction management device 200 automatically transmits information including a part of the transaction management information to the document management device 300. In other words, the transaction management device 200 transmits, in response to the operation for determining the content of the transaction management information, the information required by the provisions of the Electronic Bookkeeping Preservation Act to the document management device 300.

[0024] In the following description, the information transmitted from the transaction management device 200 to the document management device 300 is expressed as required information. The required information is information that satisfies the legal requirements specified in the Electronic Bookkeeping Preservation Act. Specifically, the required information may include form image data and a part of the transaction management information. Further, the required information may include information other than the information that satisfies the legal requirements specified in the Electronic Bookkeeping Preservation Act.

[0025] The document management device 300 associates the above-described history information and the like with the required information received from the transaction management device 200 to obtain document management information, and stores the document management information in the document management database 340.

[0026] Thus, in this embodiment, when a user of the service provided by the transaction management system 100 performs an operation to determine the content of the transaction management information, information that satisfies the legal requirements defined in the Electronic Bookkeeping Law is automatically output to the document management device 300 and stored.

[0027] Therefore, in this embodiment, in the transaction management database 240, manual operations by the user, such as selecting the transaction management information with determined content and transmitting it to the document management device 300, are no longer required, and the labor involved in information management can be reduced. Furthermore, in this embodiment, the occurrence of human errors such as forgetting to save information can be suppressed. Therefore, according to this embodiment, information management can be facilitated.

[0028] Note that the transaction management device 200 and the document management device 300 of this embodiment may be cloud servers provided on the Internet. Also, the transaction management device 200 and the document management device 300 may each be realized by a plurality of information processing devices.

[0029] Also, in the example of FIG. 1, the transaction management device 200 has the transaction management database 240, and the document management device 300 has the document management database 340, but the present invention is not limited to this. The transaction management database 240 may be provided in an external device capable of communicating with the transaction management device 200, and the document management database 340 may be provided in an external device capable of communicating with the document management device 300.

[0030] Also, each database included in the transaction management device 200 and the document management device 300 of this embodiment may be provided for each tenant using the transaction management system 100. A tenant is an organization such as a company, and a plurality of users may belong to it.

[0031] Next, with reference to FIG. 2, the hardware configuration of the transaction management device 200 of this embodiment will be described. FIG. 2 is a diagram showing an example of the hardware configuration of the transaction management device.

[0032] As shown in FIG. 2, the transaction management device 200 is constructed by a computer and includes, as shown in FIG. 2, a CPU 201, a ROM 202, a RAM 203, an HD 204, an HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I / F (Interface) 208, a network I / F 209, a bus line 210, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I / F 216.

[0033] Among these, the CPU 201 controls the operation of the entire transaction management device 200. The ROM 202 stores programs used for driving the CPU 201 such as the IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading or writing of various data to and from the HD 204 according to the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, characters, or images. The external device connection I / F 208 is an interface for connecting various external devices. External devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, and the like. The network I / F 209 is an interface for performing data communication using a communication network. The bus line 210 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 201 shown in FIG. 2.

[0034] In addition, the keyboard 211 is a type of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 214 controls reading or writing of various data with respect to the DVD-RW 213 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 216 controls reading or writing (storage) of data with respect to a recording medium 215 such as a flash memory.

[0035] Note that since the hardware configuration of the document management device 300 of the present embodiment is the same as that of the transaction management device 200, the description thereof is omitted.

[0036] FIG. 3 is a diagram showing an example of the hardware configuration of the terminal device. The terminal device 400 of the present embodiment includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a CMOS sensor 405, an imaging device I / F 406, an acceleration / azimuth sensor 407, a media I / F 409, and a GPS receiver 411.

[0037] Among these, the CPU 401 is an arithmetic processing device that controls the operation of the entire terminal device 400. The ROM 402 stores programs used for driving the CPU 401 such as the CPU 401 and IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data such as a smartphone program according to the control of the CPU 401. The ROM 402, the RAM 403, and the EEPROM 404 are an example of a storage device of the terminal device 400.

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

[0039] The imaging device I / F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration / azimuth sensor 407 is various sensors such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 409 controls the reading or writing (storage) of data to and from the recording media 408 such as a flash memory. The GPS receiver 411 receives GPS signals from GPS satellites.

[0040] Also, the terminal device 400 includes a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an imaging device I / F 414, a microphone 415, a speaker 416, an audio input / output I / F 417, a display 418, an external device connection I / F (Interface) 419, a short-distance communication circuit 420, an antenna 420a of the short-distance communication circuit 420, and a touch panel 421.

[0041] Among these, the long-distance communication circuit 412 is a circuit that communicates with other devices via a communication network. The CMOS sensor 413 is a kind of built-in imaging means that captures a subject according to the control of the CPU 401 to obtain image data. The imaging device I / F 414 is a circuit that controls the driving of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electrical signal. The speaker 416 is a built-in circuit that converts an electrical signal into physical vibration to generate sounds such as music and voice. The audio input / output I / F 417 is a circuit that processes the input and output of audio signals between the microphone 415 and the speaker 416 according to the control of the CPU 401.

[0042] The display 418 is a type of display means such as liquid crystal or organic EL (Electro Luminescence) that displays images of subjects, various icons, and the like. The external device connection I / F 419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means for operating the terminal device 400 by the user pressing down on the display 418. The display 418 is an example of the display unit of the terminal device 400.

[0043] Note that the hardware configuration shown in FIG. 3 is an example of the terminal device 400, and the hardware configuration of the terminal device 400 is not limited to this. The hardware configuration of the terminal device 400 may be the configuration shown in FIG. 2.

[0044] Next, with reference to FIGS. 4 and 5, the transaction management database 240 and the document management database 340 will be described.

[0045] FIG. 4 is a first diagram showing an example of the transaction management database of the first embodiment. The transaction management database 240 of the present embodiment is an example of a transaction management information storage unit that stores transaction management information. In the transaction management device 200, it is managed for each tenant. Also, in the following description, an invoice will be described as an example of a form.

[0046] The transaction management information stored in the transaction management database 240 includes, as information items, invoice ID, electronic document ID, file path, transfer form, registration date and time, status, confirmation date and time, invoice information, payment information, journal entry information, etc., and each item is associated with the tenant name "M Co., Ltd.". Note that the tenant name is information for identifying a tenant, and a tenant ID or the like may be used instead of the tenant name.

[0047] In the transaction management database 240, an item "document ID" is associated with other items. In the present embodiment, in the transaction management database 240, information including the value of the item "document ID" and the values of other items is referred to as transaction management information.

[0048] The value of the item "document ID" is document identification information for specifying a document (invoice) in the transaction management apparatus 200. In other words, the value of the item "document ID" is identification information for specifying transaction management information.

[0049] The value of the item "electronic document ID" is a value assigned by the document management apparatus 300, and is identification information for specifying document management information in the document management apparatus 300. The value of the item "electronic document ID" is assigned after the request information is transmitted to the document management apparatus 300.

[0050] The value of the item "file path" indicates the storage destination of the invoice image data. The invoice image data may be stored in an image data database other than the transaction management database 240.

[0051] The value of the item "transfer form" is information for specifying the form when a user of the transaction management system 100 receives an invoice. Specifically, when the value of the item "transfer form" is "electronic", it indicates that the invoice has been received as invoice image data, and when the value of the item "transfer form" is "paper", it indicates that the invoice has been received as paper.

[0052] The value of the item "registration date and time" indicates the date and time when the invoice information is stored in the transaction management database 240.

[0053] The value of the item "status" indicates the status of the transaction management information. The status of the transaction management information is the progress status of confirmation work and various input work of the invoice information included in the transaction management information. In other words, the value of the item "status" indicates the progress status of work on the transaction management information.

[0054] In this embodiment, the states of the transaction management information include four states: an unprocessed state, a draft save state, a confirmed state, and an externally output state. Each state is as follows.

[0055] · Unprocessed state (state 1): Immediately after the invoice information is obtained from the invoice image data, and the confirmation work, input work, etc. have not been performed.

[0056] · Draft save state (state 2): In the middle of the confirmation of the invoice information included in the transaction management information and various input operations, etc., and before the content of the transaction management information is finalized.

[0057] · Confirmed state (state 3): The content of the transaction management information is finalized and stored in the transaction management database 240.

[0058] · Cancelled state (state 4): The state in which an operation to cancel the transaction management information stored in the transaction management database 240 has been performed.

[0059] Note that the cancelled state is a state in which the transaction management information before it is set as the confirmed state is treated as if it has been deleted while remaining stored in the transaction management database 240.

[0060] In addition to these four states, the state of the transaction management information may include, for example, an output completed state indicating that the output of the transaction management information to the core system has been completed.

[0061] The value of the item "confirmation date and time" indicates the date and time when the content of the transaction management information was finalized. In other words, the value of the item "confirmation date and time" indicates the date and time when the value of the item "state" of the transaction management information was set to "confirmed".

[0062] The value of the item "invoice information" indicates the invoice information extracted from the invoice image data. In the example of FIG. 4, an invoice is taken as an example of the invoice, but the invoice may be other than an invoice.

[0063] The item "invoice information" is associated with items such as "invoice issuer", "invoice number", "invoice date", "total invoice amount", etc. In other words, the invoice information includes these items and the item values corresponding to the items.

[0064] The value of the item "invoice issuer" indicates the tenant who issued the invoice. In other words, the value of the item "invoice issuer" indicates the issuer of the document. The value of the item "invoice number" is identification information for specifying the invoice and is the identification information given by the invoice issuer. The value of the item "invoice date" indicates the date on which the invoice was created. The value of the item "total invoice amount" indicates the total of the invoice amounts. In other words, the value of the item "total invoice amount" indicates the total amount handled in the transaction indicated by the document specified by the document ID.

[0065] The value of the item "payment destination information" is information indicating the payment destination of the total invoice amount and may be information extracted from the invoice image data. That is, the payment information may be part of the invoice information. The item "payment information" includes items such as "bank name", "branch name", "account number", etc. The value of each of the items "bank name", "branch name", and "account number" indicates the bank name, branch name, and account number of the payment destination.

[0066] 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 on the receiving side of the document.

[0067] In FIG. 4, for example, the transaction management information 41 in the transaction management device 200 has a value of "1238" for the document ID and a blank value for the electronic document ID. Therefore, it can be seen that the request information included in the transaction management information 41 is in the state before being transmitted to the document management device 300.

[0068] Also, in the transaction management information 41, the value of the transfer form is "paper", the value of the status is "unprocessed", and the value of the settlement date and time is blank.

[0069] Therefore, in the example of FIG. 4, the document image data specified by the document ID included in the transaction management information 41 is the document image data obtained by scanning a paper document with an image forming apparatus or the like, and it can be seen that operations such as confirmation of document information (invoice information) and input of journal information have not been completed, and the content of the transaction management information 41 has not been determined.

[0070] In the transaction management information 41, for items with empty values, values will be stored when the processes described later are executed.

[0071] Also, in the transaction management information of this embodiment, the items "document ID", "biller", "invoice number", "invoice date", "total amount of claims", and their item values may be included in the request information. That is, the request information is specific item names and item values included in the transaction management information, and further, the request information includes a part of the document information included in the transaction management information.

[0072] Also, in the example of FIG. 4, information other than the invoice information (document information) extracted from the document image data may be the document management information.

[0073] FIG. 5 is a first diagram showing an example of the document management database of the first embodiment. The document management database 340 of this embodiment is an example of a document management storage unit that stores document management information. The document management database 340 is managed for each tenant in the document management apparatus 300.

[0074] The document management database 340 includes, as information items, electronic document ID, type, transfer form, customer name, transaction date, total amount, document ID, memo, confirmation status, document management registration date and time, document management registration user, transaction management registration date and time, transaction management registration user, original confirmation, original confirmation date and time, original confirmation user, file path, etc., and each item is associated with the item "electronic document ID". Also, the document management information is associated with the tenant name "M Co., Ltd.".

[0075] The value of the item "Type" indicates the type of the document corresponding to the transaction management information. The value of the item "Supplier Name" indicates the issuer (claimant) of the document. The value of the item "Transaction Date" indicates the date when the document was issued (claim date). The value of the item "Total Amount" indicates the total amount handled in the transaction corresponding to the document (total claim amount).

[0076] That is, the items "Supplier Name", "Transaction Date", "Total Amount" and their values included in the document management information of this embodiment are part of the required information corresponding to the items "Claimed Party", "Claim Date", "Total Claim Amount" and their values in the transaction management information, and can be said to be the items required to meet the legal requirements stipulated in the Electronic Bookkeeping Preservation Law.

[0077] Note that the requirements stipulated in the Electronic Bookkeeping Preservation Law are an example of the predetermined requirements when managing documents as electronic document information, and the predetermined requirements may be internal company rules, industry standards, etc.

[0078] Also, the items required to meet these legal requirements stipulated in the Electronic Bookkeeping Preservation Law are just an example, and when at least a part of the legal requirements stipulated in the Electronic Bookkeeping Preservation Law is added, changed, deleted, etc., the items required to meet the legal requirements may be added, changed, deleted, etc.

[0079] The value of the item "Document ID" is the document ID included in the transaction management information corresponding to the document management information. The value of the item "Document ID" in the document management information is information for identifying the transaction management information corresponding to the document management information.

[0080] The value of the item "Memo" indicates additional information automatically input when the document management information is stored in the document management database 340. The additional information may include the document ID included in the transaction management information corresponding to the document management information. The value of the item "Confirmation Status" indicates whether the visual confirmation of the required information stored in the document management database 340 has been completed.

[0081] The value of the item "Document Management Registration Date and Time" indicates the date and time when the document management device 300 received the request information included in the document management information. Specifically, the value of the item "Document Management Registration Date and Time" may be the value of the item "Finalization Date and Time" of the transaction management information corresponding to the document management information.

[0082] The value of the item "Document Management Registration User" is information that identifies the user who visually confirmed the content of the document management information including the request information.

[0083] The value of the item "Transaction Management Registration Date and Time" indicates the date and time when the form information was stored in the transaction management database 240. The value of the item "Transaction Management Registration User" is information that identifies the user who stored the form information in the transaction management device 200.

[0084] The value of the item "Original Document Verification" indicates whether a visual comparison has been made between the original of the form and the form image data stored in the transaction management device 200. When the value of the item "Original Document Verification" is "Verified", it indicates that a comparison has been made between the original of the form and the form image data.

[0085] The value of the item "Original Document Verification Date and Time" indicates the date and time when the comparison between the original of the form and the form image data was made, and the value of the item "Original Document Verification User" is information that identifies the user who made the comparison.

[0086] In the document management information 51 shown in FIG. 5, it can be seen that the invoice specified by the electronic document ID "5679" and the invoice ID "1238" was delivered in "paper" from the trading partner, Corporation C, and the request information extracted from this invoice has not been confirmed. Also, in the document management information 51, it can be seen that the visual comparison between the form and the form image data was performed by user X, and the form information including the request information was registered in the transaction management device 200 by user X. Also, it can be seen that the content of the document management information 51 was confirmed by user Y.

[0087] Note that in the document management information 51, for items with empty values, values will be stored as the following processing is executed.

[0088] Further, in the example of FIG. 5, among the document management information, information other than the request information may be history information for managing the history of handling of the form.

[0089] Next, with reference to FIG. 6, the functional configurations of the respective devices included in the transaction management system 100 of the present embodiment will be described. FIG. 6 is a diagram for explaining the functional configurations of the respective devices included in the transaction management system of the first embodiment.

[0090] First, the functions of the transaction management device 200 will be described. The transaction management device 200 of the present embodiment includes a transaction management database 240 and a transaction management unit 250, and the transaction management unit 250 includes an input reception unit 251, a form recognition unit 252, an information management unit 253, a display control unit 254, and an output unit 255.

[0091] The input reception unit 251 receives various inputs to the transaction management device 200. Specifically, the input reception unit 251 receives the input of form image data to the transaction management device 200, the input of form management information from the terminal device 400, and the like.

[0092] The form recognition unit 252 performs form recognition processing on the form image data received by the input reception unit 251 and extracts form information. Specifically, the form recognition processing of the present embodiment is a process of extracting the name (item) 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.

[0093] The information management unit 253 manages various types of information. Specifically, the information management unit 253 associates form information with form management information, updates transaction management information, and the like.

[0094] The display control unit 254 controls the display content on the terminal device 400. The output unit 255 outputs various types of information to an external device. Specifically, the output unit 255 outputs request information to the document management device 300.

[0095] Note that the output in this embodiment includes the transmission of information. Further, the external device in this embodiment may include, for example, a server or device that can be connected to the transaction management device 200 via a network or wireless communication.

[0096] Therefore, it can be said that the output unit 255 of this embodiment transmits request information to the document management device 300 connected to the transaction management device 200 via the network.

[0097] Next, the functions of the document management device 300 will be described. The document management device 300 includes a document management database 340 and a document management unit 350, and the document management unit 350 includes an input reception unit 351, a storage control unit 352, and a display control unit 353.

[0098] The input reception unit 351 receives various inputs to the document management device 300. The storage control unit 352 controls the storage of information in the document management database 340. Specifically, the storage control unit 352 stores the request information received from the transaction management device 200 in the document management database 340. Further, the storage control unit 352 updates the document management information stored in the document management database 340 in response to an input from the terminal device 400.

[0099] The display control unit 353 controls the display content on the terminal device 400. Specifically, the display control unit 353 controls the display of document management information on the terminal device 400.

[0100] Next, the functions of the terminal device 400 will be described. The terminal device 400 includes an input reception unit 430, a display control unit 440, and a communication unit 450. The input reception unit 430 receives various inputs to the terminal device 400. The display control unit 440 displays information on the display 418 of the terminal device 400. The communication unit 450 transmits and receives information between the terminal device 400 and other devices.

[0101] Next, with reference to FIG. 7, the operation of the transaction management system 100 of the present embodiment will be described. FIG. 7 is a first sequence diagram for explaining the operation of the transaction management system of the first embodiment. In FIG. 7, the operation until the content of the transaction management information is determined in the transaction management device 200 will be explained.

[0102] In the present embodiment, in the example of FIG. 7, it is premised that the login process required when the user of the terminal device 400 uses the service provided by the transaction management device 200 is performed.

[0103] Also, in the present embodiment, the user may be a user belonging to a tenant, and by the login process, the transaction management database 240 referred to according to the operation from the terminal device 400 may be specified as the transaction management database 240 of the tenant to which the user belongs.

[0104] In the transaction management system 100, when the terminal device 400 receives an operation instructing the upload of the form image data (step S701), it transmits the form image data to the transaction management device 200 (step S702).

[0105] When the transaction management device 200 receives the input of the form image data by the input reception unit 251 of the transaction management unit 250, the form recognition unit 252 performs form recognition processing and extracts form information (step S703).

[0106] Specifically, the form recognition unit 252 acquires the characters and the coordinate values of the characters described in the form image by OCR (Optical Character Reader), and specifies a character string based on the coordinate values. Then, the form recognition unit 252 may extract the item value corresponding to the item according to the definition information in which the items and item values of the extraction target items are defined, and associate the item with the item value. Note that the definition information may be held in the transaction management device 200 in advance.

[0107] Subsequently, the transaction management unit 250 specifies, via the information management unit 253, the form of exchange of the document that is the source of the document image data and the type of the document (step S704).

[0108] Specifically, when the document image data acquired in step S702 is image data without text data attached, the information management unit 253 specifies the form of exchange of the document as "electronic". Also, when the document image data is image data with text data attached, the information management unit 253 specifies the form of exchange of the document as "paper".

[0109] Also, the information management unit 253 specifies the type of the document based on the document information extracted in step S703.

[0110] Subsequently, the transaction management device 200 stores, via the information management unit 253, the document information in the transaction management database 240 (step S705).

[0111] Here, the information management unit 253 assigns a document ID that uniquely identifies the document information to the document information and stores it in the transaction management database 240. Also, at this time, among the items included in the transaction management information, the file path, registration date and time, and status values may also be stored in the transaction management database 240 in association with the document information.

[0112] Subsequently, the terminal device 400 receives, via the input reception unit 430, an operation instructing the display of the list screen of the transaction management information (step S706). Subsequently, the terminal device 400 transmits, via the communication unit 450, a display request for the list screen to the transaction management device 200 (step S707).

[0113] When the transaction management device 200 receives the display request for the list screen via the input reception unit 251, the display control unit 254 acquires a list of the transaction management information stored in the transaction management database 240 (step S708).

[0114] Subsequently, the transaction management device 200 generates a list screen to be displayed on the terminal device 400 by the display control unit 254 (step S709).

[0115] Subsequently, the transaction management device 200 transmits a display instruction for the list screen to the terminal device 400 by the display control unit 254 (step S710). Details of the list screen will be described later.

[0116] The terminal device 400 receives the display instruction and causes the display control unit 440 to display a list screen of transaction management information on the display 418 which is a display unit (step S711).

[0117] Subsequently, when the terminal device 400 receives an operation of selecting transaction management information for which content confirmation work is to be performed (step S712), it transmits a display request for a confirmation screen of the selected transaction management information to the transaction management device 200 (step S713).

[0118] When the transaction management device 200 receives the display request for the confirmation screen, it acquires the selected transaction management information by the display control unit 254 (step S714) and generates a confirmation screen (step S715).

[0119] Subsequently, the transaction management device 200 transmits a display instruction for the confirmation screen of the transaction management information to the terminal device 400 by the communication unit 450 (step S716). Details of the confirmation screen will be described later.

[0120] The terminal device 400 receives this display instruction and causes the display control unit 440 to display a confirmation screen of the selected transaction management information on the display 418 (step S717). Note that the confirmation screen in the present embodiment is an example of a screen displayed using form information, and is an example of a work screen for a user of the terminal device 400 to perform work (confirmation work) using the form information.

[0121] Subsequently, the terminal device 400 receives, by the input reception unit 430, the input of form management information, the correction of form information, etc. (step S718). Note that the transaction management device 200 may update the transaction management information in the transaction management database 240 each time form management information is input in the terminal device 400.

[0122] Subsequently, the terminal device 400 receives, by the input reception unit 430, an operation for determining the content of the transaction management information (step S719). Note that, in the present embodiment, the operation for determining the content is an operation for completing the work using the form information.

[0123] When the operation for determining the content is performed, the terminal device 400 transmits an update request for requesting an update of the state of the transaction management information to the transaction management device 200 (step S720).

[0124] When receiving the input of the update request, the transaction management device 200 stores, by the information management unit 253, the input form management information in the transaction management database 240 in association with the form information, changes the value of the item "state" of the transaction management information to "confirmed", and determines the content of the transaction management information (step S721).

[0125] Note that, at this time, the transaction management device 200 may display, on the terminal device 400, a screen for selecting whether to transmit the request information included in the transaction management information in the confirmed state to the document management device 300. Then, when receiving an operation for instructing the transmission of the request information, the transaction management device 200 may perform a process of transmitting the request information. Details of the process of transmitting the request information will be described later.

[0126] The above is the operation until the content of the transaction management information is determined. Next, with reference to FIG. 8, a display example of the terminal device 400 will be described.

[0127] FIG. 8 is a first diagram showing a display example of the terminal device according to the first embodiment. A screen 80 shown in FIG. 8 is an example of a list screen of the transaction management information displayed on the terminal device 400 in step S711 of FIG. 7.

[0128] The screen 80 shown in FIG. 8 includes display areas 81 and 82. The display area 81 displays information identifying the user who has logged in to the transaction management system 100 and who made a display request for the list screen in step S706 of FIG. 7.

[0129] In other words, the information displayed in the display area 81 is information identifying the user who checks the content of the transaction management information, inputs document management information, etc., and is the value of the item "transaction management registration user" in the document management information corresponding to the transaction management information.

[0130] The display area 82 displays a list of transaction management information stored in the transaction management database 240. In the example of FIG. 8, the list of transaction management information displayed in the display area 82 includes the transaction management information 41 (see FIG. 4).

[0131] In the following description, it is assumed that the transaction management information 41 is selected as the transaction management information to be worked on in the screen 80.

[0132] When the transaction management information 41 is selected on the screen 80, the screen 80 transitions to the confirmation screen of the transaction management information 41.

[0133] FIG. 9 is a second diagram showing a display example of the terminal device according to the first embodiment. The screen 91 shown in FIG. 8 is an example of the confirmation screen displayed on the terminal device 400 in step S717 of FIG. 7.

[0134] The screen 91 includes display areas 81, 92, 93, 94, and operation buttons 96, 97, 98, 99.

[0135] In the display area 92, a form image corresponding to the transaction management information 41 is displayed. Also, when the operation button 96 described later is operated, the window 92a is displayed on the screen 91 when the user of the terminal device 400 has not performed the login process required when using the service provided by the document management device 300. The display position of the window 92a is not limited to the position shown in FIG. 9 and may be displayed within the screen 91.

[0136] Note that the use of the service provided by the document management device 300 may be permitted by the login process required when using the service provided by the transaction management device 200. In other words, the transaction management system 100 may be a system that adopts single sign-on, in which the services provided by the transaction management device 200 and the services provided by the document management device 300 can be used with a single user authentication. In that case, the window 92a is not displayed when the button 96 is operated.

[0137] In the display area 93, the status of the transaction management information is displayed. More specifically, in the display area 93, the value of the item "status" included in the transaction management information is displayed. In the transaction management database 240, since the value of the item "status" of the transaction management information 41 is "unprocessed", "unprocessed" is displayed in the display area 93. The display area 94 displays the transaction management information 41. Specifically, the display area 94 has display areas 94a and 94b. The form information is displayed in the display area 94a, and an input field for the form management information is displayed in the display area 94b.

[0138] The form information included in the transaction management information 41 is invoice information. Therefore, the invoice information included in the transaction management information 41 is displayed in the display area 94a. Also, the form management information included in the transaction management information 41 is journal information or the like. Therefore, an input field for inputting the item value of the journal information included in the transaction management information 41 is displayed in the display area 94b.

[0139] The operation button 96 is an operation button for setting the state of the transaction management information 41 to the finalized state. In other words, the operation button 96 is an operation button for finalizing the content of the transaction management information 41.

[0140] The operation button 97 is an operation button for setting the state of the transaction management information 41 to the draft save state.

[0141] The operation button 98 is an operation button for canceling the confirmation after the state of the transaction management information 41 has been set to the finalized state. In other words, the operation button 98 is an operation button for setting the state of the finalized transaction management information 41 back to the draft save state again.

[0142] The operation button 99 is an operation button for canceling the storage of the transaction management information 41 in the transaction management database 240. In other words, the operation button 99 is an operation button for setting the state of the transaction management information 41 to the canceled state. The canceled state is a state where the corresponding transaction management information is regarded as being deleted apparently without being deleted from the transaction management database 240.

[0143] In this embodiment, on the screen 91, after the confirmation of the content in the display area 94a and the input of information into the input fields displayed in the display area 94b are completed, when the operation button 96 is operated, the state of the transaction management information 41 becomes the finalized state. Thus, in this embodiment, the work using the form information includes the work of correcting the content of the form information and the work of inputting information into the input fields.

[0144] Also, in this embodiment, on the screen 91, when the operation button 96 is operated and the state of the transaction management information 41 becomes the finalized state, the request information included in the transaction management information 41 is transmitted from the transaction management device 200 to the document management device 300. Then, in the document management device 300, the document management information including the request information is stored in the document management database 340.

[0145] The operations until the document management information is stored in the document management database 340 will be described below with reference to FIG. 10. FIG. 10 is a second sequence diagram for explaining the operations of the transaction management system according to the first embodiment.

[0146] In the transaction management system 100, when the transaction management device 200 receives an operation to set the transaction management information to a finalized state, the information management unit 253 of the transaction management unit 250 sends a confirmation request to the document management device 300 to confirm that user authentication is being performed (step S1001).

[0147] When the document management device 300 receives the confirmation request, it checks whether user authentication is being performed (step S1002).

[0148] The processes from step S1003 to step S1010 below are operations when user authentication is not being performed.

[0149] When user authentication is not being performed, the document management device 300 sends an authentication request to the transaction management device 200 to request user authentication (step S1003).

[0150] When the transaction management device 200 receives the authentication request, the display control unit 254 sends a display instruction for the authentication screen to the terminal device 400 (step S1004). The authentication screen is, for example, the window 92a shown in FIG. 9.

[0151] When the terminal device 400 receives the display instruction, the display control unit 440 causes the authentication screen to be displayed on the display 418 (step S1005). Subsequently, when the terminal device 400 receives the input of authentication information (step S1006), it sends an authentication execution request to the transaction management device 200 (step S1007). The transaction management device 200 sends this execution request to the document management device 300 (step S1008).

[0152] When the document management device 300 receives this execution request, it performs user authentication (step S1009) and transmits the authentication result to the transaction management device 200 (step S1010). Here, it is assumed that the user has been authenticated, and a notification indicating that the user authentication has been performed is transmitted to the transaction management device 200.

[0153] When the transaction management device 200 receives this notification, it transmits a registration request including the request information to the document management device 300 by the output unit 255 (step S1011). Specifically, the transaction management device 200 calls a predetermined API (Application Programming Interface) provided by the document management device 300 and outputs the request information included in the transaction management information to the document management device 300.

[0154] When the document management device 300 receives a registration request including the request information by the input reception unit 351, it stores the request information in the document management database 340 by the storage control unit 352 (step S1012). Specifically, the document management device 300 assigns a new electronic document ID to the request information by the storage control unit 352 and stores it in the document management database 340 as document management information.

[0155] Subsequently, the document management device 300 transmits a completion notification indicating that the registration of the request information has been completed to the document management device 300 (step S1013). The completion notification transmitted here may include the electronic document ID. In other words, the document management device 300 may transmit the electronic document ID to the transaction management device 200 as a completion notification.

[0156] When the transaction management device 200 receives the electronic document ID, it stores the electronic document ID in the transaction management database 240 as part of the corresponding transaction management information by the information management unit 253 (step S1014).

[0157] Subsequently, the transaction management device 200 transmits a notification indicating that the registration of the request information to the document management device 300 has been completed to the terminal device 400 (step S1015).

[0158] Upon receiving this completion notification, the terminal device 400 causes the display control unit 440 to display, on the display 418, a notification screen indicating that the request information to the document management device 300 has been registered (step S1016).

[0159] The above is the operation until the document management information is stored in the document management database 340.

[0160] Next, with reference to FIG. 11, the transaction management database 240 after the request information is transmitted to the document management database 340 will be described. FIG. 11 is a second diagram showing an example of the transaction management database of the first embodiment.

[0161] In the transaction management database 240A shown in FIG. 11, the value of the item "Status" in the transaction management information 41a is set to "Confirmed", and the values of the item "Electronic Document ID" and the item "Confirmation Date and Time" are stored. Also, in the transaction management information 41a, the values of the items corresponding to the item "Journal Information" are input.

[0162] Therefore, it can be seen that the transaction management information 41a is in a state where the content is confirmed, and further, the request information included in the transaction management information 41 has been registered in the document management device 300.

[0163] In this embodiment, in the document management device 300, when the document management information is stored in the document management database 340, the document management information (request information) is confirmed.

[0164] Next, with reference to FIG. 12, the operation until the document management information is confirmed in the document management device 300 will be described. FIG. 12 is a third sequence diagram for explaining the operation of the transaction management system of the first embodiment.

[0165] In the transaction management system 100, when the terminal device 400 receives an operation instruction from the user to display the list screen of document management information (step S1201), it sends a display request for the list screen to the document management device 300 (step S1202).

[0166] When the document management device 300 receives a display request for the list screen by the input reception unit 351, the display control unit 353 acquires a list of document management information stored in the document management database 340 (step S1203).

[0167] Subsequently, the document management device 300 generates a list screen to be displayed on the terminal device 400 by the display control unit 353 (step S1204).

[0168] Subsequently, the document management device 300 sends a display instruction for the list screen to the terminal device 400 by the display control unit 353 (step S1205). Details of the list screen will be described later.

[0169] The terminal device 400 receives the display instruction and causes the display control unit 440 to display the list screen of document management information on the display 418 which is a display unit (step S1206).

[0170] Subsequently, when the terminal device 400 receives an operation instruction to select document management information for which content confirmation work is to be performed (step S1207), it sends a display request for the confirmation screen of the selected document management information to the document management device 300 (step S1208).

[0171] When the document management device 300 receives the display request for the confirmation screen, the display control unit 353 acquires the selected document management information (step S1209) and generates a confirmation screen (step S1210).

[0172] Subsequently, the transaction management device 200 sends a display instruction for the confirmation screen of the document management information to the terminal device 400 by the communication unit 450 (step S1211). Details of the confirmation screen will be described later.

[0173] The terminal device 400 receives this display instruction, and the display control unit 440 causes the confirmation screen of the selected document management information to be displayed on the display 418 (step S1212).

[0174] The above is the operation until the confirmation screen of the document management information is displayed on the terminal device 400.

[0175] Next, with reference to FIGS. 13 and 14, a display example of the terminal device 400 will be described. FIG. 13 is a fourth diagram showing a display example of the terminal device according to the first embodiment.

[0176] The screen 131 shown in FIG. 13 is an example of a list screen of document management information displayed on the terminal device 400 in step S1206 of FIG. 12.

[0177] The screen 131 includes display areas 132 and 133. Information for identifying a user permitted to use the services provided by the document management device 300 is displayed in the display area 132. In other words, the information displayed in the display area 132 is information for identifying a user who checks the content of the document management information, etc., and is the value of the item "document management registered user" in the document management information.

[0178] Note that the information for identifying the user displayed in the display area 132 is different from the information for identifying the user displayed in the display area 81 shown in FIG. 8. Specifically, the information for identifying the user displayed in the display area 132 indicates user Y, and the information for identifying the user displayed in the display area 81 indicates user X.

[0179] As described above, in the present embodiment, the user who stores the transaction management information in the transaction management database 240 and the user who stores the document management information in the document management database 340 may be different.

[0180] A list of the document management information stored in the document management database 340 is displayed in the display area 133. In the example of FIG. 13, the list of the document management information displayed in the display area 133 includes the document management information 51 (see FIG. 5).

[0181] In the following description, it is assumed that document management information 51 is selected as the document management information to be processed on screen 131.

[0182] When document management information 51 is selected on screen 131, screen 131 transitions to the confirmation screen for document management information 51.

[0183] FIG. 14 is a fifth diagram showing a display example of the terminal device according to the first embodiment. Screen 141 shown in FIG. 14 is an example of the confirmation screen displayed on terminal device 400 in step S1212 of FIG. 12.

[0184] Screen 141 includes display areas 132, 143, 144, 145, and operation button 146. In display area 143, a form image corresponding to document management information 51 is displayed.

[0185] The confirmation status of the document management information is displayed in display area 144. More specifically, the value of the item "confirmation status" included in the document management information is displayed in display area 144. In document management database 340 (see FIG. 5), the value of the item "confirmation status" of document management information 51 is "incomplete", so "incomplete" is displayed in display area 144.

[0186] Display area 145 includes display areas 145a, 145b, and operation button 145c. In display area 145a, the item values acquired as request information are displayed.

[0187] In the example of FIG. 14, the item values acquired as request information are the values of the items "claimant", "claim date", and "total claim amount", each being displayed as the values of the items "customer name", "transaction date", and "total amount".

[0188] Also, the document management device 300 according to the present embodiment displays the values of the items "customer name", "transaction date", and "total amount" shown in display area 145a in a state where editing is prohibited.

[0189] The display area 145b displays the form ID included in the transaction management information as information for specifying the transaction management information corresponding to the document management information. In the example of FIG. 14, text data including the form ID "1238" is displayed as the form ID for specifying the transaction management information 41 corresponding to the document management information 51.

[0190] The operation button 145c is an operation button for displaying the transaction management information. In the present embodiment, when the operation button 145c is operated, the document management device 300 may transmit a display request to the transaction management device 200 to display the transaction management information specified by the form ID "1238" to the transaction management device 200. The transaction management device 200 may receive this display request and display the transaction management information specified by the form ID "1238" on the terminal device 400.

[0191] The operation button 146 is an operation button for completing the confirmation status of the document management information. When the operation button 146 is operated on the screen 141, the document management device 300 sets the value of the item "confirmation status" of the document management information 51 to "completed".

[0192] Hereinafter, with reference to FIG. 15, the document management database 340 after the confirmation of the content of the document management information is completed will be described. FIG. 15 is a second diagram showing an example of the document management database according to the first embodiment.

[0193] In the document management database 340A shown in FIG. 15, the value of the item "confirmation status" of the document management information 51a is set to "completed". Therefore, it can be seen that the content of the document management information 51a has been confirmed.

[0194] As described above, in the present embodiment, at the timing when the content of the form information extracted from the form image data is determined, the specific item name and item value included in the form information are output to the document management device 300 and stored in the document management database 340 in the document management device 300.

[0195] Therefore, according to this embodiment, the document information is automatically stored in the document management device 300 in a format that also meets the requirements specified by the Electronic Bookkeeping Preservation Law. For this reason, in this embodiment, after the invoice image data is imported, no special operation is required to meet the requirements of the Electronic Bookkeeping Preservation Law, and the labor involved in information management can be reduced. Further, according to this embodiment, it is possible to eliminate human errors such as forgetting to save the document information in a format that also meets the requirements specified by the Electronic Bookkeeping Preservation Law.

[0196] Note that in this embodiment, in the transaction management device 200, it is possible to cancel and overwrite the transaction management information before it is in a finalized state.

[0197] The cancellation and overwriting of the transaction management information will be described below. FIG. 16 is a first flowchart for explaining the processing of the transaction management device according to the first embodiment.

[0198] Note that the processing in FIG. 16 is the processing of the transaction management device 200 when the user selects the operation button 96 for finalizing the content of the transaction management information or the operation button 99 for canceling the transaction management information on the screen 91 shown in FIG. 9 and receives a notification indicating that user authentication has been performed from the document management device 300.

[0199] In the transaction management device 200 of this embodiment, the information management unit 253 of the transaction management unit 250 acquires the document ID assigned when the invoice image data is acquired (step S1601).

[0200] Subsequently, the transaction management device 200 determines, by the input reception unit 251, whether an operation for finalizing the content of the transaction management information has been received in the terminal device 400 (step S1602).

[0201] In step S1602, when the transaction management device 200 does not receive a confirmation operation, the input reception unit 251 of the transaction management device 200 determines whether an operation to cancel the transaction management information has been received (step S1603). In other words, the transaction management device 200 determines whether the operation button 99 has been operated on the screen 91 shown in FIG. 9.

[0202] In step S1603, when the cancellation operation is not received, error processing is performed (step S1604), and the process ends. The error processing may be, for example, a process of displaying an error message when an internal error occurs and stopping the transmission of information to the document management device 300.

[0203] In step S1603, when the operation button 99 is operated, the transaction management device 200 transmits the form ID to the document management device 300 by the output unit 255 and requests cancellation registration of the document management information including the form ID. Further, the transaction management device 200 updates the value of the item "status" of the transaction management information including the form ID acquired in step S1601 to "cancelled" in the transaction management database 240 by the information management unit 253 (step S1605), and ends the process.

[0204] Note that the document management device 300 that has received the cancellation registration updates the value of the item "confirmation status" of the document management information including the form ID to "cancelled".

[0205] Also, in step S1602, when the operation button 96 is operated, the transaction management device 200 acquires the value of the item "confirmation date and time" from the transaction management information including the form ID acquired in step S1601 (step S1606). Subsequently, the transaction management device 200 determines whether the acquired value of the item "confirmation date and time" is empty (step S1607).

[0206] Specifically, in step S1607, the transaction management device 200 determines whether the confirmation operation in step S1602 is the first operation. If the value of the item "confirmation date and time" is empty, the confirmation operation in step S1602 is the first operation. Also, if the value of the item "confirmation date and time" is not empty, the operation in step S1602 is an operation performed again after the confirmation has been cancelled once.

[0207] In step S1607, if the value of the item "confirmation date and time" is empty, the transaction management device 200 transmits the request information to the document management device 300 via the output unit 255 to request new registration of the document management information. Also, the transaction management device 200 updates the value of the item "status" of the transaction management information to "confirmed" by the information management unit 253 (step S1608) and ends the process.

[0208] Note that the document management device 300 that has received the request for new registration stores the new document management information including the transmitted request information in the document management database 340. At that time, the document management device 300 may store the form image data included in the request information in a predetermined storage area and store the file path indicating the predetermined storage area in the document management database 340 as part of the document management information. Furthermore, the document management device 300 transmits the electronic document ID assigned to the new document management information to the transaction management device 200. The transaction management device 200 includes this electronic document ID in a part of the transaction management information corresponding to the form ID.

[0209] In step S1607, if the value of the item "confirmation date and time" is not empty, the transaction management device 200 transmits the form ID acquired in step S1601 and the request information to the document management device 300 to request overwriting registration of the document management information (step S1609) and ends the process.

[0210] When the value of the item "confirmation date and time" is not empty, for example, in the screen 91 shown in FIG. 9, after the operation button 98 is operated and the status of the transaction management information is changed from the confirmed status to the draft save status, if the operation button 99 is operated again. Note that when the document management apparatus 300 receives a request for overwriting registration, it identifies the document management information including the document ID and overwrites the request information included in the document management information.

[0211] Hereinafter, with reference to FIGS. 17 and 18, the transaction management database 240 and the document management database 340 when the operation button 99 for canceling the transaction management information is operated will be described.

[0212] FIG. 17 is a third diagram showing an example of the transaction management database of the first embodiment. The document management database 340B shown in FIG. 17 is the transaction management database 240 after being updated in step S1605 of FIG. 16.

[0213] In the transaction management database 240B, for the transaction management information 41b, the value of the item "status" is set to "cancelled", indicating that the transaction management information 41b has been cancelled. Therefore, in the transaction management database 240B, the transaction management information 41b is treated as information that has been seemingly deleted.

[0214] FIG. 18 is a third diagram showing an example of the document management database of the first embodiment. The document management database 340B shown in FIG. 18 is the document management database 340 after the document management apparatus 300 receives the cancellation registration of the document management information 51a.

[0215] In the document management database 340B, for the document management information 51b, the value of the item "confirmation status" is set to "cancelled", indicating that the document management information 51b has been cancelled. Therefore, in the document management database 340B, the document management information 51b is treated as information that has been seemingly deleted.

[0216] Next, with reference to FIGS. 19 and 20, the overwriting of transaction management information will be described. FIG. 19 is a fourth diagram showing an example of the transaction management database of the first embodiment. The transaction management database 240C shown in FIG. 19 shows the transaction management database 240 when the operation button 98 for canceling the confirmed state is operated on the screen 91 shown in FIG. 9.

[0217] In the transaction management information 41c shown in the transaction management database 240C, the value of the item "Status" is set to "Draft Save". At this time, since the transaction management information 41c has been confirmed once, the values of the items "Electronic Document ID", "Confirmation Date and Time", and "Journal Information" are input.

[0218] The transaction management device 200 thus overwrites the form information when new form image data is acquired in the transaction management information 41c in the draft save state.

[0219] It can be seen from the transaction management information 41c shown in FIG. 19 that the form information has been overwritten and the value of the item "Total Claim Amount" has been updated from the transaction management information 41b shown in FIG. 17.

[0220] Also, in the transaction management device 200, when the confirmation operation is performed again after the confirmed state is canceled once in this way, the value of the item "Status" in the transaction management information 41c is updated from "Draft Saved" to "Confirmed", and the value of the item "Confirmation Date and Time" is updated to the date and time when the second confirmation operation is performed. Then, the transaction management device 200 sends a request for overwriting registration to the document management device 300.

[0221] FIG. 20 is a fourth diagram showing an example of the document management database of the first embodiment. The document management database 340C shown in FIG. 20 is the document management database 340 after the document management device 300 receives the overwriting registration of the document management information 51b.

[0222] In the document management database 340C, it can be seen that in response to overwriting registration, the requested information is updated, and the value of the item "total amount" in the document management information 51c is updated from the value of the item "total amount" in the document management information 51b shown in FIG. 18. Also, in the document management information 51c, the values of the items "document management registration date and time" and "document management registration user" are updated.

[0223] Further, in the present embodiment, in addition to the above-described cancellation and overwriting, replacement of the transaction management information in the finalized state may be performed.

[0224] Note that in the present embodiment, when the form is replaced, the transaction management information in the finalized state is replaced.

[0225] Also, in the present embodiment, the form ID indicating the form version number is included in the transaction management information, and the form ID is included in the requested information transmitted from the transaction management device 200 to the document management device 300, so that the document management device 300 stores the requested information corresponding to the replaced form.

[0226] Hereinafter, with reference to FIG. 21, in addition to the cancellation and overwriting of the transaction management information, the case where the transaction management information is replaced will be described. FIG. 21 is a second flowchart for explaining the processing of the transaction management device according to the first embodiment.

[0227] The processing from step S2101 to step S2107 in FIG. 21 is the same as the processing from step S1601 to step S1607 in FIG. 16, and thus the description thereof is omitted.

[0228] In step S2107, when the value of the item "finalization date and time" is empty, the value of the item "form ID" is acquired from the transaction management information including the form ID (step S2108).

[0229] Subsequently, the transaction management device 200 determines whether the value of the item "form ID" is empty (step S2109).

[0230] When both the value of the item "Determination Date and Time" and the value of the item "Version ID" are empty, the transaction management information is newly registered.

[0231] Therefore, in step S2109, when the value of the item "Version ID" is empty, the transaction management device 200 transmits the request information to the document management device 300 by the output unit 255 to request new registration of the document management information. Further, the transaction management device 200 updates the value of the item "Status" of the transaction management information to "Confirmed" by the information management unit 253 (step S2110), and ends the process.

[0232] In step S2109, when the value of the item "Version ID" is not empty, the transaction management device 200 acquires the form ID corresponding to the previous version ID from the transaction management information (step S2111).

[0233] When the value of the item "Version ID" is not empty, it indicates that form replacement has been performed. Therefore, the transaction management device 200 acquires the form ID of the form for which the transaction management information was determined in the past.

[0234] Subsequently, the transaction management device 200 transmits the acquired form ID to the document management device 300 and requests cancellation registration of the document management information including the form ID. Further, the transaction management device 200 updates the value of the item "Status" of the transaction management information including the form ID acquired in step S2111 to "Cancelled" in the transaction management database 240 by the information management unit 253 (step S2112), and ends the process.

[0235] Note that the document management device 300 that has received the cancellation registration updates the value of the item "Confirmation Status" of the document management information including the form ID to "Cancelled".

[0236] Also, in step S2107, when the value of the item "Determination Date and Time" is not empty, the transaction management device 200 proceeds to step S2113. Since the process of step S2113 is the same as the process of step S1609 in FIG. 16, the description is omitted.

[0237] Hereinafter, with reference to FIGS. 22 and 23, the process of replacing forms will be specifically described.

[0238] FIG. 22 is a fifth diagram showing an example of a transaction management database according to the first embodiment. In the transaction management database 240D shown in FIG. 22, the item "version ID" is included in the transaction management information.

[0239] In the example of FIG. 22, in the transaction management information 41d-1, the version ID corresponding to the form ID "1238" is "1". Also, in the transaction management information 41d-2, the form ID is "1238-2", and the corresponding version ID is "2".

[0240] Therefore, in the example of FIG. 22, the transaction management information 41d-1 is transaction management information including form information extracted from the form specified by the form ID "1238".

[0241] Also, the transaction management information 41d-2 is transaction management information including form information extracted from the form obtained by revising the form specified by the form ID "1238". Also, since the form specified by the form ID "1238-2" has a version ID of "2", it can be seen that it is the form issued for the second time.

[0242] In the following description, the form before revision is expressed as the old version form, and the newly issued form after revision is expressed as the new version form.

[0243] Therefore, the transaction management information 41d-1 is transaction management information corresponding to the old version form, and the transaction management information 41d-2 is transaction management information corresponding to the new version form.

[0244] Also, in FIG. 22, the value of the "status" column of the transaction management information 41d-1 is "confirmed", and the value of the "electronic document ID" column is stored. Also, in the example of FIG. 22, the value of the "status" column of the transaction management information 41d-2 is "unprocessed", and the value of the "electronic document ID" column is empty.

[0245] Therefore, in the example of FIG. 22, for the old version of the form, the required information has been sent to the document management device 300 and stored in the document management database 340. For the new version of the form, the content of the transaction management information 41d-2 has not been determined, and it can be seen that the required information has not been sent to the document management device 300.

[0246] FIG. 23 is a sixth diagram showing an example of the transaction management database of the first embodiment. In the transaction management database 240E shown in FIG. 23, in the terminal device 400, after an operation to determine the content is performed on the transaction management information corresponding to the form specified by the form ID "1238" and the version ID "2", the state is shown.

[0247] In the transaction management database 240E, the value of the item "status" in the transaction management information 41d-2 has been determined, and the value of the item "electronic document ID" is stored.

[0248] Therefore, in the example of FIG. 23, for the new version of the form, it can be seen that the required information has been sent to the document management device 300 and stored in the document management database 340.

[0249] Also, in the transaction management database 240E, the value of the item "electronic document ID" in the transaction management information 41d-1 is different from the value of the item "electronic document ID" in the transaction management information 41d-2. Therefore, it can be seen that the required information corresponding to the transaction management information 41d-1 and the required information corresponding to the transaction management information 41d-2 are managed separately in the document management device 300.

[0250] FIG. 24 is a fifth diagram showing an example of the document management database of the first embodiment. The document management database 340D shown in FIG. 24 shows the state after the required information corresponding to the transaction management information 41d-2 is sent from the transaction management device 200 to the document management device 300.

[0251] In the document management database 340D, the document management information 51d-1 includes the request information corresponding to the transaction management information 41d-1, and the document management information 51d-2 includes the request information corresponding to the transaction management information 41d-2.

[0252] In the example of FIG. 24, the value of the item "confirmation status" in the document management information 51d-1 is "cancelled", and the value of the item "confirmation status" in the document management information 51d-2 is "incomplete". Therefore, in the document management database 340D, the document management information 51d-1 is in the cancelled state, and the content of the document management information 51d-2 will be confirmed.

[0253] Specifically, in the document management database 340D, when the content is confirmed on the confirmation screen of the document management information 51d-2, the value of the item "confirmation status" in the document management information 51d-2 becomes "completed".

[0254] As described above, in this embodiment, after the request information corresponding to the form information extracted from the form is stored in the document management device 300, if this form is revised, the request information corresponding to the form information of the old version of the form before the revision stored in the document management device 300 is set to the cancelled state. Then, in the document management device 300, the request information corresponding to the form information of the new version of the form is stored in association with the form ID that identifies the new version of the form.

[0255] Therefore, in this embodiment, in the document management device 300, the form can be replaced (revised). Also, in this embodiment, in the document management device 300, the history of the form replacement can be retained.

[0256] Hereinafter, with reference to FIGS. 25 and 26, a display example of the terminal device 400 when replacing a form will be described.

[0257] FIG. 25 is a sixth diagram showing a display example of the terminal device of the first embodiment. The screen 91A shown in FIG. 25 is an example of the confirmation screen of the transaction management information 41d-2.

[0258] The screen 91A includes a display area 81, 92A, 93, 94, and operation buttons 96, 97, 98, 99.

[0259] The display area 92A is an operation button for selecting form image data of a new version of the form. In the screen 91A, when the operation button 92b is selected, the terminal device 400 may display a list of candidates for the form image data to be uploaded to the transaction management device 200.

[0260] Then, when the form image data is selected, the terminal device 400 transmits the selected form image data to the transaction management device 200 as the form image data of the new version.

[0261] FIG. 26 is a seventh diagram showing a display example of the terminal device according to the first embodiment. The screen 91B shown in FIG. 26 is another example of the confirmation screen of the transaction management information 41d-2.

[0262] The screen 91B includes a display area 81, 92B, 93, 94, and operation buttons 96, 97, 98, 99.

[0263] The display area 92B includes an operation button 92b and a window 92c. A list of form image data of the old version of the form is displayed in the window 92c.

[0264] In the present embodiment, in the window 92c, when the form image data of the old version is selected, the transaction management information corresponding to the selected form image data is displayed on the confirmation screen.

[0265] As described above, in the transaction management system 100 of the present embodiment, it is possible to cancel, overwrite, and replace form information. Further, in the transaction management system 100 of the present embodiment, it is possible to leave a history indicating that cancellation, overwrite, and replacement have been performed.

[0266] (Second Embodiment) The following describes a second embodiment with reference to the drawings. The second embodiment differs from the first embodiment in that it does not perform document recognition processing. In the following description, differences from the first embodiment will be described, and components having the same functional configuration as those in the first embodiment will be given the same reference numerals as used in the description of the first embodiment, and the description thereof will be omitted.

[0267] FIG. 27 is a diagram for explaining the functional configuration of each device included in the transaction management system of the second embodiment.

[0268] The transaction management system 100A of this embodiment includes a transaction management device 200A, a document management device 300, and a terminal device 400.

[0269] The transaction management device 200A of this embodiment has a transaction management database 240A and a transaction management unit 250A. The transaction management unit 250A includes an input reception unit 251, an information management unit 253, a display control unit 254, an output unit 255, and an information acquisition unit 256.

[0270] The information acquisition unit 256 may acquire document information and the like from the terminal device 400 or an external system 500.

[0271] Specifically, for example, the information acquisition unit 256 may acquire information in which document image data and document information corresponding to the document image data are associated from the terminal device 400. In this case, the transaction management device 200A may associate the document image data and the document information and store them in the transaction management database 240A, and the document recognition processing for extracting document information from the document image data is not required.

[0272] The information in which document image data and document information corresponding to the document image data are associated may be, for example, information in which PDF data of an invoice and text data extracted from the PDF data are associated.

[0273] In this embodiment, when the invoice information is acquired from the terminal device 400 in this manner, the invoice information acquired from the terminal device 400 is displayed as it is in the display area 94a of the display area 94 on the screen 91. Therefore, in this embodiment, there is no need to correct the invoice information displayed in the display area 94a. For this reason, in this embodiment, the work performed on the screen 91 using the invoice information is only the input work for the input fields displayed in the display area 94b.

[0274] Further, the information acquisition unit 256 may acquire, from the external system 500, the invoice information of other invoices specified from the invoice information acquired from the terminal device 400, and store it in the transaction management database 240A.

[0275] The external system 500 may be, for example, a system that manages by associating the invoice information acquired by the transaction management device 200A from the terminal device 400 with the invoice information of the invoice corresponding to the invoice indicated by this invoice information. Specifically, the external system 500 may manage by associating the invoice information acquired by the transaction management device 200A from the terminal device 400 with the order form information extracted from the order form corresponding to the invoice indicated by this invoice information.

[0276] The information acquisition unit 256 of this embodiment searches the external system 500 based on the claimant, invoice number, etc. included in the invoice information acquired from the terminal device 400. In other words, the information acquisition unit 256 searches the external system 500 based on the identification information of the invoice included in the invoice information acquired from the terminal device 400.

[0277] Then, the information acquisition unit 256 may acquire, from the external system 500, the order form information of the order form corresponding to the invoice specified by the claimant or invoice number, and store it in the transaction management database 240A.

[0278] In addition to the transaction management information shown in FIG. 4, the transaction management database 240A of the present embodiment may store information acquired by the information acquisition unit 256 from the external system 500. More specifically, the transaction management database 240A may store order form information acquired by the information acquisition unit 256 from the external system 500.

[0279] FIG. 28 is a diagram showing an example of the transaction management database of the second embodiment. The order form information 241 shown in FIG. 28 is information acquired by the information acquisition unit 256 from the external system 500 and is stored in the transaction management database 240A as part of the transaction management information.

[0280] In the transaction management database 240A, the order form information 241 is stored for each tenant. The order form information 241 includes, as information items, the order destination, the order form number, the total order amount, and the like.

[0281] The value of the item "order destination" is a value for identifying the order destination, and in FIG. 28, it indicates the tenant name that is the order destination. The value of the item "order form number" is identification information for identifying the order form. The value of the item "total order amount" indicates the total amount of the order indicated by the order form.

[0282] In the present embodiment, in this way, by storing the order form information of the order form corresponding to the invoice as part of the transaction management information in the transaction management database 240A, it is possible to visually check the content of the invoice and the content of the order form.

[0283] Next, with reference to FIG. 29, the operation of the transaction management system 100A of the present embodiment will be described. FIG. 29 is a sequence diagram for explaining the operation of the transaction management system of the second embodiment.

[0284] In FIG. 29, the processes of step S2901 and step S2902 and the processes after step S2903 are performed at different independent timings.

[0285] In the transaction management system 100A of this embodiment, the transaction management device 200A acquires order form information from the external system 500 by the information acquisition unit 256 (step S2901), and stores it in the transaction management database 240A (step S2902).

[0286] Note that the processes of step S2901 and step S2902 may be performed each time the transaction management device 200A acquires the form image data and form information from the terminal device 400.

[0287] Since the processes from step S2903 to step S2909 in FIG. 29 are the same as the processes from step S706 to step S712 in FIG. 7, the description thereof is omitted.

[0288] In step S2908, when the terminal device 400 receives an operation of selecting transaction management information for performing a content confirmation operation (step S2909), the terminal device 400 transmits a display request for a matching screen of the invoice information and the order form information included in the selected transaction management information to the transaction management device 200A (step S2910).

[0289] When the transaction management device 200A receives the display request for the matching screen, the information management unit 253 refers to the transaction management database 240A to specify the form information to be matched (step S2911). Here, the information management unit 253 specifies the invoice information and the order form information included in the selected transaction target information.

[0290] Subsequently, the transaction management device 200A generates a matching screen for matching the invoice information and the order form information by the display control unit 254 (step S2912), and instructs the terminal device 400 to display the matching screen (step S2913).

[0291] The terminal device 400 receives this display instruction, and the display control unit 440 causes the matching screen to be displayed on the display 418 (step S2914).

[0292] Subsequently, the terminal device 400 receives, via the input receiving unit 430, an operation indicating that the user of the terminal device 400 has performed reconciliation (step S2915), and proceeds to step S2916. Note that the reconciliation is performed visually by the user.

[0293] Note that the reconciliation screen in this embodiment is an example of a confirmation screen for checking the contents of the form information (invoice information and order form information) stored in the transaction management device 200A. In other words, the reconciliation screen is an example of a work screen for performing work using the form information.

[0294] Since the processing from step S2916 to step S2918 in FIG. 29 is the same as the processing from step S719 to step S721 in FIG. 7, the description thereof is omitted.

[0295] Next, a display example in the terminal device 400 of this embodiment will be described. FIG. 30 is a first diagram showing a display example of the terminal device of the second embodiment.

[0296] A screen 91C shown in FIG. 30 is an example of a reconciliation screen displayed on the terminal device 400 in step S2914 of FIG. 29.

[0297] The screen 91C includes display areas 81, 92, 93, 95, and operation buttons 96, 97, 98, 99.

[0298] In the display area 95, form information extracted from the form corresponding to the form shown by the form image displayed in the display area 92 is displayed. The form for which the form image is displayed in the display area 92 and the form for which the form nourishment method is displayed in the display area 95 are specified in step S2911 of FIG. 29.

[0299] In the example of FIG. 30, a form image corresponding to the transaction management information 41 is displayed in the display area 92 (see FIG. 8). The form shown by the form image displayed in the display area 92 is an invoice, and an invoice image is displayed in the display area 92. Therefore, in the display area 95, order form information corresponding to the invoice for which the invoice image is displayed in the display area 92 is displayed.

[0300] In this embodiment, in this way, by displaying both the invoice image and the order form information extracted from the order form corresponding to the invoice image, it is possible to confirm whether the content of the invoice matches the content of the order form.

[0301] In this embodiment, on the screen 91C, when the operation button 96 is operated, an update request for requesting an update of the state of the transaction management information is transmitted to the transaction management device 200A. The transaction management device 200A regards the work on the work screen as completed by this operation, changes the value of the item "status" of the transaction management information to "confirmed" in the transaction management database 240A, and finalizes the content of the transaction management information.

[0302] When the content of the transaction management information is finalized, the transaction management device 200A transmits information including a part of the transaction management information to the document management device 300.

[0303] In this way, the work screen of this embodiment may include invoice image data of a certain form (invoice) and form information of a form specified by identification information for specifying a certain form.

[0304] Also, in this embodiment, as a work screen for performing work using form information, it may include invoice image data of a certain form (invoice) and form management information for managing this form.

[0305] The form management information is, for example, journal information and payment information. FIG. 31 is a second diagram showing a display example of the terminal device of the second embodiment.

[0306] The screen 91D shown in FIG. 31 is an example of a work screen for performing work using form information. In the confirmation screen displayed in step S717 of FIG. 7, an operation is performed to display an input field for inputting journal information, indicating a state in which the journal information has been input.

[0307] Screen 91D includes tabs 94d and 94e for selecting an input field to be displayed in the display area 94c. In the present embodiment, when tab 94d is selected, an input field for journal entry information is displayed in the display area 94c, and when tab 94e is selected, an input field for journal entry information is displayed in the display area 94c.

[0308] On screen 91D, tab 94d is selected, and an input field for entering journal entry information is displayed in the display area 94c. Also, on screen 91D, journal entry information has been entered in the input field displayed in the display area 94c.

[0309] In the present embodiment, on screen 91D, when the operation button 96 is operated, the content of the transaction management information is determined.

[0310] FIG. 32 is a third diagram showing a display example of the terminal device according to the second embodiment. The screen 91E shown in FIG. 32 is an example of a work screen for performing work using form information. In the confirmation screen displayed in step S717 of FIG. 7, an operation is performed to display an input field for entering payment information, showing a state in which journal entry information has been entered.

[0311] On screen 91E, tab 94e is selected, and an input field for entering payment information is displayed in the display area 94c. Also, on screen 91E, journal entry information has been entered in the input field displayed in the display area 94c.

[0312] In the present embodiment, in this way, on the work screen, by displaying journal entry information and payment information, which are form management information, together with the form information, the user of the terminal device 400 can confirm the journal entry information, payment information, and the content of the automatically entered form information.

[0313] Also, in the present embodiment, at the timing when the confirmation of the content of the form management information and the form information is completed, a part of the transaction management information can be transmitted to the document management device 300.

[0314] Note that 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.

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

[0316] In one embodiment, the transaction management device 200 and the document management device 300 include a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other via an arbitrary type of communication link including a network, a shared memory, etc., and implement the processes disclosed in this specification. Similarly, the transaction management device 200 and the document management device 300 can include a plurality of computing devices configured to communicate with each other.

[0317] Furthermore, the transaction management device 200 and the document management device 300 can be configured to share the disclosed processing steps in various combinations. For example, a process executed by a predetermined unit can be executed by the transaction management device 200. Similarly, the functions of a predetermined unit can be executed by the transaction management device 200. Also, in the transaction management device 200 and the document management device 300, each element they have may be combined into one server device or divided into multiple devices.

[0318] Note that the device that provides the form image data is not limited to an image forming device as long as it is a device equipped with a communication function. The device that provides the form image data may be, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board), a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collection device, a medical device, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game machine, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

[0319] Aspects of the present invention are as follows, for example. <1> A transaction management system including a transaction management device, a document management device, and a terminal device, wherein the transaction management device, the document management device, and the terminal device are connected via a network, The transaction management device, A display control unit that displays on the terminal device a work screen for performing work using the form information described in the form; When an operation to complete the work using the form information is received on the work screen, an output unit that outputs at least a part of the form information and form image data that is an image of the form to the document management device; The document management device, A transaction management system having a storage control unit that stores at least a part of the form information received from the transaction management device and the form image data in a document management storage unit. <2> The transaction management system according to Appendix 1, wherein at least a part of the form information includes a predetermined specific item name and its item value. <3> The transaction management system according to Appendix 1, wherein at least a part of the form information includes the issuer of the form, the issue date of the form, the total amount of money handled in the transaction indicated by the form, and identification information for specifying the form. <4> The storage control unit is document management information that associates at least a part of the form information with history information indicating the history of handling the form, and stores the document management information including identification information for specifying the document management information in the document management storage unit. The transaction management system according to any one of Appendices 1 to 3. <5> The document management device has a display control unit that causes the terminal device to display a screen for confirming at least a part of the form information and the form image data. The display control unit causes the terminal device to display the screen in a state where editing of at least a part of the form information is prohibited. The transaction management system according to any one of Appendices 1 to 4. <6> The document management device after the document management information is stored in the document management storage unit, transmits identification information for specifying the document management information to the transaction management device. The transaction management device has an information management unit that stores transaction management information associating the identification information for specifying the document management information with the form information in a transaction management storage unit. The transaction management system according to Appendix 4. <7> The transaction management information includes a value indicating the progress status of work on the transaction management information. The information management unit receives an operation for instructing cancellation of the transaction management information in the terminal device, and sets the value indicating the progress status of the work included in the transaction management information to a cancelled state. The output unit outputs a cancellation request for the document management information corresponding to the transaction management information to the document management device. The transaction management system according to Appendix 6. <8> The information management unit receives an operation for releasing the state where the content of the transaction management information is determined in the terminal device, and sets the value indicating the progress status of the work included in the transaction management information to a draft save state. The output unit When receiving an operation to re - determine the content of the transaction management information, the transaction management system according to Supplementary Note 7 outputs a request to overwrite the document management information corresponding to the transaction management information to the document management device. <9> The transaction management information includes information indicating the version number of the form. The information management unit receives the input of form image data of a new - version form, stores in the transaction management storage unit the transaction management information in which the form information extracted from the new - version form image data is associated with the form information of the old - version form. The output unit outputs to the document management device at least a cancellation request for the document management information corresponding to the transaction management information including the form information of the old - version form, the form image data of the new - version form, and at least a part of the form information extracted from the new - version form image data. The transaction management system according to Supplementary Note 7 or 8. <10> The work screen includes the form image data and the form information of other forms specified by the identification information for specifying the form. The transaction management system according to any one of Supplementary Notes 1 to 9. <11> The form is an invoice, and the other form is an order form. The transaction management system according to Supplementary Note 10. <12> The work screen includes the form image data and the form management information for managing the form. The transaction management system according to any one of Supplementary Notes 1 to 9. <13> The form management information is journal information or payment information. The transaction management system according to Supplementary Note 12. <14> A transaction management method by a transaction management system including a transaction management device, a document management device, and a terminal device, wherein the transaction management device, the document management device, and the terminal device are connected via a network, comprising: The transaction management device displays on the terminal device a work screen for performing work using the form information described in the form. When an operation to complete the work using the form information is received on the work screen, at least a part of the form information and form image data that is an image of the form are output to the document management device. The document management device A transaction management method of storing at least a part of the form information received from the transaction management device and the form image data in a document management storage unit. <15> A display control unit that causes a terminal device to display a work screen for performing work using form information described in a form, An output unit that outputs at least a part of the form information and form image data that is an image of the form to a document management device when an operation to complete the work using the form information is received on the work screen, a transaction management device. <16> Causing a terminal device to display a work screen for performing work using form information described in a form, A transaction management program that causes a computer to execute a process of outputting at least a part of the form information and form image data that is an image of the form to a document management device when an operation to complete the work using the form information is received on the work screen.

[0320] Although the present invention has been described based on each embodiment above, the present invention is not limited to the requirements shown in the above embodiments. Regarding these points, it can be changed without departing from the gist of the present invention, and can be appropriately determined according to the application form.

Explanation of Reference Numerals

[0321] 100 Transaction management system 200 Transaction management device 240 Transaction management database 250 Transaction management unit 251 Input reception unit 252 Form recognition unit 253 Information management unit 254 Display control unit 255 Output unit 300 Document Management Device 340 Document Management Database 350 Document Management Section 400 Terminal Device

Prior Art Documents

Patent Documents

[0322]

Patent Document 1

Patent Document 2

Claims

1. A transaction management system including a transaction management device and a document management device, wherein the transaction management device has a display control unit that displays on a terminal device a work screen for performing work using the form information described in a form, and an output unit that, when receiving an operation to complete the work using the form information on the work screen, outputs to the document management device at least a part of the form information including item values of specific items required as predetermined requirements, and form image data that is an image of the form. The document management device has a storage control unit that stores in a document management storage unit at least a part of the form information received from the transaction management device and the form image data. The storage control unit stores in the document management storage unit document management information that associates at least a part of the form information with history information indicating a history of handling of the form, and includes identification information for specifying the document management information. A transaction management system.

2. The transaction management system according to claim 1, wherein at least a part of the form information includes a predetermined specific item name and its item value.

3. The transaction management system according to claim 1, wherein at least a part of the form information includes the issuer of the form, the issue date of the form, the total amount of money handled in the transaction indicated by the form, and identification information for specifying the form.

4. The document management device has a display control unit that displays on the terminal device a screen for confirming at least a part of the form information and the form image data. The display control unit displays the screen on the terminal device in a state where editing of at least a part of the form information is prohibited. The transaction management system according to claim 1.

5. The document management device transmits to the transaction management device the identification information for specifying the document management information after the document management information is stored in the document management storage unit. The transaction management device has an information management unit that stores in a transaction management storage unit transaction management information that associates the identification information for specifying the document management information with the form information. The transaction management system according to claim 1.

6. The transaction management information includes a value indicating the progress status of work on the transaction management information. The information management unit In the terminal device, an operation for instructing to cancel the transaction management information is accepted, and a value indicating a progress state of the work, which is included in the transaction management information, is set to a canceled state; The output unit is 6. The transaction management system according to claim 5, further comprising a request to cancel document management information corresponding to said transaction management information, said request being sent to said document management device.

7. The information management unit In the terminal device, an operation for canceling a state in which the contents of the transaction management information have been confirmed is accepted, and a value indicating a progress state of the work included in the transaction management information is set to a draft saved state; The output unit is 7. A transaction management system according to claim 6, wherein when an operation to reconfirm the contents of said transaction management information is accepted, a request to overwrite said document management information corresponding to said transaction management information is output to said document management device.

8. The transaction management information includes information indicating a version number of the document, The information management unit accepting input of form image data of a new version of the form, and storing, in the transaction management storage unit, form information extracted from the form image data of the new version and transaction management information associated with form information of the old version of the form; The output unit is A transaction management system as described in claim 6, which outputs to the document management device a request to cancel document management information corresponding to transaction management information including document information of the old version of the document, document image data of the new version of the document, and at least a portion of the document information extracted from the document image data of the new version.

9. The work screen is 2. The transaction management system according to claim 1, further comprising: said form image data; and form information of another form identified by identification information that identifies said form.

10. 10. The transaction management system according to claim 9, wherein the document is an invoice and the other document is a purchase order.

11. The work screen is 2. The transaction management system according to claim 1, further comprising: said form image data; and form management information for managing said form.

12. The transaction management system according to claim 11, wherein the accounting management information is journal information or payment information.

13. A transaction management method using a transaction management system including a transaction management device and a document management device, The transaction management device, a display step of displaying on a terminal device a work screen for performing work using form information written on the form; When an operation to complete an operation using the form information is received on the operation screen, at least a part of the form information, which includes item values of specific items required as predetermined requirements, and form image data that is an image of the form are output to the document management device, and an output procedure is executed. The document management device executes a storage procedure for storing at least a part of the form information received from the transaction management device and the form image data in a document management storage unit. In the storage procedure, A transaction management method for storing in the document management storage unit document management information that associates at least a part of the form information with history information indicating a history of handling of the form, and includes identification information for identifying the document management information.

14. A storage control unit that stores in a document management storage unit at least a part of the form information described in the form output from the transaction management device, which includes item values of specific items required as predetermined requirements, and form image data that is an image of the form. The storage control unit A document management device that stores in the document management storage unit document management information that associates at least a part of the form information with history information indicating a history of handling of the form, and includes identification information for identifying the document management information.

15. A document management program that causes a computer to execute a process of storing in a document management storage unit at least a part of the form information described in the form output from the transaction management device, which includes item values of specific items required as predetermined requirements, and form image data that is an image of the form. The storing process A document management program that is a process of storing in the document management storage unit document management information that associates at least a part of the form information with history information indicating a history of handling of the form, and includes identification information for identifying the document management information.

Images