Transaction management system, transaction management method, transaction management device, and transaction 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, a transaction management device, and a transaction management program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there has been known a technique for extracting form information written on a form from a form image and managing the extracted form information. Summary of the Invention [Problem to be solved by the invention]

[0003] When managing forms as electronic form information, the form information must be stored so as to meet certain requirements, such as legal requirements stipulated in the Electronic Bookkeeping Act, which makes management time-consuming.

[0004] The disclosed technology has been developed in light of the above circumstances, and aims to facilitate information management. [Means for solving the problem]

[0005] The disclosed technology is a transaction management system that includes a transaction management device, a document management device, and a terminal device, and is connected to the transaction management device, the document management device, and the terminal device via a network, wherein the transaction management device has a display control unit that displays a work screen on the terminal device for performing work using form information written on a form, and an output unit that, when an operation to complete work using the form information is received on the work screen, outputs at least a portion of the form information and form image data that is an image of the form to the document management device, and the document management device has a storage control unit that stores at least a portion of the form information and the form image data received from the transaction management device in a document management memory unit. [Effects of the Invention]

[0006] It makes it easier to manage information. [Brief explanation of the drawings]

[0007] [Figure 1] A figure showing an example of the system configuration of a transaction management system of the first embodiment. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a transaction management device. [Figure 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 1 is a first diagram showing an example of a transaction management database according to the first embodiment. [Figure 5] FIG. 2 is a first diagram illustrating an example of a document management database according to the first embodiment. [Figure 6] A diagram explaining the functional configuration of each device of the transaction management system of the first embodiment. [Figure 7] This is a first sequence diagram explaining the operation of the transaction management system of the first embodiment. [Figure 8] FIG. 10 is a first diagram illustrating a display example of the terminal device according to the first embodiment. [Figure 9] FIG. 10 is a second diagram illustrating a display example of the terminal device according to the first embodiment. [Figure 10] A second sequence diagram explaining the operation of the transaction management system of the first embodiment. [Figure 11] FIG. 10 is a second diagram showing an example of the transaction management database of the first embodiment. [Figure 12] A third sequence diagram explaining the operation of the transaction management system of the first embodiment. [Figure 13] FIG. 4 is a fourth diagram showing a display example of the drinking terminal device according to the first embodiment. [Figure 14] FIG. 10 is a fifth diagram illustrating a display example of the terminal device according to the first embodiment. [Figure 15] FIG. 10 is a second diagram illustrating an example of the document management database according to the first embodiment. [Figure 16] 10 is a first flowchart illustrating the processing of the transaction management device of the first embodiment. [Figure 17]FIG. 10 is a third diagram showing an example of a transaction management database according to the first embodiment. [Figure 18] FIG. 10 is a third diagram illustrating an example of the document management database according to the first embodiment. [Figure 19] FIG. 4 is a fourth diagram showing an example of a transaction management database according to the first embodiment. [Figure 20] FIG. 10 is a fourth diagram illustrating an example of the document management database according to the first embodiment. [Figure 21] 10 is a second flowchart illustrating the processing of the transaction management device of the first embodiment. [Figure 22] FIG. 5 is a fifth diagram showing an example of a transaction management database according to the first embodiment. [Figure 23] FIG. 6 is a sixth diagram showing an example of a transaction management database according to the first embodiment. [Figure 24] FIG. 5 is a fifth diagram illustrating an example of the document management database according to the first embodiment. [Figure 25] FIG. 6 is a sixth diagram illustrating a display example of the terminal device according to the first embodiment. [Figure 26] FIG. 7 is a seventh diagram illustrating a display example of the terminal device according to the first embodiment. [Figure 27] A diagram explaining the functional configuration of each device of the transaction management system of the second embodiment. [Figure 28] FIG. 10 is a diagram illustrating an example of a transaction management database according to the second embodiment. [Figure 29] A sequence diagram explaining the operation of the transaction management system of the second embodiment. [Figure 30] FIG. 11 is a first diagram illustrating a display example of a terminal device according to the second embodiment. [Figure 31] FIG. 11 is a second diagram illustrating a display example of the terminal device according to the second embodiment. [Figure 32] FIG. 10 is a third diagram illustrating a display example of the terminal device according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] (First embodiment) The present embodiment will be described below with reference to the drawings: Fig. 1 is a diagram showing an example of the system configuration of a 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 there is no need to distinguish between the terminal devices 400-1, 400-2, ..., 400-n, they will be referred to as terminal devices 400.

[0010] In transaction management system 100 of this embodiment, transaction management device 200, document management device 300, and 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 core system, for example, via a network. The core system is, for example, a system that performs processing corresponding to a specific application using information processed by the transaction management device 200 of this embodiment. The core system may also be, for example, software that executes processing corresponding to a specific application.

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

[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 will be referred to as a form image, and image data representing the form image will be referred to as form image data.

[0014] Furthermore, 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 information contained in the form. In the following description, the information extracted from the form is referred to as form information.

[0015] In addition, when document management information, which is information for managing document information, is input from the terminal device 400, the transaction management device 200 associates the document information with the document management information using the transaction management unit 250, creates transaction management information, and stores it in the transaction management database 240.

[0016] Furthermore, the transaction management device 200 of this embodiment transmits information including a part of the transaction management information to the document management device 300 at the timing when the content of the transaction management information is confirmed by the transaction management section 250.

[0017] Here, information that includes part of the transaction management information is information that satisfies the legal requirements stipulated in the Electronic Bookkeeping Act.

[0018] The document management device 300 of this embodiment has a document management database 340 and a document management unit 350. When the document management device 300 receives information including a portion 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 of the form corresponding to the received information with the information including the portion of the transaction management information, and stores the document management information in the document management database 340.

[0019] As a result, in the document management device 300 of this embodiment, form information is stored in a format that satisfies the legal requirements stipulated in the Electronic Bookkeeping Act.

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

[0021] More specifically, for example, terminal device 400 may be used primarily for storing the report information acquired by transaction management device 200 as transaction management information in transaction management database 240. Terminal device 400 may also be used to perform an operation to confirm the contents of the transaction management information to be stored in transaction management database 240. In other words, the operation to confirm the contents of the transaction management information is an operation to confirm the contents of the report information.

[0022] Furthermore, the terminal device 400 may be used to store information including a portion of the transaction management information acquired by the document management device 300 in the document management database 340 as document management information.

[0023] In this embodiment, when an operation to confirm the contents 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 portion of the transaction management information to the document management device 300. In other words, in response to an operation to confirm the contents of the transaction management information, the transaction management device 200 transmits information required by the provisions of the Electronic Bookkeeping Act to the document management device 300.

[0024] In the following description, information sent from the transaction management device 200 to the document management device 300 will be referred to as request information. The request information is information that meets the legal requirements stipulated in the Electronic Bookkeeping Act. Specifically, the request information may include form image data and part of the transaction management information. Furthermore, the request information may include information other than information that meets the legal requirements stipulated in the Electronic Bookkeeping Act.

[0025] The document management device 300 associates the request information received from the transaction management device 200 with the history information and the like, as document management information, and stores the document management information in the document management database 340.

[0026] In this way, in this embodiment, when a user of the service provided by the transaction management system 100 performs an operation to confirm the contents of the transaction management information, information that meets the legal requirements stipulated in the Electronic Bookkeeping Act is automatically output to and stored in the document management device 300.

[0027] Therefore, in this embodiment, manual operations by the user such as selecting transaction management information with confirmed contents in the transaction management database 240 and sending it to the document management device 300 are not required, thereby reducing the effort required for information management. Furthermore, this embodiment can prevent the occurrence of human errors such as forgetting to save information. Therefore, this embodiment can facilitate information management.

[0028] In addition, 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 multiple information processing devices.

[0029] 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 this is not limiting. 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] Furthermore, each database possessed by the transaction management device 200 and document management device 300 of this embodiment may be provided for each tenant that uses the transaction management system 100. A tenant is an organization such as a company, and may have multiple users.

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

[0032] As shown in Figure 2, the transaction management device 200 is constructed by a computer and, as shown in Figure 2, is equipped with a CPU 201, a ROM 202, a RAM 203, a 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] Of these, the CPU 201 controls the overall operation of the transaction management device 200. The ROM 202 stores programs used to drive the CPU 201, such as an 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 and writing of various data from and to the HD 204 under the control of the CPU 201. The display 206 displays various information, such as a cursor, menu, window, text, or image. The external device connection I / F 208 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I / F 209 is an interface for data communication using a communication network. The bus line 210 is an address bus, data bus, etc. for electrically connecting the various components, such as the CPU 201, shown in FIG. 2.

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

[0035] The hardware configuration of the document management device 300 of this embodiment is the same as that of the transaction management device 200, and therefore a description thereof will be omitted.

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

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

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

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

[0040] The terminal device 400 also includes a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an image sensor 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] Of 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 type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 401. The image sensor 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 vibrations to generate sound such as music or voice. The sound input / output I / F 417 is a circuit that processes the input and output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401.

[0042] The display 418 is a type of display means such as a liquid crystal display or organic electroluminescence (EL) display that displays an image of a subject, various icons, etc. The external device connection I / F 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 that allows a user to operate the terminal device 400 by pressing the display 418. The display 418 is an example of a display unit that the terminal device 400 has.

[0043] 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.

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

[0045] Figure 4 is a first diagram showing an example of a transaction management database according to the first embodiment. The transaction management database 240 according to this embodiment is an example of a transaction management information storage unit that stores transaction management information. It is managed for each tenant in the transaction management device 200. In the following explanation, an invoice will be used as an example of a form.

[0046] The transaction management information stored in the transaction management database 240 includes information items such as a form ID, an electronic document ID, a file path, a transfer format, a registration date and time, a status, a confirmation date and time, invoice information, payment information, and accounting information, and each item is associated with a tenant name "M Corporation." 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] Furthermore, the item "document ID" is associated with other items in the transaction management database 240. In this embodiment, information in the transaction management database 240 that includes 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 "Form ID" is form identification information for identifying a form (invoice) in transaction management device 200. In other words, the value of the item "Form ID" is identification information for identifying transaction management information.

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

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

[0051] The value of the item "Delivery format" is information that specifies the format in which the form was received by the user of the transaction management system 100. Specifically, if the value of the item "Delivery format" is "electronic," it indicates that the form was received as form image data, and if the value of the item "Delivery format" is "paper," it indicates that the form was received on paper.

[0052] The value of the item "Registration Date and Time" indicates the date and time when the form information was stored in the transaction management database 240.

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

[0054] In this embodiment, the transaction management information includes four states: unprocessed state, draft saved state, confirmed state, and externally output state. Each state is as follows:

[0055] Unprocessed state (state 1): This is the state immediately after form information has been acquired from form image data, and no confirmation or input work has been performed.

[0056] · Draft saved state (state 2) This is the state in which the report information included in the transaction management information is being checked or various input tasks are being performed, and the contents of the transaction management information have not yet been finalized.

[0057] Confirmed state (state 3): The contents of the transaction management information have been confirmed and stored in the transaction management database 240.

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

[0059] The canceled state is a state in which the transaction management information before being set to the confirmed state is treated as if it had been deleted, while remaining stored in the transaction management database 240.

[0060] In addition to these four states, the transaction management information may also have other states, such as an output state, which indicates that the output of the transaction management information to the core system has been completed.

[0061] The value of the "Confirmed Date and Time" field indicates the date and time when the contents of the transaction management information were confirmed. In other words, the value of the "Confirmed Date and Time" field indicates the date and time when the value of the "Status" field of the transaction management information became "Confirmed."

[0062] The value of the item "invoice information" indicates form information extracted from the form image data. Note that in the example of Fig. 4, an invoice is used as an example of a form, but the form may be something other than an invoice.

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

[0064] The value of the "Invoice Source" item indicates the tenant that issued the invoice. In other words, the value of the "Invoice Source" item indicates the issuer of the document. The value of the "Invoice Number" item is identification information used to identify the invoice, and is identification information assigned to the invoice by the invoice source. The value of the "Invoice Date" item indicates the date the invoice was created. The value of the "Invoice Total Amount" item indicates the total invoice amount. In other words, the value of the "Invoice Total Amount" item indicates the total amount handled in the transaction indicated by the document identified by the document ID.

[0065] The value of the item "Payment Information" is information indicating the payee of the total bill amount, and may be information extracted from the form image data. In other words, the payment information may be part of the form information. The item "Payment Information" includes items such as "Bank Name," "Branch Name," and "Account Number." The values ​​of the items "Bank Name," "Branch Name," and "Account Number" indicate the bank name, branch name, and account number to which payments are made.

[0066] The item "journal entry information" corresponds to various items related to journal entries, and the value of the item "journal entry information" includes various items related to journal entries and the values ​​of those items. Journal entry information is information entered by the recipient of the form.

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

[0068] In addition, in the transaction management information 41, the value of the delivery format is "paper", the value of the status is "unprocessed", and the value of the confirmed date and time is blank.

[0069] Therefore, in the example of Figure 4, the document image data identified by the document ID included in the transaction management information 41 is document image data obtained by scanning a paper document using an image forming device, etc., and it can be seen that tasks such as confirming the document information (invoice information) and entering the accounting information have not been completed, and the contents of the transaction management information 41 have not been finalized.

[0070] In the transaction management information 41, items with blank values ​​will have values ​​stored in them as the processing described below is executed.

[0071] In addition, in the transaction management information of this embodiment, the items "Report ID," "Billing Source," "Invoice Number," "Billing Date," and "Total Invoice Amount" and their item values ​​may be included in the request information. In other words, the request information is a specific item name and item value included in the transaction management information, and further includes a portion of the report information included in the transaction management information.

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

[0073] 5 is a first diagram showing an example of a document management database according to the first embodiment. The document management database 340 according to the present 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 device 300.

[0074] The document management database 340 includes information items such as electronic document ID, type, delivery format, business partner name, transaction date, total amount, form 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." Furthermore, the document management information is associated with the tenant name "M Corporation."

[0075] The value of the "Type" field indicates the type of report corresponding to the transaction management information. The value of the "Customer Name" field indicates the issuer (biller) of the report. The value of the "Transaction Date" field indicates the date the report was issued (billing date). The value of the "Total Amount" field indicates the total amount (total billing amount) handled in the transaction corresponding to the report.

[0076] In other words, the items "Customer Name," "Transaction Date," and "Total Amount" and their values ​​included in the document management information of this embodiment are part of the required information equivalent to the items "Billing Destination," "Billing Date," and "Total Billing Amount" and their values ​​in the transaction management information, and can be said to be items required to meet the legal requirements stipulated in the Electronic Bookkeeping Act.

[0077] The requirements stipulated in the Electronic Bookkeeping Act are one example of the predetermined requirements when managing documents as electronic document information, and the predetermined requirements may also be in-house rules, industry standards, etc.

[0078] Furthermore, these items required to meet the legal requirements stipulated in the Electronic Bookkeeping Act are just examples, and if at least some of the legal requirements stipulated in the Electronic Bookkeeping Act are added, changed, deleted, etc., the items required to meet the legal requirements may also be added, changed, deleted, etc.

[0079] The value of the item "Report ID" is the report ID included in the transaction management information corresponding to the document management information. The value of the item "Report 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 "Memo" item indicates additional information that is automatically entered when the document management information is stored in the document management database 340. The additional information may include the form ID included in the transaction management information corresponding to the document management information. The value of the "Confirmation Status" item indicates whether visual confirmation of the request 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 request information included in the document management information was received by the document management device 300. Specifically, the value of the item "document management registration date and time" may be the value of the item "confirmation date and time" of the transaction management information corresponding to the document management information.

[0082] The value of the item "document management registered user" is information that identifies the user who visually confirmed the contents 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 report 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 report information in the transaction management device 200.

[0084] The value of the item "Original Confirmation" indicates whether a visual comparison has been made between the original document and the document image data stored in the transaction management device 200. If the value of the item "Original Confirmation" is "Confirmed," this indicates that a comparison has been made between the original document and the document image data.

[0085] The value of the item "original confirmation date and time" indicates the date and time when the original of the form was compared with the form image data, and the value of the item "original confirmation user" is information that identifies the user who performed the comparison.

[0086] 5, it can be seen that the invoice identified by the electronic document ID "5679" and the form ID "1238" was delivered in paper form by a business partner, Corporation C, and that the request information extracted from this invoice was not confirmed. Furthermore, it can be seen from the document management information 51 that a visual comparison between the form and the form image data was performed by User X, and that the form information including the request information was registered in the transaction management device 200 by User X. Furthermore, it can be seen that the contents of the document management information 51 were confirmed by User Y.

[0087] In the document management information 51, items with blank values ​​are filled with values ​​as the processing described below is executed.

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

[0089] Next, the functional configuration of each device included in the transaction management system 100 of this embodiment will be described with reference to Fig. 6. Fig. 6 is a diagram illustrating the functional configuration of each device included in the transaction management system of the first embodiment.

[0090] First, we will explain the functions of transaction management device 200. Transaction management device 200 of this embodiment has transaction management database 240 and transaction management unit 250, and transaction management unit 250 includes input reception unit 251, document recognition unit 252, information management unit 253, display control unit 254, and output unit 255.

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

[0092] The form recognition unit 252 extracts form information by performing form recognition processing on the form image data received by the input reception unit 251. Specifically, the form recognition processing of this embodiment is processing of extracting the names of items (items) and the values ​​of these items (item values) included in the form image indicated by the form image data, converting the items and the item values ​​into text data, and associating them with each other.

[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 so on.

[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] In this embodiment, output includes transmission of information. Furthermore, 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 a network.

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

[0098] The input receiving 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 request information received from the transaction management device 200 in the document management database 340. In addition, the storage control unit 352 updates the document management information stored in the document management database 340 in response to 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 has an input receiving unit 430, a display control unit 440, and a communication unit 450. The input receiving 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, the operation of the transaction management system 100 of this embodiment will be described with reference to Figure 7. Figure 7 is a first sequence diagram explaining the operation of the transaction management system of the first embodiment. Figure 7 explains the operation until the contents of the transaction management information are confirmed in the transaction management device 200.

[0102] In this embodiment, in the example of FIG. 7, it is assumed that the user of terminal device 400 has already performed the login process required when using the services provided by transaction management device 200.

[0103] In addition, in this embodiment, the user may be a user belonging to a tenant, and through the login process, the transaction management database 240 referenced in response to an operation from the terminal device 400 may be identified as the transaction management database 240 of the tenant to which the user belongs.

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

[0105] When the input receiving unit 251 of the transaction management unit 250 receives input of the form image data, the transaction management device 200 performs form recognition processing using the form recognition unit 252 to extract form information (step S703).

[0106] Specifically, the form recognition unit 252 acquires characters and their coordinate values ​​written on the form image using an OCR (Optical Character Reader), and identifies the character string based on the coordinate values.The form recognition unit 252 then extracts item values ​​corresponding to the items to be extracted in accordance with definition information that defines the items and item values ​​of the items to be extracted, and associates the items with the item values.The definition information may be stored in advance in the transaction management device 200.

[0107] Next, the transaction management unit 250 causes the information management unit 253 to identify the form transfer format and the form type that are the source of the form image data (step S704).

[0108] Specifically, if the form image data acquired in step S702 is image data to which no text data is attached, the information management unit 253 specifies the form transfer format as "electronic." Also, if the form image data is image data to which text data is attached, the information management unit 253 specifies the form transfer format as "paper."

[0109] Furthermore, the information management unit 253 identifies the type of the form based on the form information extracted in step S703.

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

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

[0112] Next, the terminal device 400 receives an operation to instruct the display of a list screen of transaction management information through the input receiving unit 430 (step S706). Next, the terminal device 400 transmits a display request of the list screen to the transaction management device 200 through the communication unit 450 (step S707).

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

[0114] Next, 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] Next, the transaction management device 200 causes the display control unit 254 to send an instruction to the terminal device 400 to display a list screen (step S710). Details of the list screen will be described later.

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

[0117] Next, when the terminal device 400 accepts an operation to select the transaction management information for which the contents will be confirmed (step S712), it sends a request to the transaction management device 200 to display a confirmation screen for the selected transaction management information (step S713).

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

[0119] Next, transaction management device 200 transmits a display instruction for a confirmation screen of the transaction management information to terminal device 400 via 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 for the selected transaction management information on the display 418 (step S717). Note that the confirmation screen in this embodiment is an example of a screen displayed using form information, and is an example of a work screen for the user of the terminal device 400 to perform work (confirmation work) using the form information.

[0121] Next, the terminal device 400 accepts input of form management information, correction of form information, etc. through the input accepting unit 430 (step S718). Note that the transaction management device 200 may update the transaction management information in the transaction management database 240 every time form management information is input into the terminal device 400.

[0122] Next, the terminal device 400 receives an operation to confirm the contents of the transaction management information through the input receiving unit 430 (step S719). Note that, in this embodiment, the operation to confirm the contents is an operation to complete the work using the form information.

[0123] When an operation to confirm the contents is performed, terminal device 400 transmits an update request to transaction management device 200 to request an update of the status of the transaction management information (step S720).

[0124] When the transaction management device 200 receives an input update request, the information management unit 253 associates the input report management information with the report information and stores it in the transaction management database 240, changes the value of the "status" item in the transaction management information to "confirmed," and confirms the contents of the transaction management information (step S721).

[0125] At this time, the transaction management device 200 may display a screen on the terminal device 400 for selecting whether or not to send the request information included in the transaction management information that has been set to the confirmed state to the document management device 300. Then, when the transaction management device 200 receives an operation to instruct the sending of the request information, it may perform a process to send the request information. The process of sending the request information will be described in detail later.

[0126] The above is the operation until the contents of the transaction management information are confirmed. Next, an example of the display on the terminal device 400 will be described with reference to FIG.

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

[0128] The screen 80 shown in Figure 8 includes display areas 81 and 82. The display area 81 displays information identifying the user who is logged in to the transaction management system 100 and who requested the display of the list screen in step S706 of Figure 7.

[0129] In other words, the information displayed in the display area 81 is information that identifies the user who will check the contents of the transaction management information, enter the report management information, etc., and is the value of the item ``Transaction management registered user'' in the document management information corresponding to the transaction management information.

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

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

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

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

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

[0135] The display area 92 displays a form image corresponding to the transaction management information 41. Furthermore, when an operation button 96 (described later) is operated, the window 92a is displayed on the screen 91 if the user of the terminal device 400 has not performed the login process required to use the services 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 it may be displayed anywhere within the screen 91.

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

[0137] Display area 93 displays the status of the transaction management information. More specifically, display area 93 displays the value of the "Status" item included in the transaction management information. In transaction management database 240, the value of the "Status" item of transaction management information 41 is "Unprocessed," so "Unprocessed" is displayed in display area 93. Display area 94 displays transaction management information 41. More specifically, display area 94 has display areas 94a and 94b, with report information displayed in display area 94a and an input field for report management information displayed in display area 94b.

[0138] The form information included in the transaction management information 41 is invoice information. Therefore, the display area 94a displays the invoice information included in the transaction management information 41. Furthermore, the form management information included in the transaction management information 41 is journal information, etc. Therefore, the display area 94b displays input fields for inputting item values ​​for the items of the journal information included in the transaction management information 41.

[0139] The operation button 96 is an operation button for changing the state of the transaction management information 41 to a confirmed state. In other words, the operation button 96 is an operation button for confirming the contents of the transaction management information 41.

[0140] The operation button 97 is an operation button for changing the state of the transaction management information 41 to a draft saved 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 confirmed state. In other words, the operation button 98 is an operation button for changing the state of the transaction management information 41 that has been set to the confirmed state back to the draft saved state.

[0142] Operation button 99 is an operation button for canceling the storage of transaction management information 41 in transaction management database 240. In other words, operation button 99 is an operation button for changing the state of transaction management information 41 to a canceled state. A canceled state is a state in which the corresponding transaction management information is not deleted from transaction management database 240, but is considered to have been deleted in appearance.

[0143] In this embodiment, when the operation button 96 is operated after the contents of the display area 94a on the screen 91 have been confirmed and information has been entered into the input fields displayed in the display area 94b, the status of the transaction management information 41 becomes "confirmed." Thus, in this embodiment, work using the form information includes the work of correcting the contents of the form information and the work of entering information into the input fields.

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

[0145] The operation up to the storage of document management information in document management database 340 will be described below with reference to Fig. 10. Fig. 10 is a second sequence diagram illustrating the operation of the transaction management system of 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 confirmed 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 has been performed (step S1001).

[0147] Upon receiving the confirmation request, the document management device 300 checks whether user authentication has been performed (step S1002).

[0148] The following processing from step S1003 to step S1010 is the operation when user authentication has not been performed.

[0149] If user authentication has not been performed, the document management device 300 transmits an authentication request to the transaction management device 200 requesting user authentication (step S1003).

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

[0151] Terminal device 400 receives the display instruction and causes display control unit 440 to display the authentication screen on display 418 (step S1005). Next, when terminal device 400 receives input of authentication information (step S1006), it transmits a request to transaction management device 200 to execute authentication (step S1007). Transaction management device 200 transmits this execution request to 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 user authentication has been performed is transmitted to the transaction management device 200.

[0153] When the transaction management device 200 receives this notification, the output unit 255 transmits a registration request including the request information to the document management device 300 (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 request information through the input receiving unit 351, the storage control unit 352 stores the request information in the document management database 340 (step S1012). Specifically, the document management device 300 assigns a new electronic document ID to the request information through the storage control unit 352 and stores the request information in the document management database 340 as document management information.

[0155] Next, the document management device 300 transmits a completion notification to the document management device 300 indicating that the registration of the request information has been completed (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 the completion notification.

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

[0157] Next, the transaction management device 200 transmits to the terminal device 400 a notification indicating that the registration of the request information in the document management device 300 has been completed (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 and the registration have been completed (step S1016).

[0159] The above is the operation up to the point where the document management information is stored in the document management database 340 .

[0160] The transaction management database 240 after the request information is sent to the document management database 340 will be described below with reference to Fig. 11. Fig. 11 is a second diagram showing an example of the transaction management database of the first embodiment.

[0161] 11, the value of the item "Status" of transaction management information 41a is set to "Confirmed," and the values ​​of the items "Electronic Document ID" and "Confirmation Date and Time" are stored. Also, in transaction management information 41a, values ​​of the items corresponding to the item "Journalization Information" are entered.

[0162] Therefore, it is understood that the contents of the transaction management information 41a are in a confirmed state, and furthermore, the request information included in the transaction management information 41a is registered in the document management device 300.

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

[0164] The operation up to confirmation of document management information in document management device 300 will be described below with reference to Fig. 12. Fig. 12 is a third sequence diagram illustrating 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 from a user instructing to display a list screen of document management information (step S1201), the terminal device 400 transmits a request to display the list screen to the document management device 300 (step S1202).

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

[0167] Next, 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] Next, the document management device 300 causes the display control unit 353 to send a display instruction for the list screen to the terminal device 400 (step S1205). Details of the list screen will be described later.

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

[0170] Next, when the terminal device 400 receives an operation to select the document management information for which the contents are to be confirmed (step S1207), it sends a request to the document management device 300 to display a confirmation screen for the selected document management information (step S1208).

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

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

[0173] Upon receiving this display instruction, the terminal device 400 causes the display control unit 440 to display a confirmation screen for the selected document management information on the display 418 (step S1212).

[0174] The above is the operation up to the time when the confirmation screen for document management information is displayed on the terminal device 400.

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

[0176] A 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.

[0177] The screen 131 includes display areas 132 and 133. The display area 132 displays information that identifies a user who is authorized to use the services provided by the document management device 300. In other words, the information displayed in the display area 132 is information that identifies a user who will check the contents of the document management information, and is the value of the item "document management registered user" in the document management information.

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

[0179] In this manner, in this embodiment, the user who stores the transaction management information in the transaction management database 240 may be different from the user who stores the document management information in the document management database 340.

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

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

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

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

[0184] The screen 141 includes display areas 132, 143, 144, and 145, and an operation button 146. In the display area 143, the document management information 51 and the corresponding form image are displayed.

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

[0186] The display area 145 includes display areas 145a and 145b and an operation button 145c. The display area 145a displays the item values ​​acquired as the request information.

[0187] In the example of Figure 14, the item values ​​obtained as request information are the value of the item "billing source", the value of the item "billing date", and the value of the item "total billing amount", and are displayed as the value of the item "client name", the value of the item "transaction date", and the value of the item "total amount", respectively.

[0188] Furthermore, the document management device 300 of this embodiment displays the values ​​of the items "Customer Name," "Transaction Date," and "Total Amount" shown in the display area 145a in a state where editing is prohibited.

[0189] Display area 145b displays the form ID included in the transaction management information as information for identifying 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 identifying the transaction management information 41 corresponding to the document management information 51.

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

[0191] The operation button 146 is an operation button for setting the confirmation status of the document management information to "completed." 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] The document management database 340 after confirmation of the contents of the document management information is completed will be described below with reference to Fig. 15. Fig. 15 is a second diagram showing an example of the document management database of the first embodiment.

[0193] 15, the value of the item “confirmation status” of the document management information 51a is “completed.” Therefore, it can be seen that the document management information 51a is in a state where confirmation of the contents has been completed.

[0194] As described above, in this embodiment, when the content of the form information extracted from the form image data is confirmed, the specific item names and item values ​​contained 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, form information is automatically stored in the document management device 300 in a format that also satisfies the requirements of the Electronic Bookkeeping Act. Therefore, in this embodiment, after importing form image data, special work to satisfy the provisions of the Electronic Bookkeeping Act is not required, and the effort required for information management can be reduced. Furthermore, according to this embodiment, human errors such as forgetting to save form information in a format that also satisfies the requirements of the Electronic Bookkeeping Act can be eliminated.

[0196] In this embodiment, the transaction management device 200 can cancel and overwrite transaction management information before it is set to a confirmed state.

[0197] The cancellation and overwriting of transaction management information will be explained below. Figure 16 is a first flowchart illustrating the processing of the transaction management device of the first embodiment.

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

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

[0200] Next, transaction management device 200 determines whether input receiving unit 251 has received an operation to confirm the contents of the transaction management information from terminal device 400 (step S1602).

[0201] If a confirmation operation is not received in step S1602, the transaction management device 200 determines whether an operation to cancel the transaction management information has been received by the input receiving unit 251 (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.

[0202] If the cancel operation is not accepted in step S1603, 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, if the operation button 99 is operated, the transaction management device 200 transmits the form ID to the document management device 300 via the output unit 255 and requests cancellation and registration of the document management information including the form ID. In addition, the transaction management device 200 updates the value of the "Status" item of the transaction management information including the form ID acquired in step S1601 to "Cancelled" in the transaction management database 240 via the information management unit 253 (step S1605), and terminates the processing.

[0204] Upon receiving the cancellation registration, the document management device 300 updates the value of the item "confirmation status" of the document management information including the form ID to "cancelled."

[0205] Also, in step S1602, if the operation button 96 is operated, the transaction management device 200 acquires the value of the item "confirmed date and time" from the transaction management information including the form ID acquired in step S1601 (step S1606). Next, the transaction management device 200 determines whether the acquired value of the item "confirmed 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 a first operation. If the value of the item "Confirmation Date and Time" is blank, the confirmation operation in step S1602 is a first operation. On the other hand, if the value of the item "Confirmation Date and Time" is not blank, the operation in step S1602 is an operation performed again after the confirmation was once released.

[0207] In step S1607, if the value of the item "Confirmed date and time" is empty, the transaction management device 200 sends request information to the document management device 300 via the output unit 255, requesting new registration of document management information. In addition, the transaction management device 200 updates the value of the item "Status" of the transaction management information to "Confirmed" via the information management unit 253 (step S1608), and terminates the processing.

[0208] Upon receiving the new registration request, the document management device 300 stores 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 specified storage area, and store a file path indicating the specified storage area as part of the document management information in the document management database 340. 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 as part of the transaction management information corresponding to the form ID.

[0209] In step S1607, if the value of the item "Confirmed Date and Time" is not empty, the transaction management device 200 sends the report ID acquired in step S1601 and the request information to the document management device 300, requests overwrite registration of the document management information (step S1609), and terminates processing.

[0210] An example of a case where the value of the item "Confirmed date and time" is not blank is when, on the screen 91 shown in Fig. 9, the operation button 98 is operated to change the state of the transaction management information from the confirmed state to the draft saved state, and then the operation button 99 is operated again. When the document management device 300 receives a request for overwrite registration, it identifies the document management information including the form ID and overwrites the requested information included in the document management information.

[0211] 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 below with reference to FIGS.

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

[0213] In transaction management database 240B, transaction management information 41b has the value of the item "Status" set to "Cancelled," indicating that transaction management information 41b has been set to a canceled state. Therefore, in transaction management database 240B, transaction management information 41b is treated as information that appears to have been deleted.

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

[0215] In the document management database 340B, the value of the item "confirmation status" of the document management information 51b is "cancelled," which indicates that the document management information 51b has been put into a canceled state. Therefore, in the document management database 340B, the document management information 51b is treated as information that appears to have been deleted.

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

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

[0218] When new form image data is acquired in the transaction management information 41c that is in a draft state, the transaction management device 200 overwrites the form information.

[0219] In the transaction management information 41c shown in FIG. 19, it can be seen that the form information has been overwritten and the value of the item "total billing amount" has been updated from the value in the transaction management information 41b shown in FIG.

[0220] Furthermore, in the transaction management device 200, when a confirmation operation is performed again after the confirmed state has been released once, 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 "Confirmed date and time" is updated to the date and time when the second confirmation operation was performed. Then, the transaction management device 200 sends an overwrite registration request to the document management device 300.

[0221] 20 is a fourth diagram showing an example of the document management database according to 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 overwrite registration of the document management information 51b.

[0222] In the document management database 340C, the request information is updated in response to the overwrite registration, and it can be seen that the value of the item "Total Amount" in the document management information 51c has been updated from the value of the item "Total Amount" in the document management information 51b shown in Fig. 18. Furthermore, 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] In addition to the above-described cancellation and overwriting, in this embodiment, transaction management information that has been set to a confirmed state may be replaced.

[0224] In this embodiment, when a form is replaced, transaction management information that has been confirmed is replaced.

[0225] In addition, in this embodiment, the transaction management information includes a version ID indicating the version number of the document, and the version ID is included in the request information sent from the transaction management device 200 to the document management device 300, so that the request information corresponding to the replaced document is stored in the document management device 300.

[0226] Below, we will explain the case where transaction management information is replaced in addition to being canceled and overwritten, with reference to Figure 21. Figure 21 is a second flowchart explaining the processing of the transaction management device of 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 therefore the description thereof will be omitted.

[0228] In step S2107, if the value of the item "confirmed date and time" is blank, the value of the item "version ID" is obtained from the transaction management information including the form ID (step S2108).

[0229] Next, the transaction management device 200 determines whether the value of the item "version ID" is null (step S2109).

[0230] If the value of the item "Determined Date and Time" and the value of the item "Version ID" are both blank, the transaction management information is newly registered.

[0231] Therefore, in step S2109, if the value of the item "Version ID" is empty, the transaction management device 200 sends request information to the document management device 300 via the output unit 255, requesting new registration of document management information. In addition, the transaction management device 200 updates the value of the item "Status" of the transaction management information to "Confirmed" via the information management unit 253 (step S2110), and terminates the processing.

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

[0233] If the value of the item "Version ID" is not empty, it indicates that the form has been replaced. Therefore, the transaction management device 200 acquires the form ID of the form whose transaction management information was previously confirmed.

[0234] Next, the transaction management device 200 sends the acquired form ID to the document management device 300 and requests cancellation and registration of the document management information including the form ID. In addition, the transaction management device 200, via the information management unit 253, updates the value of the "Status" item of the transaction management information including the form ID acquired in step S2111 to "Cancelled" in the transaction management database 240 (step S2112), and terminates the processing.

[0235] Upon receiving the cancellation registration, the document management device 300 updates the value of the item "confirmation status" of the document management information including the form ID to "cancelled."

[0236] Also, in step S2107, if the value of the item "confirmed date and time" is not blank, the transaction management device 200 proceeds to step S2113. The processing of step S2113 is the same as the processing of step S1609 in Figure 16, so a description thereof will be omitted.

[0237] The process of replacing a form will be specifically described below with reference to FIGS.

[0238] Fig. 22 is a fifth diagram showing an example of the 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 transaction management information 41d-1, the version ID corresponding to the form ID "1238" is "1." Also, in 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, transaction management information 41d-1 is transaction management information that includes form information extracted from the form identified by the form ID "1238."

[0241] Additionally, transaction management information 41d-2 is transaction management information that includes form information extracted from a revised version of the form identified by form ID "1238." Furthermore, the form identified by form ID "1238-2" has a version ID of "2," which indicates that it is the second version of the form.

[0242] In the following description, a form before revision will be referred to as an old version of the form, and a newly issued revised form will be referred to as a new version of the form.

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

[0244] 22, the value of the "Status" item in transaction management information 41d-1 is "Confirmed," and the value of the "Electronic Document ID" item is stored. Also, in the example of FIG. 22, the value of the "Status" item in transaction management information 41d-2 is "Unprocessed," and the value of the "Electronic Document ID" item is blank.

[0245] Therefore, in the example of Figure 22, for the old version of the form, the request information has been sent to the document management device 300 and stored in the document management database 340, and for the new version of the form, the contents of the transaction management information 41d-2 have not been confirmed and the request information has not been sent to the document management device 300.

[0246] Figure 23 is a sixth diagram showing an example of a transaction management database according to the first embodiment. The transaction management database 240E shown in Figure 23 shows the state after an operation to confirm the contents of the transaction management information corresponding to the form identified by the form ID "1238" and the version ID "2" has been performed on the terminal device 400.

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

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

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

[0250] Fig. 24 is a fifth diagram showing an example of the document management database according to the first embodiment. Document management database 340D shown in Fig. 24 shows the state after transaction management information 41d-2 and corresponding request information have been sent from transaction management device 200 to document management device 300.

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

[0252] 24, the value of the item "Verification Status" of document management information 51d-1 is "Cancelled," and the value of the item "Verification Status" of document management information 51d-2 is "Incomplete." Therefore, in document management database 340D, document management information 51d-1 is in the canceled state, and the contents of document management information 51d-2 are to be confirmed.

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

[0254] In this embodiment, when request information corresponding to form information extracted from a form is stored in the document management device 300 and the form is then revised, the request information corresponding to the form information of the old version of the form before revision stored in the document management device 300 is canceled. Then, the document management device 300 stores the request information corresponding to the form information of the new version of the form in association with the form ID that identifies the new version of the form.

[0255] Therefore, in this embodiment, it is possible to replace (revise) a form in the document management device 300. Also, in this embodiment, it is possible to keep a history of form replacement in the document management device 300.

[0256] An example of the display on the terminal device 400 when replacing a form will be described below with reference to FIGS.

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

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

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

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

[0261] Fig. 26 is a seventh diagram showing an example of a display on the terminal device of the first embodiment. Screen 91B shown in Fig. 26 is another example of a confirmation screen for transaction management information 41d-2.

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

[0263] The display area 92B includes an operation button 92b and a window 92c, which displays a list of form image data of old versions of forms.

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

[0265] In this way, the transaction management system 100 of this embodiment can cancel, overwrite, and replace document information. In addition, the transaction management system 100 of this embodiment can keep a history showing that cancellation, overwriting, and replacement have been performed.

[0266] (Second embodiment) The second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that form recognition processing is not performed. 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 assigned the same reference numerals as those used in the description of the first embodiment, and descriptions thereof will be omitted.

[0267] FIG. 27 is a diagram illustrating the functional configuration of each device 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 receiving 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 form information and the like from the terminal device 400 or the external system 500.

[0271] Specifically, for example, the information acquisition unit 256 may acquire information linking form image data and form information corresponding to the form image data from the terminal device 400. In this case, the transaction management device 200A simply associates the form image data with the form information and stores them in the transaction management database 240A, eliminating the need for form recognition processing to extract the form information from the form image data.

[0272] The information linking the form image data with the form information corresponding to the form image data may be, for example, information linking PDF data of an invoice with text data extracted from the PDF data.

[0273] In this embodiment, when form information is acquired from the terminal device 400 in this way, the form information acquired from the terminal device 400 is displayed as is in the display area 94a of the display area 94 on the screen 91. Therefore, in this embodiment, there is no need to modify the form information displayed in the display area 94a. Therefore, in this embodiment, the only work performed on the screen 91 using form information is inputting data into the input fields displayed in the display area 94b.

[0274] Furthermore, the information acquisition unit 256 may acquire, for example, form information of other forms identified from the form information acquired from the terminal device 400 from the external system 500, and store the information in the transaction management database 240A.

[0275] External system 500 may be, for example, a system that manages, in association with each other, the form information acquired by transaction management device 200A from terminal device 400 and the form indicated by this form information and the form information of the corresponding form. Specifically, external system 500 may manage, in association with each other, invoice information acquired by transaction management device 200A from terminal device 400 and 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 for the external system 500 based on the billing source, invoice number, etc. included in the form information acquired from the terminal device 400. In other words, the information acquisition unit 256 searches for the external system 500 based on the form identification information included in the form information acquired from the terminal device 400.

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

[0278] 4, the transaction management database 240A of this 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 purchase order information acquired by the information acquisition unit 256 from the external system 500.

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

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

[0281] The value of the item "Order Destination" is a value that identifies the order destination, and in Figure 28 it shows the name of the tenant that is the order destination. The value of the item "Order Form Number" is identification information that identifies the order form. The value of the item "Order Total Amount" shows the total amount of the order indicated by the order form.

[0282] In this embodiment, 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 contents of the invoice against the contents of the order form.

[0283] Next, the operation of the transaction management system 100A of this embodiment will be described with reference to Figure 29. Figure 29 is a sequence diagram illustrating the operation of the transaction management system of the second embodiment.

[0284] In FIG. 29, the processes in steps S2901 and S2902 and the processes in steps S2903 and after are performed at separate, independent timings.

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

[0286] The processes of steps S2901 and S2902 may be performed every time the transaction management device 200A acquires form image data and form information from the terminal device 400.

[0287] The processing from step S2903 to step S2909 in FIG. 29 is the same as the processing from step S706 to step S712 in FIG. 7, and therefore a description thereof will be omitted.

[0288] In step S2908, when the terminal device 400 accepts an operation to select the transaction management information for which the contents will be confirmed (step S2909), it sends a request to the transaction management device 200A to display a matching screen for the invoice information and order form information contained in the selected transaction management information (step S2910).

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

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

[0291] Upon receiving this display instruction, the terminal device 400 causes the display control unit 440 to display the matching screen on the display 418 (step S2914).

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

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

[0294] 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, and therefore the description thereof will be omitted.

[0295] Next, a description will be given of a display example on the terminal device 400 of this embodiment. Fig. 30 is a first diagram showing a display example on the terminal device of the second embodiment.

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

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

[0298] Display area 95 displays form information extracted from the form corresponding to the form indicated by the form image displayed in display area 92. The form whose form image is displayed in display area 92 and the form whose form nutritional information is displayed in display area 95 are identified in step S2911 of FIG.

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

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

[0301] In this embodiment, when operation button 96 is operated on screen 91C, an update request is sent to transaction management device 200A to request an update of the status of the transaction management information. With this operation, transaction management device 200A determines that the work on the work screen has been completed, and changes the value of the "Status" item in the transaction management information in transaction management database 240A to "Confirmed," thereby confirming the contents of the transaction management information.

[0302] Once the contents of the transaction management information are confirmed, transaction management device 200A transmits information including a part of the transaction management information to document management device 300.

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

[0304] In this embodiment, the work screen for performing work using form information may include form 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 an example of a display on the terminal device of the second embodiment.

[0306] Screen 91D shown in Figure 31 is an example of a work screen for performing work using report information, and shows the state in which an operation is performed to display an input field for entering journal information on the confirmation screen displayed in step S717 of Figure 7, and the journal information has been entered.

[0307] The screen 91D includes tabs 94d and 94e for selecting input fields to be displayed in the display area 94c. In this embodiment, when the tab 94d is selected, input fields for journal information are displayed in the display area 94c, and when the tab 94e is selected, input fields for journal information are displayed in the display area 94c.

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

[0309] In this embodiment, when the operation button 96 is operated on the screen 91D, the contents of the transaction management information are confirmed.

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

[0311] On screen 91E, tab 94e is selected, and input fields for inputting payment information are displayed in display area 94c. Also on screen 91E, journal information is entered in the input fields displayed in display area 94c.

[0312] In this embodiment, by displaying the accounting information and payment information, which are document management information, together with the document information on the work screen, the user of the terminal device 400 can confirm the accounting information and payment information and the contents of the automatically entered document information.

[0313] In addition, in this embodiment, a part of the transaction management information can be sent to the document management device 300 at the timing when confirmation of the contents of the form management information and the form information is completed.

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

[0315] Additionally, the devices described in each embodiment represent only one of multiple computing environments for implementing the embodiments disclosed herein.

[0316] In some embodiments, transaction management apparatus 200 and document management apparatus 300 may include multiple computing devices, such as a server cluster, configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein. Similarly, transaction management apparatus 200 and document management apparatus 300 may include multiple computing devices configured to communicate with each other.

[0317] Furthermore, transaction management device 200 and document management device 300 can be configured to share the disclosed processing steps in various combinations. For example, a process performed by a specific unit can be performed by transaction management device 200. Similarly, the functions of a specific unit can be performed by transaction management device 200. Furthermore, the elements of transaction management device 200 and document management device 300 may be integrated into a single server device or may be separated into multiple devices.

[0318] The device that provides the form image data is not limited to an image forming device as long as it has a communication function. The device that provides the form image data may be, for example, a projector (PJ), an interactive whiteboard (IWB: an electronic whiteboard with a blackboard function that allows mutual communication), an output device such as digital signage, a head-up display (HUD) device, industrial machinery, an imaging device, a sound collection device, a medical device, a network home appliance, an automobile (connected car), a personal computer (laptop PC), a mobile phone, a smartphone, a tablet terminal, a game console, a personal digital assistant (PDA), a digital camera, a wearable PC, a desktop PC, or the like.

[0319] For example, aspects of the present invention are as follows. <1> A transaction management system including a transaction management device, a document management device, and a terminal device, the transaction management device, the document management device, and the terminal device being 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 form information written on the form; an output unit that, when an operation to complete a task using the form information is received on the task screen, 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 portion of the form information received from the transaction management device and the form image data in a document management memory unit. <2> A transaction management system as described in Appendix 1, wherein at least a portion of the report information includes predetermined specific item names and their item values. <3> A transaction management system as described in Appendix 1, wherein at least a portion of the document information includes the issuer of the document, the date of issue of the document, the total amount handled in the transaction indicated by the document, and identification information for identifying the document. <4> The storage control unit A transaction management system described in any one of Appendices 1 to 3, which stores document management information in the document management memory unit, the document management information correlating at least a portion of the report information with historical information indicating the history of how the report has been handled, and including identification information for identifying the document management information. <5> The document management device a display control unit that displays a screen on the terminal device that allows the user to confirm at least a part of the form information and the form image data; The display control unit A transaction management system described in any one of Appendices 1 to 4, wherein the screen is displayed on the terminal device in a state in which editing of at least a portion of the report information is prohibited. <6> The document management device After the document management information is stored in the document management storage unit, identification information for identifying the document management information is transmitted to the transaction management device; The transaction management device A transaction management system as described in Appendix 4, having an information management unit that stores identification information for identifying the document management information and transaction management information that corresponds to the report information in a transaction management memory unit. <7> The transaction management information includes a value indicating a progress status of the work for the transaction management information, The information management unit In the terminal device, an operation to instruct cancellation of the transaction management information is accepted, and a value indicating the progress status of the work included in the transaction management information is set to a canceled status; The output unit A transaction management system as described in Appendix 6, which outputs a cancellation request for document management information corresponding to the transaction management information to the document management device. <8> The information management unit In the terminal device, an operation for canceling the state in which the contents of the transaction management information have been confirmed is accepted, and a value indicating the progress state of the work included in the transaction management information is set to a draft saved state; The output unit A transaction management system as described in Appendix 7, which, when it receives an operation to re-confirm the contents of the transaction management information, outputs to the document management device a request to overwrite the document management information corresponding to the transaction management information. <9> The transaction management information includes information indicating the version number of the form, The information management unit Accepting input of form image data of a new version of a form, and storing in the transaction management storage unit transaction management information associated with form information of the old version of a form and form information extracted from the form image data of the new version; The output unit A transaction management system as described in Appendix 7 or 8, which outputs to the document management device a request to cancel document management information corresponding to transaction management information including report information of the old version of the report, report image data of the new version of the report, and at least a portion of the report information extracted from the report image data of the new version. <10> The work screen is A transaction management system described in any one of appendices 1 to 9, including the form image data and form information of another form identified by identification information that identifies the form. <11> A transaction management system as described in Appendix 10, wherein the document is an invoice and the other document is an order form. <12> The work screen is A transaction management system described in any one of appendices 1 to 9, including the form image data and form management information for managing the form. <13> A transaction management system as described in Appendix 12, wherein the document management information is journal entry information or payment information. <14> A transaction management method using 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 displaying on the terminal device a work screen for performing work using the form information written on the form; When an operation to complete a task using the form information is accepted on the task 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 in which at least a portion of the form information received from the transaction management device and the form image data are stored in a document management storage unit. <15> a display control unit that displays on the terminal device a work screen for performing work using the form information written on the form; A transaction management device having an output unit that outputs at least a portion of the report information and report image data, which is an image of the report, to a document management device when an operation to complete work using the report information is received on the work screen. <16> displaying on the terminal device a work screen for performing work using the form information written on the form; A transaction management program that causes a computer to execute a process in which, when an operation to complete a task using the document information is received on the work screen, at least a portion of the document information and document image data, which is an image of the document, are output to a document management device.

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

[0321] 100 Transaction Management System 200 Transaction Management Device 240 Transaction Management Database 250 Transaction Management Department 251 Input Reception Unit 252 Document Recognition Unit 253 Information Management Department 254 Display control unit 255 output section 300 Document management device 340 Document Management Database 350 Document Management Department 400 Terminal Equipment [Prior art documents] [Patent documents]

[0322] [Patent Document 1] Japanese Patent Application Publication No. 2019-095849 [Patent Document 2] Japanese Patent Publication No. 2020-021461

Claims

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 form information written on a form; an output unit that, when an operation to complete a task using the form information is received on the task screen, 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 portion of the form information received from the transaction management device and the form image data in a document management memory unit.

2. 2. The transaction management system according to claim 1, wherein at least a portion of the form information includes predetermined specific item names and their item values.

3. A transaction management system as described in claim 1, wherein at least a portion of the document information includes the issuer of the document, the date of issue of the document, the total amount handled in the transaction indicated by the document, and identification information for identifying the document.

4. The storage control unit A transaction management system as described in claim 1, wherein the document management memory unit stores document management information that corresponds at least a portion of the report information with historical information indicating the history of how the report has been handled, and the document management information includes identification information for identifying the document management information.

5. The document management device a display control unit that displays a screen on the terminal device that allows the user to confirm at least a part of the form information and the form image data; The display control unit 2. The transaction management system according to claim 1, wherein said screen is displayed on said terminal device in a state in which editing of at least a part of said form information is prohibited.

6. The document management device After the document management information is stored in the document management storage unit, identification information for identifying the document management information is transmitted to the transaction management device; The transaction management device 5. A transaction management system according to claim 4, further comprising an information management unit that stores transaction management information in a transaction management storage unit, the transaction management information correlating identification information for identifying the document management information with the form information.

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

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

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

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

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

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

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

14. A transaction management method using 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 displaying on the terminal device a work screen for performing work using the form information written on the form; When an operation to complete a task using the form information is accepted on the task 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 in which at least a portion of the form information received from the transaction management device and the form image data are stored in a document management storage unit.

15. a display control unit that displays on the terminal device a work screen for performing work using the form information written on the form; A transaction management device having an output unit that outputs at least a portion of the report information and report image data, which is an image of the report, to a document management device when an operation to complete work using the report information is received on the work screen.

16. displaying on the terminal device a work screen for performing work using the form information written on the form; A transaction management program that causes a computer to execute a process in which, when an operation to complete a task using the document information is received on the work screen, at least a portion of the document information and document image data, which is an image of the document, are output to a document management device.

Images