JP7786166B2 - Information processing device, information processing method, program, and information processing system - Google Patents

Description

The present invention relates to an information processing device, an information processing method, a program, and an information processing system.

Conventionally, when matching two documents, a technique is known that matches documents with similar visual layouts.

For example, when matching two documents, such as an invoice and a purchase order, it is necessary to match the two documents based on information that identifies the two documents. Traditionally, this matching has been done visually by the person in charge of the matching work or using existing software functions, making the matching work cumbersome.

The disclosed technology aims to make it easier to match documents with each other.

The disclosed technology is an information processing device that has a display control unit that displays on a terminal device a reception screen that accepts input of information that identifies first report information to be associated with second report information from among the first report information stored in a memory unit, and a matching unit that matches the first report information identified based on the identifying information with the second report information, wherein the reception screen is a screen that accepts input of search conditions for the first report information to be associated with the second report information, and includes an area that displays the second report information and an area that accepts input of the search conditions, and the matching unit matches the first report information identified based on the results of searching the memory unit with the search conditions with the second report information .

Reports can now be matched more easily.

A figure showing an example of the system configuration of a transaction management system of the first embodiment. FIG. 2 illustrates an example of a hardware configuration of a transaction management device. FIG. 2 illustrates an example of a hardware configuration of a terminal device. FIG. 10 is a diagram illustrating an example of an order destination management database. FIG. 10 is a diagram illustrating an example of an order form management database. FIG. 10 is a diagram illustrating an example of an invoice management database. FIG. 10 is a diagram illustrating an example of a matching management database. FIG. 2 is a diagram explaining the functions of each device included in the transaction management system. This is a first sequence diagram explaining the operation of the transaction management system. 10 is a first flowchart illustrating the processing of the transaction management device. FIG. 10 is a diagram illustrating an example of a confirmation screen for order form information. 10 is a second flowchart illustrating the processing of the transaction management device. FIG. 10 is a diagram showing an example of a confirmation screen for invoice information. This is a second sequence diagram explaining the operation of the transaction management system. FIG. 10 is a first diagram showing an example of a display on a buyer terminal. FIG. 10 is a second diagram showing an example of a display on the buyer terminal. FIG. 10 is a third diagram showing an example of a display on a buyer terminal. FIG. 4 is a fourth diagram showing an example of a display on a buyer terminal. FIG. 5 is a fifth diagram showing an example of a display on a buyer terminal. FIG. 6 is a sixth diagram showing an example of a display on a buyer terminal. FIG. 10 is a diagram illustrating another example of the system configuration of a transaction management system.

Embodiments will be described below with reference to the drawings. Figure 1 shows an example of the system configuration of a transaction management system.

The transaction management system 100 of this embodiment includes a transaction management device 200 and a terminal device 300. The transaction management device 200 and the terminal device 300 can communicate via a network. Furthermore, the transaction management device 200 of this embodiment communicates with the terminal device 400 via a network.

The transaction management device 200 of this embodiment stores the form information contained in the form created by the terminal device 300. Furthermore, when the transaction management device 200 receives input of form information for a form issued for this form, it associates and manages the stored form information with the input form information.

In the following description, the form information input from the terminal device 300 will be referred to as first form information, a form including the first form information will be referred to as the first form, and form image data including the first form information will be referred to as first form image data.

In the following description, the form issued in correspondence with the first form will be referred to as the second form, the form image data showing the second form will be referred to as the second form image data, and the form information contained in the second form will be referred to as the second form information.

When second accounting form information is input from the terminal device 300, the transaction management device 200 of this embodiment displays a screen on the terminal device 300 that allows the user to select first accounting form information that corresponds to the second accounting form information from among the first accounting form information already stored. Then, when first accounting form information is selected on the terminal device 300, the transaction management device 200 associates the selected first accounting form information with the second accounting form information and performs a matching process between the two.

In this way, in this embodiment, the input of second form information is accepted, and a screen is displayed for selecting first form information that corresponds to the second form information, thereby assuring that the first form and the second form are matched. As a result, in this embodiment, tasks such as visually checking the form information of the two forms are not required, and the forms can be easily matched. Furthermore, because this embodiment makes it easy to match forms, the workload of reconciliation work can be reduced.

The terminal device 300 in this embodiment is a terminal device that is primarily used by order sources that place orders via the transaction management device 200. In other words, the terminal device 300 is a terminal device that is used by buyers who purchase products, etc. In the following description, the terminal device 300 may be referred to as the buyer terminal 300.

In this embodiment, an order source is, for example, a business that places an order with various ordering destinations. In this embodiment, a business may be an individual, or an organization such as a company or corporation. In the following description of the embodiment, a business may be referred to as a tenant.

The terminal device 400 in this embodiment is a device external to the transaction management system 100 and is a terminal device that is primarily used by sellers of products, etc. In other words, the terminal device 400 is a terminal device that is used by sellers who sell products, etc. In the following description, the terminal device 400 may be referred to as a seller terminal 400.

In this embodiment, the first form is, for example, a product order form. In this case, the first form information is order form information indicating the contents of the order. Furthermore, if the first form is an order form, the second form corresponding to the first form is an invoice corresponding to this order form. In this case, the second form information is invoice information indicating the contents of the bill, and the second form image data is invoice image data. Furthermore, for example, the first form may be an order form and the second form may be a delivery note, or the first form may be an estimate and the second form may be an order form.

In the following explanation, an order form will be used as an example of the first form, and an invoice will be used as an example of the second form.

Furthermore, the terminal device 300 in this embodiment is a terminal device that is primarily used by an order source that places an order via the transaction management device 200. In other words, the terminal device 300 is a terminal device that is used by a buyer who purchases goods, etc. In the following description, the terminal device 300 may be referred to as a buyer terminal 300.

In this embodiment, an order source is, for example, a business that places an order with various ordering destinations. In this embodiment, a business may be an individual, or an organization such as a company, corporation, or group. In the following description of the embodiment, a business may be referred to as a tenant.

The terminal device 400 in this embodiment is a device external to the transaction management system 100 and is a terminal device that is primarily used by sellers of products, etc. In other words, the terminal device 400 is a terminal device that is used by sellers who sell products, etc. In the following description, the terminal device 400 may be referred to as a seller terminal 400.

The transaction management device 200 of this embodiment has an order destination management database 210, an order form management database 220, an invoice management database 230, a matching management database 240, and a transaction management unit 260.

The order destination management database 210 stores order destination information related to order destinations. In other words, the order destination management database 210 stores information related to sellers. The order form management database 220 stores order form management information.

The order form management information in this embodiment is information for managing order form information and includes order form information. The order form information in this embodiment may be extracted by form recognition processing of order form image data created on the buyer terminal 300.

The document recognition process may be performed by the transaction management device 200. Furthermore, the order form information may be obtained as a result of performing OCR (Optical Character Recognition) on the order form, for example, by an image forming device capable of communicating with the transaction management device 200.

The invoice management database 230 stores invoice management information.

Invoice management information in this embodiment is information for managing invoice information and includes invoice information. Invoice information in this embodiment is information extracted from an invoice received by a buyer from a seller, and an invoice in this embodiment is issued by a seller in response to a purchase order issued by the buyer and given to the buyer.

The invoice information may be obtained by performing document recognition processing on the invoice image data in the transaction management device 200. The invoice information may also be obtained as a result of OCR processing performed by an image forming device, etc.

The matching management database 240 stores information such as the results of matching purchase order information with invoice information.

When the transaction management unit 260 matches the invoice information of an invoice received by a buyer with the order form information of an order form issued by the buyer, it displays a screen on the buyer terminal 300 for associating the invoice information with the order form information. In other words, the transaction management unit 260 associates the invoice management information with the order form management information.

Specifically, when the transaction management unit 260 receives an instruction from the buyer terminal 300 to match invoice information with purchase order information, it causes the buyer terminal 300 to display a screen for selecting the purchase order information corresponding to the invoice information to be matched.

In this embodiment, by displaying such a screen, invoice information and order form information can be associated within the transaction management system 100, even if, for example, both or either of the invoice and order form are in paper form. In other words, according to this embodiment, forms can be easily associated with each other. Furthermore, since this embodiment makes it easy to associate related forms with each other, the burden of reconciliation work is also reduced.

The matching process involves comparing the contents of an order with the contents of the corresponding order to confirm whether they match.

In the example of FIG. 1, the order destination management database 210, purchase order management database 220, invoice management database 230, and matching management database 240 are provided in the transaction management device 200, but this is not limited to this. Some or all of these databases may be provided in other devices. Furthermore, the transaction management device 200 may be realized by multiple information processing devices.

Next, we will explain the hardware configuration of the transaction management device 200 of this embodiment.

Figure 2 shows an example of the hardware configuration of a transaction management device. The transaction management device 200 is constructed using a computer, and as shown in Figure 2, includes a CPU 201, ROM 202, RAM 203, HDD 204, HDD (Hard Disk Drive) controller 205, display 206, external device connection I/F (Interface) 208, network I/F 209, bus line B1, keyboard 211, pointing device 212, DVD-RW (Digital Versatile Disk Rewritable) drive 214, and media I/F 216.

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 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 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 B1 is an address bus, data bus, etc. for electrically connecting the various components, such as the CPU 201, shown in FIG. 2.

The keyboard 211 is a type of input device equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input device for selecting and executing various instructions, selecting processing targets, moving the cursor, etc. The DVD-RW drive 214 controls the reading and writing of various data from 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 or the like. The media I/F 216 controls the reading and writing (storing) of data from a recording medium 215, such as a flash memory.

Next, the hardware configuration of the buyer terminal 300 of this embodiment will be described with reference to Figure 3. Figure 3 is a diagram showing an example of the hardware configuration of a terminal device. The terminal device 300 of this embodiment includes a CPU 301, ROM 302, RAM 303, EEPROM 304, CMOS sensor 305, image sensor I/F 306, acceleration/direction sensor 307, media I/F 309, and GPS receiver 311.

Of these, CPU 301 is an arithmetic processing unit that controls the overall operation of terminal device 300. ROM 302 stores CPU 301 and programs used to drive CPU 301, such as IPL. RAM 303 is used as a work area for CPU 301. EEPROM 304 reads and writes various data, such as smartphone programs, under the control of CPU 301. ROM 302, RAM 303, and EEPROM 304 are examples of storage devices for terminal device 300.

The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging device that captures an image of a subject (mainly a self-portrait) under the control of the CPU 301 to obtain image data. Note that instead of a CMOS sensor, an imaging device such as a CCD (Charge Coupled Device) sensor may also be used.

The imaging element I/F 306 is a circuit that controls the operation of the CMOS sensor 305. The acceleration/azimuth sensor 307 is a variety of sensors, such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I/F 309 controls the reading and writing (storage) of data from the recording media 308, such as flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

The terminal device 300 also includes a long-distance communication circuit 312, an antenna 312a for the long-distance communication circuit 312, a CMOS sensor 313, an image sensor I/F 314, a microphone 315, a speaker 316, an audio input/output I/F 317, a display (display device) 318, an external device connection I/F (Interface) 319, a short-distance communication circuit 320, an antenna 320a for the short-distance communication circuit 320, and a touch panel 321.

Of these, the long-distance communication circuit 312 is a circuit that communicates with other devices via a communication network. The CMOS sensor 313 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 301. The image sensor I/F 314 is a circuit that controls the operation of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 317 is a circuit that processes the input and output of sound signals between the microphone 315 and speaker 316 under the control of the CPU 301.

The display 318 is a type of display means, such as an LCD or organic EL (Electro Luminescence) display, that displays an image of a subject, various icons, etc. The external device connection I/F 319 is an interface for connecting various external devices. The short-range communication circuit 320 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a type of input means that allows a user to operate the terminal device 300 by pressing the display 318. The display 318 is an example of a display unit that the terminal device 300 has. The user is, for example, an individual, or in the case of a tenant, an employee of the business.

Note that the terminal device 300 of this embodiment may be, for example, an information processing device having the same functional configuration as the transaction management device 200.

Next, we will explain each database of the transaction management device 200 with reference to Figures 4 to 8. Figure 4 shows an example of an order destination management database.

In this embodiment, the order destination management database 210 is provided, for example, for each tenant. Furthermore, the order destination management database 210 in this embodiment includes information items such as name, address, telephone number, email address, and contact person name, and these items are associated with a tenant ID (tenant identification information) and tenant name.

In this embodiment, information in the order destination management database 210 that includes values for items such as name, address, telephone number, email address, and person in charge may be referred to as order destination information. The tenant ID and tenant name are information for identifying a tenant. The value of the "Name" item indicates the name of the business partner (billing destination), and the values of the "Address," "Telephone Number," "Email Address," and "Person in Charge" items indicate the billing destination's address, telephone number, email address, and name of the person in charge of the transaction, respectively.

Note that the information items included in the order destination information are not limited to the example shown in Figure 4. The information items included in the order destination information do not have to include all of the items shown in Figure 4, and may include items other than those shown in Figure 4.

In this embodiment, the order destination information is stored in the order destination management database 210 when the transaction management device 200 accepts input from the buyer terminal 300.

Figure 5 shows an example of an order form management database. In this embodiment, the order form management database 220 may be provided for each tenant, similar to the order destination management database 210.

The order form management database 220 contains information items such as purchase order number, corresponding invoice number, confirmation status, form status, order recipient, total amount, order date, information status, form image path, and statement information, and each item is associated with a tenant name. In this embodiment, a tenant ID for identifying the tenant may be used instead of the tenant name.

In addition, the order form management database 220 associates the item "order form number" with other items. In this embodiment, information in the order form management database 220 that includes the value of the item "order form number" and the values of other items is referred to as order form management information.

In addition, in the purchase order management information, items such as "Corresponding invoice number," "Confirmation status," "Report status," and "Information status" are information items for managing purchase order information and do not necessarily need to be included in the purchase order information.

The value of the "Order Form Number" item is form identification information used to identify the order form, order form information, and order form management information. In other words, the value of the "Order Form Number" item is identification information used to identify the first form information.

The value of the "Corresponding Invoice Number" item is identification information for identifying an invoice that contains invoice information that corresponds to the purchase order information identified by the purchase order number. In other words, the value of the "Corresponding Invoice Number" item is document identification information for identifying a document (invoice). In other words, the value of the "Corresponding Invoice Number" item is identification information for identifying second document information.

In this embodiment, if a value for the "Corresponding Invoice Information" item is stored in the purchase order management database 220, this indicates that the correspondence between purchase order information and invoice information has been completed.

The value of the "Confirmation Status" item indicates the progress of the matching process for the corresponding purchase order information. Specifically, for example, if the value of the "Confirmation Status" item is "Confirmed," this indicates that the buyer has completed the visual matching process. Also, for example, if the value of the "Confirmation Status" item is "Confirmation Required," this indicates that the buyer has not yet performed the visual matching process. If the value of the "Confirmation Status" item is "Unbilled," this indicates that the purchase order information and invoice information have not been matched, and in this case the value of the "Corresponding Invoice Information" item will be empty. Also, if the value of the "Confirmation Status" item is "Success," this indicates that the matching process by the transaction management device 200 was successful.

The value of the "Orderer" field indicates the name of the order recipient for the order form identified by the order form number. In the example in Figure 5, the order recipient is "XX Co., Ltd." Therefore, it can be seen that the order form identified by order form number "190186" was issued by tenant name "XX Co., Ltd." to XX Co., Ltd.

The values in the "Total Amount" and "Order Date" fields indicate the total amount and order date listed on the order form.

The value of the "Report Status" item indicates the progress of the recognition of the report. In this embodiment, the "Report Status" item has four values: unprocessed, saved as draft, confirmed, and externally output. The states are as follows:

- Unprocessed state (state 1): This is the state immediately after document information (order form information, invoice information) has been obtained, and the contents of the document information have not yet been confirmed.

- Draft saved state (state 2) This is the state when work such as checking report information is in progress and the report management information (order form management information, invoice management information) has not yet been finalized.

Confirmed state (state 3): The state in which tasks such as confirmation of the report information have been completed, and the report management information (order form management information, invoice management information) has been stored in the report management database (order form management database 220, invoice management database 230) as confirmed information.
External output completed state (state 4) A state in which the output of report information to an accounting system or the like linked to the transaction management system 100 has been completed.

The value of the "Information Status" item indicates the status of the accounting information (order form information, invoice information) in the transaction management system 100. Specifically, the status of accounting information includes the following four states:

- Unprocessed state (state 1): This is the state immediately after document information (order form information, invoice information) has been obtained, and the contents of the document information have not yet been confirmed.

- Draft saved state (state 2) This is the state when work such as checking report information is in progress and the contents of the report information (order form information, invoice information) have not yet been finalized.

- Confirmed state (state 3): The state in which tasks such as checking the report information have been completed and the report information (order form information, invoice information) has been confirmed.

In this embodiment, the status indicating the progress of document recognition (order form, invoice) and the status of confirmation of document information (order form information, invoice information) are managed separately. Therefore, in this embodiment, for example, after a buyer receives an invoice corresponding to a purchase order, only the invoice information can be confirmed first before processing such as journalizing the invoice, and the confirmed invoice information can be reconciled with the order form information.

The value of the "Report Image Path" field indicates the storage location of the order form image data.

The "Details Information" item may be associated with items that indicate the breakdown of the order amount, such as "Product Code," "Product Name," and "Quantity."

Note that the information items included in the purchase order management information are not limited to the example shown in Figure 5. The information items included in the purchase order management information do not have to include all of the items shown in Figure 5, and may include items other than those shown in Figure 5.

Figure 6 is a diagram showing an example of an invoice management database. In this embodiment, the invoice management database 230 may be provided for each tenant, similar to the order destination management database 210. In this embodiment, the invoice management database 230 includes information items such as billing source, invoice number, corresponding purchase order number, total amount, issue date, form status, information status, form image path, transfer destination, and statement information. Each of these items is associated with a tenant name. In addition, the items "billing destination" and "invoice number" are associated with other items.

In the following explanation, information including the items "billing source" and "invoice number" in the invoice management database 230, as well as values for other items, will be referred to as invoice management information.

In addition, in the invoice management information, items such as "Corresponding order number," "Confirmation status," "Report status," and "Information status" are information items for managing invoice information and do not necessarily need to be included in the invoice information.

The value of the "Biller" field indicates the name of the tenant that made the bill. In other words, the value of the "Biller" field indicates the name of the tenant that created the invoice information.

The value of the "Invoice Number" item is identification information for identifying the invoice, invoice information, and invoice management information. In other words, the value of the "Invoice Number" item is identification information for identifying the second report information.

The value of the "Corresponding Purchase Order Number" item is identification information for identifying the purchase order that contains the purchase order information that corresponds to the invoice information identified by the invoice number. In other words, the value of the "Corresponding Purchase Order Number" item is identification information for identifying the first form information.

In this embodiment, if a value for the "Corresponding Purchase Order Information" item is stored in the invoice management database 230, this indicates that the invoice information and purchase order information have been associated.

The value of the "Confirmation Status" field will be "Confirmation Required" if the buyer has not yet confirmed the matching results from the matching process after receiving the invoice information. The value of the "Status" field will be "Confirmed" if the buyer has confirmed the matching results.

The value of the "Total Amount" field indicates the total invoice amount. The value of the "Issue Date" field indicates the date the invoice identified by the invoice number was issued.

The value of the "Form Image Path" item indicates the storage location of the order form image data. The "Details Information" item corresponds to items that indicate the breakdown of the total amount, such as "Product Code," "Product Name," and "Quantity."

Note that the information items included in the invoice information are not limited to the example shown in Figure 6. The information items included in the invoice information do not have to include all of the items shown in Figure 6, and may include items other than those shown in Figure 6.

Next, the matching management database 240 of this embodiment will be described with reference to Figure 7. Figure 7 is a diagram showing an example of the matching management database. The matching management database 240 of this embodiment may be provided for each tenant.

The matching management database 240 contains information items such as purchase order number, processing date and time, total amount, and detailed information, with the "purchase order number" item corresponding to other items.

The value in the "Processing Date and Time" field indicates the date and time the matching process was performed. The value in the "Total Amount" field indicates the result of matching the total amount included in the purchase order information identified by the purchase order number with the total amount included in the invoice information corresponding to this purchase order information.

The "Details" item corresponds to items that indicate the breakdown of the total amount, such as "Product Code," "Product Name," and "Quantity." In the matching management database 240, the values of these items indicate the results of matching the details contained in the invoice information and the order form information for which the product name matches.

In the example of Figure 7, the result of comparing the total amount is "confirmation required," and the result of comparing the detailed information 1 included in the invoice information and the order form information is that the unit price is "confirmation required."

In addition, in this embodiment, if the matching results are a match, it may be expressed as "success," and if the matching results are a mismatch, it may be expressed as "confirmation required."

Note that the information items contained in the matching management database 240 are not limited to the example shown in FIG. 7. The information items contained in the matching management database 240 do not have to include all of the items shown in FIG. 7, and may include items other than those shown in FIG. 7.

Next, with reference to Figure 8, the functions of each device included in the transaction management system 100 of this embodiment will be explained. Figure 8 is a diagram explaining the functions of each device included in the transaction management system.

First, we will explain the functions of the transaction management device 200. In this embodiment, the transaction management unit 260 of the transaction management device 200 has a transmission unit 261, a reception unit 262, an input acceptance unit 263, a document recognition unit 264, a display control unit 265, a storage control unit 266, a correspondence unit 267, a matching unit 268, and an output unit 269.

The transmitting unit 261 and receiving unit 262 transmit and receive information between the transaction management device 200 and other devices. The input accepting unit 263 accepts various inputs to the transaction management device 200. Specifically, the input accepting unit 263 accepts various information inputs and requests from the buyer terminal 300. Examples of various information include form image data (invoice image data, order form image data), form information (invoice information, order form information), etc.

The form recognition unit 264 extracts form information from the form image data. Specifically, the form recognition unit 264 performs character recognition processing on the form image data to obtain text data, extracts items and item values contained in the form image from the obtained text data, and uses the information associating the items with their values as form information. In the following explanation, extracting items and their values contained in the form image, converting them into text data, and associating them is referred to as form recognition.

In this embodiment, when the input acceptance unit 263 accepts input of invoice image data, the form recognition unit 264 acquires invoice information from the invoice image data. In addition, in this embodiment, when the input acceptance unit 263 accepts input of order form image data, the form recognition unit 264 acquires order form information from the order form image data.

The display control unit 265 controls the display on the buyer terminal 300. The display control unit 265 may also control the display on the seller terminal 400. The storage control unit 266 updates each database in accordance with the processing of the transaction management unit 260.

The association unit 267 associates the order form information with the invoice information. Specifically, when the association unit 267 receives an instruction to match the invoice information with the order form information, it determines whether the invoice information and the order form information are associated. If the invoice information is not associated with the order form information, the association unit 267 causes the display control unit 265 to display on the buyer terminal 300 a screen for selecting the order form information to associate with the invoice information.

When purchase order information is selected on this screen, the association unit 267 associates the selected purchase order information with the invoice information. Specifically, the association unit 267 causes the storage control unit 266 to update the value of the corresponding invoice number in the purchase order management database 220 and update the value of the corresponding purchase order number in the invoice management database 230.

The matching unit 268 performs matching processing between associated invoice information and order form information, and causes the storage control unit 266 to update the matching management database 240. The output unit 269 outputs various information from the transaction management device 200.

Next, the functions of the buyer terminal 300 will be described. In this embodiment, the buyer terminal 300 has a display unit 330 and a communication unit 340. The display unit 330 displays information on the display of the buyer terminal 300. The communication unit 340 sends and receives information between the buyer terminal 300 and other devices.

Next, the operation of the transaction management system 100 of this embodiment will be described with reference to Figure 9.

9 is a first sequence diagram illustrating the operation of the transaction management system, showing steps S901 to S908 of the transaction management system 100, from when the order information of a purchase order issued by a buyer is stored in the order management database 220.
FIG. 9 also shows steps S909 to S917 of the operation of transaction management system 100 until invoice information of an invoice received by a buyer from a seller is stored in invoice management database 230.

Note that the operation of storing the order form information in the order form management database 220 and the operation of storing the invoice information in the invoice management database 230 may be performed at independent times.

In the transaction management system 100 of this embodiment, when the buyer terminal 300 receives an operation from a tenant instructing the registration of purchase order information (step S901), it sends a request to register the purchase order information to the transaction management device 200 (step S902).

The request to register purchase order information may be sent to the transaction management device 200, for example, along with purchase order image data entered into the buyer terminal 300, or may be a CSV file that associates item names and item values written on a paper purchase order.

When the transaction management device 200 receives a request to register order form information via the input reception unit 263, it acquires the order form information and stores the acquired order form information in the order form management database 220 via the storage control unit 266 (step S903). Details of step S903 will be described later.

Next, the transaction management device 200, via the display control unit 265, sends an instruction to the buyer terminal 300 to display a confirmation screen for confirming the order form information (step S904).

The buyer terminal 300 accepts the instruction to display the confirmation screen and causes the display unit 330 to display the confirmation screen for the purchase order information (step S905).

Next, when the buyer terminal 300 receives an instruction from the tenant to confirm the purchase order information (step S906), it sends a request to confirm the purchase order information to the transaction management device 200 (step S907).

In response to this request, the transaction management device 200 causes the storage control unit 266 to confirm the status of the order form information stored in the order form management database 220 in step S903 (step S908). Specifically, the storage control unit 266 sets the values of the items "Report Status" and "Information Status" to "Confirmed" in the order form management information, including the order form information stored in the order form management database 220.

The above explains the operation for storing purchase order information in the purchase order management database 220. Next, we will explain the operation for storing invoice information in the invoice management database 230.

When the buyer tenant receives an invoice from the seller (step S909) and the buyer terminal 300 accepts an operation from the buyer tenant instructing the registration of invoice information (step S910), the buyer terminal 300 sends a request to register the invoice information to the transaction management device 200 (step S911).

When the transaction management device 200 receives a request to register invoice information via the input reception unit 263, it acquires the invoice information and stores the acquired invoice information in the invoice management database 230 via the storage control unit 266 (step S912). Details of step S912 will be described later.

Next, the transaction management device 200, via the display control unit 265, sends an instruction to the buyer terminal 300 to display a confirmation screen for confirming the invoice information (step S913).

The buyer terminal 300 accepts the instruction to display the confirmation screen and causes the display unit 330 to display the invoice information confirmation screen (step S914).

Next, when the buyer terminal 300 receives an instruction from the tenant to confirm the invoice information (step S915), it sends a request to confirm the invoice information to the transaction management device 200 (step S916).

In response to this request, the transaction management device 200 causes the storage control unit 266 to confirm the status of the invoice information stored in the invoice management database 230 in step S912 (step S917). Specifically, the storage control unit 266 sets the value of the item "information status" in the invoice management information including the invoice information stored in the invoice management database 230 to "confirmed."
In this embodiment, before journalizing the invoice, only the invoice information is confirmed, and the confirmed invoice information can be matched with the purchase order information. Also, in this embodiment, the "document status" item of the invoice management information may be confirmed after journalizing the invoice information is completed.

The above is the operation for storing invoice information in the invoice management database 230. Next, we will explain the processing of the storage control unit 266.

Figure 10 is a first flowchart explaining the processing of the transaction management device. Figure 10 shows details of the processing of the storage control unit 266, which stores purchase order information in the purchase order management database 220 in step S903 of Figure 9.

When the transaction management unit 260 of the transaction management device 200 of this embodiment receives a request to register order form information via the input reception unit 263 (step S1001), the storage control unit 266 determines whether the order form is in paper form (step S1002).

Specifically, the storage control unit 266 determines whether the information sent from the buyer terminal 300 along with the request to register the order form information is order form image data. If order form image data is sent from the buyer terminal 300, this indicates that a paper order form has been read by a reading device such as a scanner, and the order form can be said to be in paper form.

If the order form is not in paper form in step S1002, the transaction management unit 260 proceeds to step S1004, which will be described later. An order form not in paper form would be one in which the information sent from the buyer terminal 300 along with the order form information registration request is, for example, data in CSV format.

At this time, the order form information sent from the buyer terminal 300 may be order form information created using an application provided to the buyer terminal 300 by the transaction management device 200, or it may be order form information created using another application.

In step S1002, if the order form is on paper, the transaction management device 200 performs form recognition on the order form image data using the form recognition unit 264 and extracts order form information from the order form image data (step S1003).

Next, the transaction management device 200 causes the storage control unit 266 to store the order form information in the order form management database 220 (step S1004), and causes the display control unit 265 to generate screen data for displaying a confirmation screen for the order form information (step S1005), thereby terminating the process.

The order form information confirmation screen will be described below with reference to Figure 11. Figure 11 is a diagram showing an example of the order form information confirmation screen. Note that the example in Figure 11 may also be an example of an order form information confirmation screen when the order form is in paper form.

The screen 111 shown in Figure 11 includes display areas 112, 113, and 114, and operation buttons 26 and 27.

Display area 112 displays order form image data. Display area 113 displays order form information extracted by form recognition of the order form image data. In the example of Figure 11, the order form number, order recipient, total amount, detailed information, etc. are displayed. Also displayed in display area 113 is an operation button 116. Operation button 116 is an operation button for changing the information status of the order form information displayed in display area 113 to a confirmed state.

Display area 114 displays the value of the form status. Operation button 26 is an operation button for changing the status of the order form, whose image data and information are displayed on screen 111, to a draft saved status. Operation button 27 is an operation button for changing the status of the order form, whose image data and information are displayed on screen 111, to a confirmed status.

In this embodiment, for example, when making corrections to purchase order information extracted by form recognition, the buyer simply performs an operation on the buyer terminal 300 to change the value of the item to be corrected.

In this embodiment, the buyer is prompted to confirm the purchase order information in the manner described above.

Figure 12 is a second flowchart explaining the processing of the transaction management device. Figure 12 shows details of the processing of the storage control unit 266, which stores invoice information in the invoice management database 230 in step S912 of Figure 9.

When the transaction management unit 260 of the transaction management device 200 of this embodiment receives a request to register invoice information via the input reception unit 263 (step S1201), the storage control unit 266 determines whether the invoice is on paper (step S1202).

Specifically, the storage control unit 266 determines whether the information sent from the buyer terminal 300 along with the request to register invoice information is invoice image data. If invoice image data is sent from the buyer terminal 300, this indicates that a paper invoice has been read by a reading device such as a scanner, and the invoice can be said to be on paper.

If the invoice is not on paper in step S1202, the transaction management unit 260 proceeds to step S1204, which will be described later. An invoice is not on paper if, for example, the information sent from the buyer terminal 300 along with the request to register the invoice information is in CSV format.

In this case, the invoice information sent from the buyer terminal 300 may be invoice information created using an application provided by the transaction management device 200 to the seller terminal 400, and sent from the seller terminal 400 to the buyer terminal 300 via the transaction management device 200.

Furthermore, in this embodiment, if both the invoice information and the order form information corresponding to this invoice information are created using an application provided by the transaction management device 200, the order form information may be automatically associated with the invoice information when the invoice information is created.

The invoice information may also be invoice information created using another application.

In step S1202, if the invoice is on paper, the transaction management device 200 performs form recognition on the invoice image data using the document recognition unit 264 and extracts order form information from the invoice image data (step S1203).

Next, the transaction management device 200 uses the association unit 267 to determine whether there is purchase order information associated with the invoice information (step S1204). Specifically, the association unit 267 determines whether the invoice information was created using an application provided by the transaction management device 200 and whether a corresponding purchase order number has been assigned to the invoice information.

If no relevant order form information exists in step S1204, the transaction management device 200 proceeds to step S1206, which will be described later.

If corresponding order information is found in step S1204, the transaction management device 200 associates the invoice information with the order information using the association unit 267 (step S1205).

Specifically, the transaction management device 200 uses the association unit 267 to identify, from the order form information stored in the order form management database 220, order form information whose order form number value matches the corresponding order form number assigned to the invoice information. Then, the transaction management device 200 uses the storage control unit 266 to set the value of the "Corresponding Invoice Number" item in the order form management information containing the identified order form information to the invoice number included in the invoice information.

Next, the transaction management device 200 stores the invoice information in the invoice management database 230 via the storage control unit 266 (step S1206). At this time, if purchase order information corresponding to the invoice information exists, the value of the "Corresponding Purchase Order Number" item in the invoice management information containing the invoice information is set as the purchase order number of the corresponding purchase order information.

Next, the transaction management device 200 generates screen data for displaying a confirmation screen for the invoice information via the display control unit 265 (step S1207), and then ends the process.

Next, the invoice information confirmation screen of this embodiment will be described with reference to Figure 13. Figure 13 is a diagram showing an example of the invoice information confirmation screen. Note that the example in Figure 13 may also be an example of the invoice information confirmation screen when the invoice is in paper form.

The screen 131 shown in Figure 13 includes display areas 132 and 133 and operation buttons 28 and 29.

Invoice image data is displayed in display area 132.

Display area 133 has display areas 134, 135, 136, and 137, and display area 134 displays invoice information extracted by form recognition of invoice image data. In the example of Figure 13, the invoice number, billing party, invoice amount, detailed information, etc. are displayed. Also displayed in display area 134 is an operation button 140. Operation button 140 is an operation button for changing the information status of the invoice information displayed in display area 134 to a confirmed state.

In this embodiment, for example, when making corrections to invoice information extracted by form recognition, the buyer simply performs an operation on the buyer terminal 300 to change the value of the item to be corrected before operating the operation button 140.

Display area 135 displays fields for inputting journal information for invoices. In this embodiment, after the operation button 140 is operated to confirm the invoice information, journal information can be input.

Display area 136 displays the invoice's report status. In the example of Figure 13, display area 136 displays "Unprocessed," indicating that the invoice's status has not been determined.

Display area 137 displays the progress of the matching. In the example of Figure 13, display area 137 displays "Confirmation Required," indicating that the matching results have not yet been confirmed.

In addition, in this embodiment, tabs 138 and 139 are displayed in the display area 134. Tab 138 is a tab for displaying invoice information in the display area 134. Tab 139 is a tab for displaying purchase order information corresponding to the invoice information displayed in the display area 134, and the results of matching with the purchase order information.

In this embodiment, when the invoice information confirmation screen is displayed, tab 138 is displayed in the selected state.

In addition, in this embodiment, when tab 139 is selected on the invoice information screen 131, an instruction to match the invoice information whose invoice image data is displayed in the display area 132 with the order form information is accepted. Here, the invoice information whose invoice image data is displayed in the display area 132 is the invoice information selected as the target for matching.

Next, referring to Figure 14, we will explain how order form information and invoice information are matched in this embodiment.

Figure 14 is a second sequence diagram explaining the operation of the transaction management system. In the transaction management system 100 of this embodiment, the buyer terminal 300 accepts an operation to instruct matching by a tenant or the like (step S1401). Specifically, when the buyer terminal 300 accepts the selection of a tab on the invoice information confirmation screen to display the matching results with the purchase order information, it is deemed to have accepted the operation to instruct matching.

When the buyer terminal 300 receives this instruction, it sends a request to the transaction management device 200 to display the matching results (step S1402).

When the transaction management device 200 receives this display request via the input reception unit 263, the matching unit 267 determines whether there is purchase order information to be matched with the invoice information displayed on the confirmation screen (step S1403).

Specifically, the association unit 267 determines whether the invoice management database 230 contains a corresponding order form number value that corresponds to the invoice information displayed on the confirmation screen.

The following processing from step S1404 to step S1406 is performed when it is determined in step S1403 that purchase order information to be matched exists.

If it is determined in step S1403 that there is purchase order information to be matched, the transaction management device 200 uses the matching unit 268 to match the invoice information with the purchase order information (step S1404), and outputs information indicating the matching results and an instruction to display this information to the buyer terminal 300 using the output unit 269 (step S1405).

Note that matching refers to comparing the order details in the purchase order information with the billing details in the invoice information to confirm whether the order details and the order details match.

When the buyer terminal 300 receives the information indicating the matching results and the display instruction, it displays the matching results on the display unit 330 (step S1406).

The following processing from step S1407 to step S1423 is performed when it is determined in step S1403 that there is no purchase order information to match.

If it is determined in step S1403 that there is no purchase order information to be matched, the transaction management device 200, via the display control unit 265, sends an instruction to the buyer terminal 300 to display a search screen for purchase order information to be matched (step S1407).

In response to this display instruction, the buyer terminal 300 displays a search screen for purchase order information on the display unit 330 (step S1408). Next, when the tenant or other party inputs search conditions for purchase order information (step S1409), the buyer terminal 300 sends a search request to the transaction management device 200 (step S1410).

When the transaction management device 200 receives a search request, the matching unit 267 searches the order form management database 220 using the search criteria (step S1411).

At this time, the association unit 267 searches for order form information that matches the search criteria from the order form information in the order form management database 220 where the value of the "information status" item is set to "confirmed."

The following steps S1412 to S1415 show the processing performed when one piece of order information is extracted as a search result in the search in step S1411. In this embodiment, when one piece of order information is identified through the search, the transaction management device 200 uses the association unit 267 to associate the identified order information with invoice information (step S1412).

Specifically, the association unit 267 causes the storage control unit 266 to store the order number of the identified order information in the invoice management database 230 as the corresponding order number of the invoice information. Furthermore, the association unit 267 causes the storage control unit 266 to store the invoice number of the invoice information in the order management database 220 as the corresponding invoice number of the identified order information.

In this way, the search screen displayed in step S1408 is an example of a reception screen that accepts the selection of invoice information and corresponding order form information.

Next, the transaction management device 200 uses the matching unit 268 to match the invoice information with the identified purchase order information (step S1413) and transmits information indicating the matching results to the buyer terminal 300 (step S1414).

At this time, the transaction management device 200 also stores the matching results in the order form management database 220, invoice management database 230, and matching management database 240 via the storage control unit 266.

Specifically, the storage control unit 266 stores information indicating the results of matching on a document-by-document basis, i.e., an invoice and an order form, as the value of the "Verification Status" item in the order form management database 220 and the invoice management database 230. For example, if the matching between the documents is successful, the storage control unit 266 sets the value of the "Verification Status" item to "Success," and if the matching between the documents is unsuccessful, the storage control unit 266 sets the value of the "Verification Status" item to "Verification Required." Details regarding the success and failure of matching on a document-by-document basis will be provided later.

The storage control unit 266 also stores the matching results for each detail information unit contained in the invoice information and purchase order information in the matching management database 240. Details regarding the success and failure of matching for each detail information unit will be described later.

When the buyer terminal 300 receives information indicating the matching results, it displays this information (step S1415).

The following processing from step S1416 to step S1423 shows the processing when multiple pieces of purchase order information are extracted in the search in step S1411.

When multiple pieces of purchase order information are extracted in step S1411, the transaction management device 200 causes the display control unit 265 to send an instruction to display the search results to the buyer terminal 300 (step S1416).

When the buyer terminal 300 receives the instruction to display the search results, it causes the display unit 330 to display a selection screen for selecting purchase order information from the multiple purchase order information extracted as the search results (step S1417). In other words, the transaction management device 200 causes the buyer terminal 300 to display a reception screen for accepting the selection of purchase order information to be associated with invoice information.

Next, when the buyer terminal 300 receives an operation from a tenant or the like to select purchase order information (step S1418), the buyer terminal 300 notifies the transaction management device 200 of the selected purchase order information (step S1419).

When the transaction management device 200 receives a notification identifying purchase order information via the input receiving unit 263, the association unit 267 associates the identified purchase order information with invoice information (step S1420).

Next, the transaction management device 200 uses the matching unit 268 to match the invoice information with the selected order form information (step S1421).

Next, the transaction management device 200 transmits information indicating the matching results and an instruction to display this information to the buyer terminal 300 via the output unit 269 (step S1422).

When the buyer terminal 300 receives the information indicating the matching results and the display instruction, it displays the information indicating the matching results on the display unit 330 (step S1423).

In this way, in this embodiment, if the invoice information and purchase order information are not associated before receiving a matching instruction, a matching screen for associating the invoice information and purchase order information is displayed on the buyer terminal 300.

Furthermore, the only purchase order information displayed on the matching screen is that whose information status is confirmed. Therefore, in this embodiment, purchase order information that may be changed in the future can be prevented from being selected as a matching target. In other words, in this embodiment, it is possible to prevent unconfirmed form information from being selected as a matching target.

In the example of Figure 14, the operation to instruct reconciliation is performed from the invoice information confirmation screen that is displayed when the invoice information is stored in the invoice management database 230, but the timing at which the operation to instruct reconciliation is performed is not limited to this.

In this embodiment, for example, a list of received invoices may be displayed on the buyer terminal 300, and when an invoice is selected from the displayed list, a confirmation screen for the selected invoice information may be displayed. In this way, the buyer can compare the invoice information with the purchase order information at any time after receiving the invoice.

The following describes an example of the display on the buyer terminal 300. Figure 15 is the first diagram showing an example of the display on the buyer terminal. Screen 131A shown in Figure 15 is an example of a search screen displayed on the buyer terminal 300 in step S1408 of Figure 14.

The screen 131A shown in FIG. 15 includes display areas 132 and 133A and operation buttons 28 and 29. Invoice image data is displayed in the display area 132.

Display area 133A has display areas 134A, 135, 136, and 137, and display area 134A includes input fields 141 and 142, operation buttons 143, and a display area.

Input fields 141 and 142 are input fields for search conditions for order form information. Specifically, the order form number is input into input field 141, and the date and time the order form information was imported into the transaction management system 100 is input into input field 142. The import date and time is the date and time the information status of the order form information was set to confirmed.

For this reason, screen 131A in this embodiment can also be considered an example of a reception screen that accepts input of information to identify purchase order information that is associated with invoice information.

In the example of Figure 15, the search conditions are the purchase order number and the import date and time, but this is not limited to this. In this embodiment, the items to be entered as search conditions can be changed as desired by tenant operations.

Operation button 143 is an operation button for instructing a search using the search criteria entered in input fields 141 and 142. When search criteria are entered in input fields 141 and 142 and operation button 143 is operated, the buyer terminal 300 of this embodiment sends a search request to the transaction management device 200 and displays the search results.

Display area 144 is a display area for displaying the matching results. In the example of Figure 15, the purchase order information to be matched has not been specified, so display area 144 is blank.

Figure 16 is a second diagram showing an example of a display on the buyer terminal. Screen 131B shown in Figure 16 is an example of a screen displayed on buyer terminal 300 when, as a result of performing search conditions entered in input fields 141 and 142 on screen 131A, one piece of purchase order information corresponding to invoice information extracted from invoice image data displayed in display area 132 is identified.

Specifically, screen 131B shown in Figure 16 is an example of a screen displayed on the buyer terminal 300 in step S1415 of Figure 14.

Screen 131B shown in FIG. 16 includes display areas 132 and 133B and operation buttons 28 and 29. Tab 139 is selected on screen 131B.

Display area 133B has display areas 134B, 135, 136, and 137A, and display area 134B displays information showing the matching results.

Specifically, display area 134B displays the order form number and import date and time entered as search conditions in input fields 141 and 142.

Display area 134B also includes display area 144A. Display area 144A displays the detailed information of the order form information identified by the order form number entered in input field 141, as well as the results of matching each detailed information with the detailed information included in the invoice information.

In display area 144A, a notification that "Match successful" is displayed for all of the detailed information contained in the purchase order information, indicating that it matches the detailed information contained in the invoice information.

Here, we will explain the success and failure of matching detail information units.

In this embodiment, if there is exactly one item of detail information with a matching product name in both the invoice information and the order form information, and the quantity, unit price, and total amount all match, the matching result of the item of detail information for this product name is considered to be "success."

In addition, in this embodiment, if there is only one item of detail information with a matching product name in both the invoice information and the order form information, and the quantity, unit price, or total amount does not match, the result of the comparison of the item of detail information for this product name will be "confirmation required."

In this embodiment, if there is a plurality of itemized information with the same product name in each of the invoice information and the order form information, or if there is no itemized information with the same product name,
Regardless of the quantity, unit price, or total amount, the result of the matching of the detailed information for this product name will be "Confirmation Required."

Next, we will explain the success and failure of document-level matching.

In this embodiment, if the matching result for all of the detailed information is "success," the progress status of the matching between the forms displayed in display area 137A will be "success." Also, in this embodiment, if the matching result for all of the detailed information includes even one item that says "confirmation required," the progress status of the matching between the forms will also be "confirmation required."

In the example of Figure 16, the progress status of the matching between the forms displayed in display area 137A is "successful," which indicates that the invoice information displayed in display area 132, represented by the invoice image data, matches the order form information.

Figure 17 is a third diagram showing an example of a display on a buyer terminal. Screen 131C shown in Figure 17 is an example of a screen displayed on buyer terminal 300 when multiple pieces of purchase order information are extracted as a result of performing the search conditions entered in input fields 141 and 142 on screen 131A. Specifically, screen 131C shown in Figure 17 is an example of a selection screen for purchase order information displayed on buyer terminal 300 in step S1417 of Figure 14.

Screen 131C includes a display area 170. Display area 170 displays a list of order form information extracted as search results and operation buttons 171.

In this embodiment, when purchase order information is selected in the display area 170 and the operation button 171 is operated, the buyer terminal 300 notifies the transaction management device 200 of the selected purchase order information as the purchase order information to be matched.

Upon receiving the notification, the transaction management device 200 matches the selected purchase order information with the invoice information and performs a matching process.

If the match is successful, a screen with the same layout as the screen shown in Figure 16 will be displayed.

Figure 18 is a fourth diagram showing an example of a display on the buyer terminal. Screen 131D shown in Figure 18 is an example of a screen displayed on the buyer terminal 300 when, during a match performed after the invoice information and the order form information have been associated, the detailed information contained in the order form information does not match the detailed information contained in the invoice information. Therefore, screen 131D can be said to be an example of a screen displayed on the buyer terminal 300 in step S1423 of Figure 14.

Screen 131D shown in FIG. 18 includes display areas 132 and 133C and operation buttons 28 and 29. Also, tab 139 is selected on screen 131D.

Display area 133C has display areas 134C, 135, 136, and 137. Display area 134C also includes display areas 144B and 145.

Display area 145 displays the search criteria, which are the order form number and import date and time. Display area 145 also displays detailed information about the order form information for each product name.

Display area 144B displays the results of matching the detailed information in the invoice information with the detailed information in the order form information, for each detailed information item.

In this embodiment, for example, display area 144B may display detail information from the order form information that corresponds to product names that do not match the details in the invoice information.

In addition, display area 144B displays a "Confirmation Required" notification for each item of detailed information, indicating that the tenant must confirm the contents. Also, display area 144B displays a check box associated with each item of detailed information. This check box is checked when the tenant or other person confirms the matching results of the corresponding item of detailed information.

In this embodiment, the reconciliation is completed when the tenant has confirmed all of the detailed information displayed in display area 144B.

Figure 19 is a fifth diagram showing an example of a display on a buyer terminal. Screen 131E shown in Figure 19 is an example of a screen that is displayed after the tenant confirms the matching results displayed in display area 144B on screen 131D shown in Figure 18.

Screen 131E shown in FIG. 19 includes display areas 132 and 133D and operation buttons 28 and 29. Also, tab 139 is selected on screen 131E.

Display area 133D has display areas 134D, 135, 136, and 137B. Display area 134D also includes display areas 144C and 145.

In the example of Figure 19, in display area 144C, a check mark is entered in the check box associated with each item of detailed information, indicating that confirmation has been performed by the tenant.

In addition, in the example of Figure 19, the display area 137B displays "Confirmed," indicating that the confirmation of the detailed information matching results has been completed.

Figure 20 is a sixth diagram showing an example of a display on a buyer terminal. Screen 131F shown in Figure 20 shows an example of an invoice information confirmation screen for an invoice whose document status has been set to "confirmed" and whose matching with purchase order information has been completed.

Screen 131F shown in FIG. 20 includes display areas 132 and 133E and operation buttons 28 and 29. Furthermore, tab 138 is selected on screen 131F. Display area 133E includes display areas 134, 135, 136A, and 137A.

In the example of Figure 20, "Confirmed" is displayed in display area 136A, and "Success" is displayed in display area 137A.

Therefore, it can be seen that the invoice whose invoice image data is displayed in display area 132 has been confirmed and has been successfully matched with the corresponding purchase order.

In this way, in this embodiment, the report status and the progress of reconciliation are displayed, allowing tenants to easily understand the status of invoice information and purchase order information.

In addition, in this embodiment, if the invoice information and the purchase order information are not associated, a reception screen is displayed on the buyer terminal 300 to accept input of information identifying the purchase order information to be associated with the invoice information.

In addition, in this embodiment, if the order form or invoice is on paper media, form recognition is performed on the order form image data or invoice image data to obtain order form information and invoice information.

Therefore, in this embodiment, even if the order forms and invoices are on paper, there is no need for the person in charge of the matching work to visually check the correspondence, and it is possible to easily match invoice information with order form information.

In this embodiment, the transaction management device 200 has a document recognition unit 264 that realizes the document recognition function, but this is not limited to this. The document recognition unit 264 may also be provided external to the transaction management device 200. Another configuration of the transaction management system will be described below with reference to Figure 21.

Figure 21 is a diagram showing another example of the system configuration of a transaction management system. The transaction management system 100A shown in Figure 21 has a transaction management device 200A, a buyer terminal 300, and a document recognition device 500.

The transaction management device 200A has an order destination management database 210, an order form management database 220, an invoice management database 230, a matching management database 240, and a transaction management section 260A.

The transaction management unit 260A is similar to the transaction management unit 260 except that it does not have the document recognition unit 264. The document recognition device 500 does have the document recognition unit 264.

In the transaction management system 100A, for example, when the transaction management device 200A receives form image data from the buyer terminal 300, it may transmit this form image data to the form recognition device 500, which may then perform form recognition. The transaction management device 200A may then receive form information obtained by form recognition from the form recognition device 500.

In this embodiment, by performing document recognition on a device other than the transaction management device 200A, the processing load on the transaction management device 200A can be reduced.

Furthermore, each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" as used herein includes processors programmed to perform each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to perform each of the functions described above.

Furthermore, the devices described in the embodiments represent only one of several computing environments for implementing the embodiments disclosed herein.

In one embodiment, transaction manager 200 includes multiple computing devices, such as a server cluster, configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processing disclosed herein. Similarly, transaction manager 200 may include multiple computing devices configured to communicate with each other.

Furthermore, the transaction management device 200 can be configured to share the disclosed processing steps in various combinations. For example, the processes performed by the transaction management device 200 can be performed by other server devices. Similarly, the functions of the transaction management device 200 can be performed by other server devices. Furthermore, the server device and the elements of the other server devices may be combined into a single server device or separated into multiple devices.

The tables in the statement may also be generated through the learning effects of machine learning. Furthermore, by using machine learning to classify keywords and items that may be included in the transaction details, it is not necessary to use a correspondence table.

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

The present invention has been described above based on various embodiments, but the present invention is not limited to the requirements set forth in the above embodiments. These aspects can be modified without departing from the spirit of the present invention, and can be determined appropriately depending on the application form.

100, 100A Transaction management system 200, 200A Transaction management device 210 Order destination management database 220 Order form management database 230 Invoice management database 240 Matching management database 260 Transaction management unit 263 Input reception unit 264 Document recognition unit 265 Display control unit 266 Storage control unit 267 Correspondence unit 268 Matching unit 269 Output unit 300 Buyer terminal (terminal device)
400 Seller terminal (terminal device)

Japanese Patent Application Publication No. 11-232306

Claims (14)

a display control unit that displays, on the terminal device, a reception screen that receives input of information that identifies the first form information to be associated with the second form information from the first form information stored in the storage unit;
a correlation unit that correlates the first form information identified based on the identifying information with the second form information ,
The reception screen is
a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions;
The association unit
The information processing device associates the first form information identified based on the result of searching the storage unit using the search conditions with the second form information . The display control unit
When there are a plurality of pieces of the specified first form information, a selection screen including the plurality of pieces of the specified first form information is displayed on the terminal device;
The association unit
2. The information processing apparatus according to claim 1, wherein the first form information selected on the selection screen is associated with the second form information. a matching unit that matches first form information associated with the second form information with the second form information;
The information processing apparatus according to claim 1 or 2, wherein the display control unit causes the terminal device to display information indicating a result of the matching performed by the matching unit. The display control unit
4. The information processing apparatus according to claim 3, wherein information indicating the result of the matching is displayed on the terminal device together with the first form information and second form image data including the second form information. The association unit
When a request for registration of the second form information is received, it is determined whether or not first form information that can be associated with the second form information exists, and if it is determined that first form information exists, it associates the first form information with the second form information;
The display control unit
An information processing device as described in claim 3, which accepts a request to display information indicating the results of the matching by the matching unit, and displays the reception screen on the terminal device if there is no first report information corresponding to the second report information. The determination by the association unit is
An information processing device as described in claim 5, wherein the second report information is created using an application provided by the information processing device, and the process is performed depending on whether or not identification information identifying the first report information is assigned to the second report information. The information processing apparatus according to claim 1 , wherein the search based on the search condition is performed only on first form information whose state has been confirmed in the storage unit. An information processing method by an information processing device, the information processing device comprising:
displaying on the terminal device a reception screen for receiving input of information for identifying the first form information to be associated with the second form information from the first form information stored in the storage unit;
Correlating the first form information identified based on the identifying information with the second form information ;
The reception screen is
a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions;
The association is
An information processing method for associating first form information identified based on a result of searching the storage unit using the search conditions with second form information . The information processing device,
When there are a plurality of pieces of the specified first form information, a selection screen including the plurality of pieces of the specified first form information is displayed on the terminal device;
9. The information processing method according to claim 8 , wherein the first form information selected on the selection screen is associated with the second form information. The information processing device,
comparing first form information associated with the second form information with the second form information;
10. The information processing method according to claim 8, wherein information indicating the result of the matching is displayed on the terminal device. The information processing device,
11. The information processing method according to claim 10 , wherein information indicating the result of the matching is displayed on the terminal device together with the first form information and second form image data including the second form information. An information processing method according to claim 11, wherein the search based on the search criteria is performed only on first report information whose status has been confirmed in the storage unit. displaying on the terminal device a reception screen for receiving input of information for identifying the first form information to be associated with the second form information from the first form information stored in the storage unit;
Correlating the first form information identified based on the identifying information with the second form information ;
The reception screen is
a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions;
The association is
A program that causes an information processing device to execute a process of associating first form information identified based on a result of searching the storage unit using the search conditions with second form information . An information processing system including an information processing device and a terminal device,
The information processing device includes:
a display control unit that displays, on the terminal device, a reception screen that receives input of information that identifies first form information to be associated with second form information from the first form information stored in the storage unit;
a correlation unit that correlates the first form information identified based on the identifying information with the second form information,
The reception screen is
a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions;
The association unit
associates the first form information identified based on the result of searching the storage unit using the search conditions with the second form information;
The terminal device
An information processing system having a display unit that displays the reception screen.