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

Abstract

To allow a user to select an object to be collated.SOLUTION: An information processing device comprises an input acceptance unit and a display control unit. The input acceptance unit accepts a change instruction to change description information included in first document information to be collated from a terminal device for description information whose collation results do not match description information included in the first document information among description information included in second document information associated with the first document information. The display control unit displays a selection screen for selecting description information to be collated with description information whose collation results do not match from among description information included in the first document information on the terminal device according to the change instruction accepted by the input acceptance unit.SELECTED DRAWING: Figure 23

Description

Technical Field

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

Background Art

[0002] Conventionally, when matching two documents (also referred to as "collation"), a system that matches documents based on the similarity of the visual layout is known.

Summary of the Invention

Problems to be Solved by the Invention

[0003] In the above-described conventional technology, when collating two forms such as a claim form and an order form, the collation target is determined from the detailed information included in each form based on the rules on the system, and users of the system cannot change the collation target. Therefore, in the conventional technology, even if there is corresponding detailed information on both documents, depending on the rules on the system, collation may not be performed.

[0004] The disclosed technology aims to enable a user to select a collation target.

Means for Solving the Problems

[0005] The disclosed technology includes an input reception unit that receives, from a terminal device, a change instruction to change the detailed information included in the first form information to be collated, for the detailed information included in the second form information associated with the first form information, which does not match the collation result with the detailed information included in the first form information; and a display control unit that causes the terminal device to display a selection screen for selecting, from the detailed information included in the first form information, the detailed information to be collated with the detailed information whose collation result does not match, in response to the change instruction by the input reception unit. The display control unit receives the change instruction and causes the terminal device to display an additional screen for adding detail information included in the first report information to be matched, and on the additional screen, it receives an operation to instruct the display of the selection screen and causes the terminal device to display the selection screen. , which is an information processing apparatus.

Effects of the Invention

[0006] Disclosure technology allows users to select the data to be matched. [Brief explanation of the drawing]

[0007] [Figure 1] This figure shows an example of the system configuration of the transaction management system according to the first embodiment. [Figure 2] This figure shows an example of the hardware configuration of a transaction management device. [Figure 3] This figure shows an example of the hardware configuration of a terminal device. [Figure 4] This figure shows an example of an order management database. [Figure 5A] This figure shows an example of a purchase order management database. [Figure 5B] This figure shows another example of an order management database. [Figure 6A] This is a diagram showing an example of an invoice management database. [Figure 6B] Another example of an invoice management database is shown in the diagram. [Figure 7] This is a diagram showing an example of a matching management database. [Figure 8] This diagram illustrates the functions of each device included in the transaction management system. [Figure 9] This is the first sequence diagram illustrating the operation of the transaction management system. [Figure 10] This is the first flowchart explaining the processing of the transaction management system. [Figure 11] This figure shows an example of a confirmation screen for order form information. [Figure 12] This is the second flowchart explaining the processing of the transaction management system. [Figure 13] This figure shows an example of a screen for confirming invoice information. [Figure 14] This is the second sequence diagram illustrating the operation of the transaction management system. [Figure 15] The first figure shows an example of how the buyer's terminal will display. [Figure 16] It is a second figure showing an example display of the buyer terminal. [Figure 17] It is a third figure showing an example display of the buyer terminal. [Figure 18] It is a fourth figure showing an example display of the buyer terminal. [Figure 19] It is a third sequence diagram explaining the operation of the transaction management system. [Figure 20] It is a flowchart explaining the process of generating a selection screen. [Figure 21] It is a fifth figure showing an example display of the buyer terminal. [Figure 22] It is a sixth figure showing an example display of the buyer terminal. [Figure 23] It is a seventh figure showing an example display of the buyer terminal. [Figure 24] It is a first figure showing an example of the display form of a list of detailed information. [Figure 25] It is a second figure showing an example of the display form of a list of detailed information. [Figure 26] It is an eighth figure showing an example display of the buyer terminal. [Figure 27] It is a ninth figure showing an example display of the buyer terminal. [Figure 28] It is a figure showing another example of the system configuration of the transaction management system.

Mode for Carrying Out the Invention

[0008] Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the system configuration of the transaction management system.

[0009] The transaction management system 100 of the present 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. Further, the transaction management device 200 of the present embodiment communicates with the terminal device 400 via a network.

[0010] The transaction management device 200 in this embodiment stores the document information contained in the documents created by the terminal device 300. Furthermore, when the transaction management device 200 receives input of document information for documents issued in relation to these documents, it manages the stored document information in association with the input document information.

[0011] In the following explanation, the form information input from the terminal device 300 will be referred to as the first form information, the form containing the first form information will be referred to as the first form, and the form image data containing the first form information will be referred to as the first form image data.

[0012] Furthermore, in the following explanation, the document issued in correspondence with the first document will be referred to as the second document, the document image data representing the second document will be referred to as the second document image data, and the document information contained in the second document will be referred to as the second document information.

[0013] In this embodiment, when the transaction management device 200 receives input of second document information from the terminal device 300, it displays a screen on the terminal device 300 prompting the terminal device 300 to select the first document information that corresponds to the second document information from the first document information already stored. Then, when the first document information is selected on the terminal device 300, the transaction management device 200 associates the selected first document information with the second document information and performs a matching process between the two.

[0014] Thus, in this embodiment, the system accepts input of second document information and displays a screen for selecting the first document information that corresponds to the second document information, thereby establishing a correspondence between the first and second documents. For this reason, in this embodiment, there is no need to visually check the document information of the two documents, and the correspondence between documents can be easily performed. Furthermore, in this embodiment, since the correspondence between documents is made easy, the workload of the matching process can also be reduced.

[0015] Furthermore, in this embodiment, if the transaction management device 200 matches the first and second report information, which are associated with each other, and the results do not match, it displays a selection screen on the terminal device 300 for selecting a detail from the detail information contained in the second report information to match with a certain detail from the first report information. This selection screen may display a list of detail information contained in the first report information.

[0016] The detail information included in the second report information may be one of several detail information items included in the second report information. Furthermore, the detail information is detail information included in the second report information that does not match the detail information included in the first report information.

[0017] In this embodiment, the detail information refers, for example, to information that associates the name of a detail item with the value of that detail item, as described in the detail section of the form. The detail section of the form is the part that shows the aggregated results of the data, and is the part in which the same format of data is repeatedly printed vertically for each detail item.

[0018] Furthermore, in this embodiment, when a terminal device 300 selects detail information included in the first document information on the selection screen, the transaction management device 200 matches the selected detail information with a certain detail information included in the second detail information, treating it as the matching target.

[0019] Thus, in this embodiment, if the matching results of the first report information and the second report information do not match, the user of the terminal device 300 can be allowed to select from the detail information contained in the second report information to match with a certain detail information in the first report information. Furthermore, in this embodiment, by displaying a list of detail information contained in the second report information on the selection screen, it is made easier for the user of the transaction management system 100 to select the detail information to be matched.

[0020] The terminal device 300 in this embodiment is primarily used by customers who place orders via the transaction management device 200. In other words, the terminal device 300 is used by buyers who purchase goods, etc. The terminal device includes various types of terminal devices such as PCs (Personal Computers), smart terminals (smartphones), and tablet terminals (the same applies to the terminal device 400 described later). In the following description, the terminal device 300 may be referred to as the buyer terminal 300.

[0021] In this embodiment, the ordering party is, for example, a business that places orders with various suppliers. This business may be an individual, a company, or a legal entity. In the following description of the embodiments, the business may be referred to as a tenant.

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

[0023] In this embodiment, the first document is, for example, a product order. In this case, the information of the first document is the order information showing the details of the order. If the first document is a purchase order, the second document corresponding to the first document is the invoice corresponding to this purchase order. In this case, the information of the second document is the invoice information showing the details of the invoice, and the image data of the second document is the invoice image data. Alternatively, for example, the first document may be a purchase order and the second document may be a delivery note, or the first document may be a quotation and the second document may be a purchase order.

[0024] In the following explanation, the purchase order will be used as an example of the first type of document, and the invoice as an example of the second type of document.

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

[0026] The transaction management device 200 of this embodiment includes a storage unit 250 and a transaction management unit 260. The storage unit 250 includes a customer management database 210, an order management database 220, an invoice management database 230, and a matching management database 240.

[0027] The customer management database 210 stores customer information about customers. In other words, the customer management database 210 stores information about the seller. The order management database 220 stores order management information.

[0028] The order management information in this embodiment is information for managing order information and includes order information. The order information in this embodiment may be extracted by a document recognition process on order image data created at the buyer terminal 300.

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

[0030] The invoice management database 230 stores invoice management information.

[0031] The invoice management information in this embodiment is information for managing invoice information and includes invoice information. The invoice information in this embodiment is information extracted from invoices received by the buyer from the seller, and the invoice in this embodiment is issued by the seller and given to the buyer in response to a purchase order issued by the buyer.

[0032] Invoice information may be obtained by performing document recognition processing on invoice image data in the transaction management device 200. Alternatively, invoice information may be obtained as a result of OCR processing performed by an image forming apparatus or the like.

[0033] The matching management database 240 stores information such as the results of matching purchase order information and invoice information.

[0034] When the transaction management unit 260 matches the invoice information of an invoice received by the buyer with the purchase order information of a purchase order issued by the buyer, it displays a screen on the buyer's terminal 300 that links the invoice information with the purchase order information. In other words, the transaction management unit 260 links the invoice management information with the purchase order management information.

[0035] Specifically, when the transaction management unit 260 receives a matching instruction from the buyer terminal 300 for invoice information and purchase order information, it displays a screen on the buyer terminal 300 for selecting the invoice information to be matched and the corresponding purchase order information.

[0036] In this embodiment, by displaying such a screen, it is possible to associate invoice information and purchase order information within the transaction management system 100, even when, for example, both or either of the invoice and purchase order are in paper format. In other words, according to this embodiment, documents can be easily associated with each other. Furthermore, in this embodiment, since it is easy to associate related documents with each other, the workload in matching work is also reduced.

[0037] Matching is the process of comparing the contents of an order with the contents of the corresponding order received, and confirming whether the contents of the order and the contents of the order match.

[0038] Furthermore, if the transaction management unit 260 finds that the invoice information and purchase order information, which are associated with each other, do not match, it displays a selection screen on the buyer terminal 300 for selecting the item information to match with the item information contained in the invoice information from the item information contained in the purchase order information.

[0039] Furthermore, in the example shown in Figure 1, the customer management database 210, the purchase order management database 220, the invoice management database 230, and the matching management database 240 are provided in the transaction management device 200, but this is not limited to that. Some or all of these databases may be provided in other devices. Also, the transaction management device 200 may be implemented by multiple information processing devices.

[0040] Next, the hardware configuration of the transaction management device 200 in this embodiment will be described.

[0041] Figure 2 shows an example of the hardware configuration of a trading management device. The trading management device 200 is built on a computer and, as shown in Figure 2, includes a CPU 201, ROM 202, RAM 203, HD 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.

[0042] Of these, the CPU 201 controls the operation of the entire transaction management device 200. The ROM 202 stores programs used to drive the CPU 201, such as the IPL. The RAM 203 is used as the work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading or writing of various data to the HD 204 according to the control of the CPU 201. The display 206 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 208 is an interface for connecting various external devices. External devices in this case 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 each component such as the CPU 201 shown in Figure 2.

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

[0044] Next, with reference to Figure 3, the hardware configuration of the buyer terminal 300 in this embodiment will be described. Figure 3 is a diagram showing an example of the hardware configuration of a terminal device. The terminal device 300 in 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, data bus B2, and GPS receiver 311.

[0045] Of these, the CPU 301 is an arithmetic processing unit that controls the operation of the entire terminal device 300. The ROM 302 stores programs used to drive the CPU 301, such as the CPU 301 and IPL. The RAM 303 is used as the work area for the CPU 301. The EEPROM 304 reads or writes various data, such as smartphone (terminal device) programs, according to the control of the CPU 301. The ROM 302, RAM 303, and EEPROM 304 are examples of the storage devices of the terminal device 300.

[0046] The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging means that captures an image of a subject and obtains image data according to the control of the CPU 301. Note that an imaging means other than a CMOS sensor, such as a CCD (Charge Coupled Device) sensor, may also be used.

[0047] The image sensor interface 306 is a circuit that controls the driving of the CMOS sensor 305. The acceleration / direction sensor 307 is a variety of sensors, such as an electronic magnetic compass, gyrocompass, and acceleration sensor that detect the Earth's magnetic field. The media interface 309 controls the reading or writing (storage) of data to the recording medium 308, such as flash memory. The GPS receiver 311 receives GPS signals from GPS satellites. The data bus B2 is an address bus and data bus for electrically connecting the various components, such as the CPU 301 shown in Figure 3.

[0048] Furthermore, the terminal device 300 includes a long-range communication circuit 312, an antenna 312a for the long-range communication circuit 312, a CMOS sensor 313, an image sensor interface 314, a microphone 315, a speaker 316, an audio input / output interface 317, a display (display device) 318, an external device connection interface 319, a short-range communication circuit 320, an antenna 320a for the short-range communication circuit 320, and a touch panel 321.

[0049] 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 according to the control of the CPU 301. The image sensor interface 314 is a circuit that controls the driving of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into electrical signals. The speaker 316 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and speech. The sound input / output interface 317 is a circuit that processes the input and output of sound signals between the microphone 315 and the speaker 316 according to the control of the CPU 301.

[0050] The display 318 is a type of display means, such as a liquid crystal or organic EL (Electro Luminescence), that displays images of the subject and various icons. 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 the user to operate the terminal device 300 by pressing the display 318. The display 318 is an example of a display unit of the terminal device 300. The user is, for example, an individual or, in the case of a tenant, an employee of the business operator.

[0051] In this embodiment, the terminal device 300 may be, for example, an information processing device having a similar functional configuration to the transaction management device 200.

[0052] Next, with reference to Figures 4 to 8, the databases of the transaction management device 200 will be described. Figure 4 is a diagram showing an example of the order management database.

[0053] The order management database 210 in this embodiment is, for example, provided for each tenant, but it may also be configured so that definition information associated with the tenant ID (tenant identification information) is stored together with other tenants in one or more databases. Furthermore, the order management database 210 in this embodiment includes information items such as name, address, telephone number, email address, and contact person's name, and these items are associated with the tenant ID (tenant identification information) and tenant name.

[0054] In this embodiment, in the customer management database 210, information including values ​​for items such as name, address, telephone number, email address, and contact person's name may be referred to as customer information. The tenant ID and tenant name are information used to identify the tenant. The value of the item "Name" indicates the name of the trading partner (billing party), and the values ​​of the items "Address," "Telephone Number," "Email Address," and "Contact Person's Name" indicate the billing party's address, telephone number, email address, and the name of the person in charge of the transaction, respectively.

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

[0056] In this embodiment, when the transaction management device 200 receives input from the buyer terminal 300, the customer information is stored in the customer management database 210.

[0057] Figure 5A shows an example of an order management database. The order management database 220 in this embodiment may be provided for each tenant, similar to the customer management database 210.

[0058] The order management database 220 includes the following information items: order number, corresponding invoice number, confirmation status, document status, customer, total amount, order date, information status, document image path, and detailed information. Each item is associated with the tenant name. In this embodiment, a tenant ID may be used to identify the tenant instead of the tenant name.

[0059] Furthermore, in the order management database 220, the item "order number" is associated with other items. In this embodiment, the information in the order management database 220 that includes the value of the item "order number" and the values ​​of other items is called order management information.

[0060] Furthermore, in the order management information, items such as "corresponding invoice number," "confirmation status," "document status," and "information status" are items for managing order information and do not necessarily have to be included in the order information itself.

[0061] The value of the item "Order Number" is document identification information used to identify the order, order information, and order management information. In other words, the value of the item "Order Number" is identification information used to identify the first document information.

[0062] The value of the item "Corresponding Invoice Number" is identification information used to identify an invoice containing the invoice information corresponding to the purchase order information identified by the purchase order number. In other words, the value of the item "Corresponding Invoice Number" is document identification information used to identify a document (invoice). In other words, the value of the item "Corresponding Invoice Number" is identification information used to identify the second document information.

[0063] In this embodiment, if the value of the item "corresponding invoice number" is stored in the order management database 220, it indicates that the association between order information and invoice information has been completed.

[0064] In the example in Figure 5A, the value of the item "Corresponding Invoice Number" is stored as "30126". Therefore, in the example in Figure 5A, it can be seen that the association between the purchase order information identified by the purchase order number "190186" and the invoice number identified by the invoice number "30126" has been completed.

[0065] The value of the "Confirmation Status" field indicates the progress of the matching process for the corresponding purchase order information. Specifically, for example, if the value of the "Confirmation Status" field is "Confirmed," it indicates that the buyer's visual matching process has been completed. Also, for example, if the value of the "Confirmation Status" field is "Requires Confirmation," it indicates that the buyer's visual matching process has not been performed, and if the value of the "Confirmation Status" field is "Unconfirmed," it indicates that the association between the purchase order information and the invoice information has not been made, in which case the value of the "Corresponding Invoice Number" field will be empty. Furthermore, if the value of the "Confirmation Status" field is "Successful," it indicates that the matching process by the transaction management device 200 was successful.

[0066] In the example in Figure 5A, the value of the item "Confirmation Status" is "Confirmation Required". Therefore, in the example in Figure 5A, it can be seen that a visual verification has not been performed between the order information identified by order number "190186" and the invoice number identified by invoice number "30126".

[0067] The value of the item "Ordering Party" indicates the name of the ordering party for the order identified by the order number. In the example in Figure 5A, the ordering party is "○○ Co., Ltd." Therefore, it can be seen that the order identified by order number "190186" is an order issued by tenant "△△ Co., Ltd." to ○○ Co., Ltd.

[0068] The values ​​for the items "Total Amount" and "Order Date" represent the total amount and order date as stated on the order form.

[0069] The value of the item "Document Status" indicates the progress of document recognition. In this embodiment, the value of the item "Document Status" includes four states: unprocessed, saved as draft, finalized, and externally outputted. Each state is as follows:

[0070] • Unprocessed state (State 1): This is the state immediately after the acquisition of document information (order information, invoice information), and before any verification of the contents of the document information has been performed.

[0071] • Draft save state (State 2): This state is in the middle of tasks such as checking document information, and is before the document management information (order form management information, invoice management information) is finalized.

[0072] • Confirmed state (State 3): The process of verifying document information has been completed, and the document management information (order management information, invoice management information) has been stored in the document management database (order management database 220, invoice management database 230) as confirmed information. • External output completed (Status 4): The output of report information to the accounting system, etc., which is linked with the transaction management system 100 has been completed.

[0073] The value of the item "Information Status" indicates the progress of the verification process for document information (order information, invoice information) in the transaction management system 100. Specifically, the status of document information includes the following four states.

[0074] • Unprocessed state (State 1): This is the state immediately after the acquisition of document information (order information, invoice information), and before any verification of the contents of the document information has been performed.

[0075] • Draft save state (State 2): This state is in the middle of tasks such as checking document information, and the content of the document information (order form information, invoice information) has not yet been finalized.

[0076] • Confirmed state (State 3): The state in which the verification of document information and other related tasks have been completed, and the document information (order form information, invoice information) has been confirmed.

[0077] In this embodiment, as described above, the state indicating the progress of invoice (order form, bill) recognition and the state indicating the progress of the confirmation work of invoice information (order form information, bill information) are managed separately. Therefore, in this embodiment, for example, after the buyer receives a bill corresponding to an order form and before performing processing such as journal entry of the bill, only the bill information can be determined first, and the determined bill information can be matched with the order form information.

[0078] The value of the item "invoice image path" indicates the storage location of the order form image data.

[0079] The item "detail information" may be associated with items indicating the breakdown of the order amount, such as the items "product code", "product name", "quantity", etc.

[0080] Note that the items of information included in the order form management information are not limited to the example shown in FIG. 5A. The items of information included in the order form management information may not include all the items shown in FIG. 5A, or may include items other than the items shown in FIG. 5.

[0081] FIG. 5B is a diagram showing another example of the order form management database. The example of FIG. 5B shows a case where a plurality of bills issued when the ordered items are stored separately in multiple batches are associated with one order form.

[0082] Note that in the following description, the bill issued when the ordered items are stored separately may be referred to as a separate storage bill. The separate storage bill is a bill corresponding to the items to be stored among the items included in the order form.

[0083] Also, in the following description, the information indicating the separate storage bill may be referred to as separate storage bill information. Therefore, in FIG. 5B, the order form information is associated with a plurality of separate storage bill information.

[0084] Specifically, in the example in Figure 5B, there are two pieces of purchase order management information that include the purchase order number "190186". One of them includes the corresponding invoice number "30126", and the other includes the corresponding invoice number "30127".

[0085] In other words, the invoices identified by invoice numbers "30126" and "30127" are invoices for installment payments.

[0086] Figure 6A shows an example of an invoice management database. The invoice management database 230 in this embodiment may be provided for each tenant, similar to the customer management database 210. The invoice management database 230 in this embodiment includes the following information items: billing source, invoice number, corresponding order number, confirmation status, total amount, issue date, document status, information status, document image path, bank transfer destination, detailed information, etc. Each of these items is associated with the tenant name. In addition, the items "billing destination" and "invoice number" are associated with the other items.

[0087] In the following explanation, the information including the "Billing Party" and "Invoice Number" fields in the invoice management database 230, as well as the values ​​of other fields, will be referred to as invoice management information.

[0088] Furthermore, in the invoice management information, items such as "corresponding order number," "confirmation status," "document status," and "information status" are items for managing invoice information and do not necessarily have to be included in the invoice information itself.

[0089] The value of the "Billing" field indicates the name of the tenant that issued the invoice. In other words, the value of the "Billing" field indicates the name of the tenant that created the invoice information.

[0090] The value of the "Invoice Number" field is identification information used to identify the invoice, invoice information, and invoice management information. In other words, the value of the "Invoice Number" field is identification information used to identify the second set of document information.

[0091] The value of the item "Corresponding Order Number" is identification information used to identify the order containing the invoice information and corresponding order information identified by the invoice number. In other words, the value of the item "Corresponding Order Number" is identification information used to identify the first document information.

[0092] In this embodiment, if the value of the item "Corresponding Purchase Order Information" is stored in the invoice management database 230, it indicates that the association between invoice information and purchase order information has been completed.

[0093] In the example in Figure 6A, the value of the item "Corresponding Order Number" is stored as "190186". Therefore, in the example in Figure 6A, it can be seen that the mapping between the invoice number identified by invoice number "30126" and the order information identified by order number "190186" has been completed.

[0094] The value of the "Confirmation Status" field will be "Confirmation Required" if the buyer has not yet confirmed the matching results after the invoice information has been received. Conversely, the value of the "Status" field will be "Confirmed" if the buyer has confirmed the matching results.

[0095] In the example in Figure 6A, the value of the item "Confirmation Status" is "Confirmation Required". Therefore, in the example in Figure 6A, it can be seen that a visual verification has not been performed between the invoice number identified by invoice number "30126" and the purchase order information identified by purchase order number "190186".

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

[0097] The value of the "Document Image Path" field indicates the storage location of the order form image data. The "Detailed Information" field is associated with fields that show the breakdown of the total amount, such as "Product Code," "Product Name," and "Quantity."

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

[0099] Figure 6B shows another example of an invoice management database. In Figure 6B, one invoice is a consolidated invoice associated with multiple purchase orders.

[0100] Specifically, in Figure 6B, the invoice management information corresponding to invoice number "30216" includes multiple corresponding purchase order numbers "190187" and "190188".

[0101] Therefore, the invoice identified by invoice number "30216" is a combined invoice for the purchase order identified by purchase order number "190187" and the purchase order identified by purchase order number "190188".

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

[0103] The matching management database 240 includes information items such as order number, invoice number, processing date and time, total amount, and item details, with the "order number" item being associated with the other items.

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

[0105] The "Detailed Information" field is associated with fields such as "Product Code," "Product Name," and "Quantity," which show the breakdown of the total amount. In the matching management database 240, the values ​​of these fields represent the results of matching detailed information containing matching product names between the detailed information included in the invoice information and the detailed information included in the purchase order information.

[0106] In the example in Figure 7, the result of matching the total amount is "requires verification," and the result of matching the itemized information 1 included in the invoice information and purchase order information shows that the unit price "requires verification."

[0107] Furthermore, in this embodiment, a match in the matching results may be expressed as "success," while a mismatch in the matching results may be expressed as "requires verification."

[0108] Note that the items of information included in the matching management database 240 are not limited to the example shown in Figure 7. The items of information included in the matching management database 240 do not have to include all of the items shown in Figure 7, and may also include items other than those shown in Figure 7.

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

[0110] First, the functions of the transaction management unit 260 of the transaction management device 200 will be described. The transaction management unit 260 of the transaction management device 200 in this embodiment includes a transmission unit 261, a reception unit 262, an input reception unit 263, a document recognition unit 264, a display control unit 265 (first display control unit), a screen generation unit 266, a storage control unit 267, a correspondence unit 268, a matching unit 269, and an output unit 270.

[0111] The transmitting unit 261 and the receiving unit 262 transmit and receive information between the transaction management device 200 and other devices. The input receiving unit 263 receives various inputs to the transaction management device 200. Specifically, the input receiving unit 263 receives inputs and requests for various information from the buyer terminal 300. Various information includes, for example, document image data (invoice image data, purchase order image data), document information (invoice information, purchase order information), etc.

[0112] The document recognition unit 264 extracts document information from document image data. Specifically, the document recognition unit 264 performs character recognition processing on the document image data to obtain text data, extracts items and their values ​​from the obtained text data, and associates the items with their values ​​to obtain document information. In the following explanation, the process of extracting items and their values ​​from the document image, and converting the items and their values ​​into text data and associating them with each other is referred to as document recognition.

[0113] In this embodiment, when the input reception unit 263 receives invoice image data, the document recognition unit 264 obtains invoice information from the invoice image data. Also in this embodiment, when the input reception unit 263 receives purchase order image data, the document recognition unit 264 obtains purchase order information from the purchase order image data.

[0114] 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. More specifically, in either case, screen data may be communicated so that it can be displayed on each terminal device described later, and the display control unit 340 may be used to control the display of the seller terminal 400.

[0115] The screen generation unit 266 generates screen data to display a selection screen for the buyer terminal 300, based on the matching result between the order information and the invoice information by the matching unit 269. Specifically, if the matching result requires confirmation, the screen generation unit 266 generates screen data for a selection screen to allow the buyer to select the item information to match with the item information in the invoice information from among the item information included in the order information associated with the invoice information.

[0116] The storage control unit 267 updates each database in accordance with the processing performed by the transaction management unit 260.

[0117] The matching unit 268 associates the order information with the invoice information. Specifically, when the matching unit 268 receives an operation to instruct the matching of invoice information and order information, it determines whether the invoice information and order information are already associated. If the invoice information is not associated with the order information, the display control unit 265 then displays a screen on the buyer terminal 300 for selecting the order information to associate with the invoice information.

[0118] When purchase order information is selected on this screen, the mapping unit 268 maps the selected purchase order information to the invoice information. Specifically, the mapping unit 268 causes the storage control unit 267 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.

[0119] The matching unit 269 performs matching processing between the corresponding invoice information and purchase order information, and the storage control unit 267 updates the matching management database 240. The output unit 270 outputs various types of information from the transaction management device 200.

[0120] Next, the functions of the buyer terminal 300 will be described. The buyer terminal 300 in this embodiment has an operation reception unit 330, a display control unit 340 (second display control unit), and a communication control unit 350.

[0121] The operation reception unit 330 receives various operations for the buyer terminal 300. Specifically, the operation reception unit 330 receives operations corresponding to information displayed on the buyer terminal 300's display 318, and operations to make requests to the transaction management device 200, for example. The display control unit 340 displays information on the buyer terminal 300's display. The communication control unit 350 controls the transmission and reception of information between the buyer terminal 300 and other devices.

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

[0123] Figure 9 is the first sequence diagram illustrating the operation of the transaction management system. In Figure 9, steps S901 to S908 show the operation in the transaction management system 100 from when the purchase order information of a purchase order issued by a buyer is stored in the purchase order management database 220. Also in Figure 9, steps S909 to S917 show the operation in the transaction management system 100 from when the invoice information of an invoice received by a buyer from a seller is stored in the invoice management database 230.

[0124] Furthermore, the operation of storing purchase order information in the purchase order management database 220 and the operation of storing invoice information in the invoice management database 230 may be performed at independent times.

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

[0126] The request to register order information may be sent to the transaction management device 200 along with the order image data entered into the buyer terminal 300, for example, or it may be a CSV file or the like that associates the item names and item values ​​listed on the paper order form.

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

[0128] 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 information (step S904).

[0129] The buyer terminal 300 receives an instruction to display a confirmation screen, and the display control unit 340 displays a confirmation screen of the order information (step S905).

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

[0131] Upon receiving this request, the transaction management device 200 uses the storage control unit 267 to determine the status of the order information stored in the order management database 220 in step S903 (step S908). Specifically, the storage control unit 267 sets the values ​​of the items "Document Status" and "Information Status" to "Confirmed" in the order management information, including the order information stored in the order management database 220.

[0132] The above describes the process of storing purchase order information in the purchase order management database 220. Next, we will explain the process of storing invoice information in the invoice management database 230.

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

[0134] 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 267 (step S912). Details of step S912 will be described later.

[0135] 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 checking the invoice information (step S913).

[0136] The buyer terminal 300 receives a command to display a confirmation screen, and the display control unit 340 displays a confirmation screen of the invoice information (step S914).

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

[0138] Upon receiving this request, the transaction management device 200 uses the storage control unit 267 to determine the status of the invoice information stored in the invoice management database 230 in step S912 (step S917). Specifically, the storage control unit 267 sets the value of the item "Information Status" to "Confirmed" in the invoice management information, including the invoice information stored in the invoice management database 230.

[0139] In this embodiment, before processing such as journal entries for invoices, the invoice information can be finalized first, and the finalized invoice information can be compared with the purchase order information. Alternatively, in this embodiment, the "Document Status" item in the invoice management information may be finalized after the journal entries for the invoice information have been completed.

[0140] The above describes the operation of storing invoice information in the invoice management database 230. Next, the processing of the storage control unit 267 will be explained.

[0141] Figure 10 is a first flowchart illustrating the processing of the transaction management device. Figure 10 shows the details of the processing of the storage control unit 267 in step S903 of Figure 9, where the order information is stored in the order management database 220.

[0142] In this embodiment, when the transaction management unit 260 of the transaction management device 200 receives a request to register order information from the input receiving unit 263 (step S1001), the storage control unit 267 determines whether or not the order is in paper format (step S1002).

[0143] Specifically, the storage control unit 267 determines whether the information transmitted from the buyer terminal 300 along with the order information registration request is order form image data. If order form image data is transmitted from the buyer terminal 300, it indicates that a paper order form has been read by a reading device such as a scanner, and therefore the order form is in paper format.

[0144] In step S1002, if the purchase order is not in paper format, the transaction management unit 260 proceeds to step S1004, which will be described later. A purchase order being not in paper format means that the information sent from the buyer terminal 300 along with the purchase order information registration request is, for example, data in CSV format.

[0145] In this case, the order information transmitted from the buyer terminal 300 may be order information created using an application provided by the transaction management device 200 to the buyer terminal 300, or it may be order information created using another application.

[0146] In step S1002, if the order form is in paper format, the transaction management device 200 uses the document recognition unit 264 to perform document recognition on the order form image data and extracts order form information from the order form image data (step S1003).

[0147] Next, the transaction management device 200 stores the order information in the order management database 220 using the storage control unit 267 (step S1004), generates screen data for displaying the order information confirmation screen using the display control unit 265 (step S1005), and then terminates the process.

[0148] The order confirmation screen will be explained below with reference to Figure 11. Figure 11 is a diagram showing an example of the order confirmation screen. Note that the example in Figure 11 may also be an example of the order confirmation screen when the order is in paper format.

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

[0150] Display area 112 displays the order form image data. Display area 113 displays the order form information extracted from the order form image data through form recognition. In the example in Figure 11, the order form number, customer, total amount, and details are displayed. Operation button 116 is also displayed in display area 113. Operation button 116 is used to set the information status of the order form information displayed in display area 113 to the "confirmed" state.

[0151] The display area 114 shows the document status value. Operation button 26 is used to change the status of the order, which is displayed on screen 111 with order image data and order information, to the draft save state. Operation button 27 is used to change the status of the order, which is displayed on screen 111 with order image data and order information, to the confirmed state.

[0152] In this embodiment, for example, if you want to modify the order information extracted by document recognition, you can do so by changing the value of the item to be modified on the buyer terminal 300.

[0153] In this embodiment, the buyer is asked to confirm the order information as described above.

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

[0155] In this embodiment, when the transaction management unit 260 of the transaction management device 200 receives a request to register invoice information from the input reception unit 263 (step S1201), the storage control unit 267 determines whether or not the invoice is in paper format (step S1202).

[0156] Specifically, the storage control unit 267 determines whether the information transmitted from the buyer terminal 300 along with the request to register invoice information is invoice image data. If invoice image data is transmitted from the buyer terminal 300, it indicates that a paper invoice has been read by a reading device such as a scanner, and therefore the invoice is in paper format.

[0157] In step S1202, if the invoice is not in paper format, the transaction management unit 260 proceeds to step S1204, which will be described later. The invoice is not in paper format if the information sent from the buyer terminal 300 along with the invoice information registration request is, for example, data in CSV format.

[0158] In this case, the invoice information transmitted 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 transmitted from the seller terminal 400 to the buyer terminal 300 via the transaction management device 200.

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

[0160] Furthermore, the invoice information may be invoice information created using other applications.

[0161] In step S1202, if the invoice is in paper format, the transaction management device 200 uses the document recognition unit 264 to perform document recognition on the invoice image data and extracts purchase order information from the invoice image data (step S1203).

[0162] Next, the transaction management device 200 determines, using the mapping unit 268, whether or not there is purchase order information associated with the invoice information (step S1204). Specifically, the mapping unit 268 determines whether the invoice information was created using an application provided by the transaction management device 200, and whether or not a corresponding purchase order number is assigned to the invoice information.

[0163] If no corresponding order information exists in step S1204, the transaction management device 200 proceeds to step S1206, which will be described later.

[0164] In step S1204, if the corresponding purchase order information exists, the transaction management device 200 uses the matching unit 268 to match the invoice information with the purchase order information (step S1205).

[0165] Specifically, the transaction management device 200 uses the matching unit 268 to identify order information stored in the order management database 220, where the value of the order number matches the corresponding order number assigned to the invoice information. Then, the transaction management device 200 uses the storage control unit 267 to set the value of the item "corresponding invoice number" in the order management information containing the identified order information to the invoice number included in the invoice information.

[0166] Next, the transaction management device 200 stores the invoice information in the invoice management database 230 using the storage control unit 267 (step S1206). At this time, if there is corresponding purchase order information for the invoice information, the value of the item "corresponding purchase order number" in the invoice management information containing the invoice information is set to the purchase order number of the corresponding purchase order information.

[0167] Next, the transaction management device 200, using the display control unit 265, generates screen data for displaying the invoice information confirmation screen (step S1207), and then terminates the process.

[0168] Next, with reference to Figure 13, the invoice information confirmation screen of this embodiment will be described. 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 format.

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

[0170] Invoice image data is displayed in display area 132.

[0171] Display area 133 includes display areas 134, 135, 136, and 137. Display area 134 displays invoice information extracted from invoice image data through document recognition. In the example in Figure 13, the invoice number, billing source, invoice amount, and itemized information are displayed. Operation button 140 is also displayed in display area 134. Operation button 140 is used to set the information status of the invoice information displayed in display area 134 to the "confirmed" state.

[0172] In this embodiment, for example, when correcting invoice information extracted by document recognition, the buyer terminal 300 can perform an operation to change the value of the item to be corrected before operating the operation button 140.

[0173] The display area 135 shows input fields for journal entry information for the invoice. In this embodiment, after the operation button 140 is operated to confirm the invoice information, the input of journal entry information can be performed.

[0174] Display area 136 shows the document status of the invoice. In the example in Figure 13, display area 136 shows "Pending," indicating that the status of the invoice has not yet been finalized.

[0175] Display area 137 shows the progress of the matching process. In the example in Figure 13, display area 137 shows "Requires Confirmation," indicating that the matching results have not yet been confirmed.

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

[0177] In this embodiment, when displaying the invoice information confirmation screen, tab 138 is displayed with the tab selected.

[0178] Furthermore, in this embodiment, when tab 139 is selected on the invoice information screen 131, it is assumed that a matching instruction has been received between the invoice information and the purchase order information, with the invoice image data displayed in the display area 132. Here, the invoice information with the invoice image data displayed in the display area 132 is the invoice information selected as the target for matching.

[0179] Next, with reference to Figure 14, the matching of order information and invoice information in this embodiment will be explained.

[0180] Figure 14 is a second sequence diagram illustrating the operation of the transaction management system. In the transaction management system 100 of this embodiment, the buyer terminal 300 receives an operation from a tenant or the like to instruct a matching (step S1401). Specifically, when the buyer terminal 300 receives a selection of a tab to display the matching result with the purchase order information on the invoice information confirmation screen, it is assumed that an operation to instruct a matching has been received.

[0181] Upon receiving this instruction, the buyer terminal 300 sends a request to the transaction management device 200 to display the matching results (step S1402).

[0182] When the transaction management device 200 receives this display request via the input reception unit 263, the matching unit 268 determines whether or not there is purchase order information that is subject to matching with the invoice information displayed on the confirmation screen (step S1403).

[0183] Specifically, the matching unit 268 determines whether a corresponding order number value exists in the invoice management database 230 for the invoice information displayed on the confirmation screen.

[0184] The following steps S1404 to S1406 are performed when it is determined in step S1403 that there is purchase order information to be matched.

[0185] In step S1403, if it is determined that there is purchase order information to be matched, the transaction management device 200 matches the invoice information with the purchase order information using the matching unit 269 (step S1404), and outputs information indicating the matching result and an instruction to display this information to the buyer terminal 300 using the output unit 270 (step S1405).

[0186] Matching refers to comparing the breakdown of orders in the purchase order information with the breakdown of invoices in the invoice information to confirm whether the breakdown of orders and the breakdown of orders match.

[0187] When the buyer terminal 300 receives information indicating the matching result and a display instruction, it causes the display control unit 340 to display the matching result (step S1406).

[0188] The following steps S1407 through S1423 are the steps taken when it is determined in step S1403 that there is no purchase order information to match.

[0189] If it is determined in step S1403 that there is no 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 the search screen for order information to be matched (step S1407).

[0190] Upon receiving this display instruction, the buyer terminal 300 causes the display control unit 340 to display the order information search screen (step S1408). Subsequently, when the search criteria for the order information are entered by the tenant or the like (step S1409), the buyer terminal 300 sends a search request to the transaction management device 200 (step S1410).

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

[0192] At this time, the matching unit 268 searches the order management database 220 for order information that matches the search criteria from the order information for which the value of the item "Information Status" is set to "Confirmed".

[0193] Steps S1412 to S1415 below describe the processing when one order information is extracted as a search result in step S1411. In this embodiment, when one order information is identified by the search, the transaction management device 200 associates the identified order information with the invoice information using the matching unit 268 (step S1412).

[0194] Specifically, the mapping unit 268 causes the storage control unit 267 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. The mapping unit 268 also causes the storage control unit 267 to store the invoice number of the identified order information in the order management database 220 as the corresponding invoice number of the invoice information.

[0195] Thus, the search screen displayed in step S1408 is an example of a reception screen that accepts the selection of invoice information and corresponding purchase order information.

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

[0197] At this time, the transaction management device 200 stores the matching results in the order management database 220, the invoice management database 230, and the matching management database 240, respectively, using the storage control unit 267.

[0198] Specifically, the storage control unit 267 stores information indicating the matching results for invoices and purchase orders as the value of the item "Confirmation Status" in the purchase order management database 220 and the invoice management database 230. For example, if the matching of the documents is successful, the storage control unit 267 sets the value of the item "Confirmation Status" to "Success," and if the matching of the documents fails, it sets the value of the item "Confirmation Status" to "Requires Confirmation." Details regarding the success and failure of document-level matching will be described later.

[0199] Furthermore, the storage control unit 267 stores the matching results for each item information unit contained in the invoice information and purchase order information in the matching management database 240. Details regarding the success and failure of the matching of item information units will be described later.

[0200] When the buyer terminal 300 receives information indicating the matching result, it displays this information (step S1415).

[0201] The following steps S1416 to S1423 show the process when multiple purchase order information is extracted in the search in step S1411.

[0202] In step S1411, when multiple order information is extracted, the transaction management device 200 sends a display instruction to the buyer terminal 300 via the display control unit 265 (step S1416).

[0203] When the buyer terminal 300 receives an instruction to display the search results, it causes the display control unit 340 to display a selection screen for selecting order information from the multiple order information extracted as search results (step S1417). In other words, the transaction management device 200 displays a reception screen on the buyer terminal 300 to accept the selection of order information to be associated with invoice information.

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

[0205] When the transaction management device 200 receives a notification from the input reception unit 263 that identifies the purchase order information, the matching unit 268 associates the identified purchase order information with the invoice information (step S1420).

[0206] Next, the transaction management device 200 matches the invoice information with the selected purchase order information using the matching unit 269 (step S1421).

[0207] Next, the transaction management device 200 transmits information indicating the matching result and an instruction to display this information to the buyer terminal 300 via its output unit 270 (step S1422).

[0208] When the buyer terminal 300 receives information indicating the matching result and a display instruction, it causes the display control unit 340 to display the information indicating the matching result (step S1423).

[0209] Thus, in this embodiment, if the invoice information and purchase order information have not been associated before a matching instruction is received, a matching screen for associating the invoice information and purchase order information is displayed on the buyer terminal 300.

[0210] Furthermore, the order information displayed on the matching screen is limited to only those with a confirmed information status. Therefore, in this embodiment, it is possible to prevent order information that may be changed in the future from being selected for matching. In other words, in this embodiment, it is possible to prevent unconfirmed document information from being included in the matching process.

[0211] In the example shown in Figure 14, the operation to instruct matching is performed from the invoice information confirmation screen displayed when storing invoice information in the invoice management database 230. However, the timing of the operation to instruct matching is not limited to this.

[0212] In this embodiment, for example, the buyer terminal 300 may be made to display a list of received invoices, 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 match the invoice information with the purchase order information at any time after receiving the invoice.

[0213] 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 the search screen displayed on the buyer terminal 300 in step S1408 of Figure 14.

[0214] The screen 131A shown in Figure 15 includes display areas 132 and 133A, and operation buttons 28 and 29. Invoice image data is displayed in display area 132.

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

[0216] Input fields 141 and 142 are input fields for search criteria of order information. Specifically, the order number is entered in input field 141, and the date and time when the order information was imported into the transaction management system 100 is entered in input field 142. The import date and time is the date and time when the information status of the order information was set to confirmed.

[0217] Therefore, screen 131A in this embodiment can be considered an example of a reception screen that accepts input of information for identifying the order information associated with the invoice information.

[0218] In the example shown in Figure 15, the search criteria were the order number and import date and time, but this is not limited to these. In this embodiment, the input items used as search criteria can be arbitrarily changed by the tenant's operation.

[0219] Operation button 143 is an operation button used to instruct the user to perform a search using the search criteria entered in input fields 141 and 142. In this embodiment, when search criteria are entered in input fields 141 and 142 and operation button 143 is pressed, the buyer terminal 300 sends a search request to the transaction management device 200 and displays the search results.

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

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

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

[0223] The screen 131B shown in Figure 16 includes display areas 132 and 133B, and operation buttons 28 and 29. In screen 131B, tab 139 is selected.

[0224] Display area 133B includes display areas 134B, 135, 136, and 137A, and display area 134B displays information indicating the matching result.

[0225] Specifically, display area 134B shows the order number and import date and time entered as search criteria in input fields 141 and 142.

[0226] Furthermore, display area 134B has a display area 144A. Display area 144A displays the detailed information of the order information identified by the order number entered in input field 141, and the result of matching each detail information with the detail information included in the invoice information.

[0227] In display area 144A, a notification "Matching successful" is displayed for all the item information included in the purchase order information, indicating that it matches the item information included in the invoice information.

[0228] Here, we will explain the success and failure of matching at the detail information level.

[0229] In this embodiment, the matching result of the item details for the product name is considered "successful" if there is only one item detail with a matching product name in both the invoice information and the purchase order information, and the quantity, unit price, and total amount all match.

[0230] Furthermore, in this embodiment, if there is only one item in the invoice information and purchase order information where the product name matches, and the quantity, unit price, or total amount does not match, the result of matching the item in the product name is set to "requires verification".

[0231] Furthermore, in this embodiment, if there are multiple item entries with matching product names in both the invoice information and the purchase order information, or if there are no item entries with matching product names, Regardless of quantity, unit price, or total amount, the result of matching the detailed information for this product name will be marked as "requires verification."

[0232] Next, we will explain the success and failure of matching at the document level.

[0233] In this embodiment, if the matching result of all detail information is "successful," the progress status of the matching between the documents displayed in the display area 137A will be "successful." Also, in this embodiment, if even one of the detail information matching results is "requires confirmation," the progress status of the matching between the documents will also be "requires confirmation."

[0234] In the example in Figure 16, the progress status of the matching of the documents displayed in display area 137A is "successful," which indicates that all the detail information contained in the invoice information, where the invoice image data is displayed in display area 132, and the purchase order information have matched.

[0235] Figure 17 is a third diagram showing an example of the display on the buyer's terminal. Screen 131C shown in Figure 17 is an example of a screen displayed on the buyer's terminal 300 when multiple order information is 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 an order information selection screen displayed on the buyer's terminal 300 in step S1417 of Figure 14.

[0236] Screen 131C includes a display area 170. The display area 170 displays a list of order information extracted as search results and operation buttons 171.

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

[0238] Upon receiving a notification, the transaction management device 200 performs a matching process by associating the selected purchase order information with the invoice information.

[0239] If the matching is successful, a screen with a layout similar to that shown in Figure 16 will be displayed.

[0240] Figure 18 is the fourth figure showing an example of the display on the buyer's terminal. Screen 131D shown in Figure 18 is an example of a screen displayed on the buyer's terminal 300 when, in the matching process performed after the invoice information and purchase order information have been associated, the detail information contained in the purchase order information does not match the detail information contained in the invoice information. Therefore, screen 131D can be said to be an example of a screen displayed on the buyer's terminal 300 in step S1423 of Figure 14.

[0241] In the display examples of the buyer terminal 300 from Figure 18 onwards, the product name "reception table" included in the details information of the invoice information will be explained as being registered as the product name "table" in the purchase order information associated with the invoice information.

[0242] The screen 131D shown in Figure 18 includes display areas 132 and 133C, and operation buttons 28 and 29. In addition, tab 139 is selected in screen 131D.

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

[0244] Display area 145 displays the search criteria, namely the order number and the import date and time. Additionally, display area 145 displays detailed order information for each product name.

[0245] The display area 144B shows the operation button 144-1. In addition, the display area 144B also displays the order information details 144-2, the matching result 144-3 obtained by matching the order information details with the invoice information including the product name "reception table", and the operation button 144-4 for each piece of information.

[0246] Operation button 144-1 is primarily used when the details of the purchase order information that are to be matched with the details of the invoice information are changed. In this embodiment, when operation button 144-1 is operated after the match target has been changed, a matching process is performed between the details of the invoice information and the details of the modified purchase order information. Operation button 144-1 may be displayed only when the matching result displayed in the display area 137 is "Requires Confirmation".

[0247] In Figure 18, in item information 144-2 included in the order information for order number "190186", the product name is "table". Therefore, the product name does not match the item information in the invoice information, which includes the product name "reception table". As a result, the matching result 144-3 of item information 144-2 is "requires verification".

[0248] In the explanations from Figure 18 onward, the itemized information including the product name "reception table" in the invoice information will be described as a specific itemized piece of information included in the invoice information.

[0249] Certain itemized information can be defined as itemized information included in the invoice information that did not match the itemized information in the purchase order information. Alternatively, certain itemized information can be defined as itemized information included in the invoice information that is currently being reviewed by the user of the buyer terminal 300.

[0250] Operation button 144-4 is an operation button that displays a screen for adding detail information to the matching target, separate from the detail information 144-2 of the order information. In this embodiment, when operation button 144-4 is operated, it becomes possible to add detail information to the order information.

[0251] In this embodiment, for example, the display area 144B may display the product name and corresponding detail information from the order information that did not match the details in the invoice information.

[0252] Furthermore, display area 144B displays a notification "Confirmation Required" for each detail item, indicating that the tenant needs to verify the contents. In addition, each detail item in display area 144B is associated with a checkbox. This checkbox is checked when the tenant or other relevant party has completed the verification process for the matching results of the corresponding detail items.

[0253] In this embodiment, the matching process is considered complete when the tenant has verified all the detail information displayed in the display area 144B.

[0254] Here, referring to Figures 19 and 20, we will explain the case where the result of matching the invoice information and purchase order information is "requires verification".

[0255] Figure 19 is a third sequence diagram illustrating the operation of the transaction management system. Figure 19 shows the operation of the transaction management system 100 when the result of matching the invoice information and purchase order information is determined to require "confirmation," and an operation is performed to instruct the addition of detail information to the purchase order information. In other words, Figure 19 shows the operation of the transaction management system 100 when the operation button 144-4 is operated on screen 131D shown in Figure 18.

[0256] In this embodiment, when the buyer terminal 300 receives an operation to add detail information via the operation reception unit 330 (step S1901), it sends a request to the transaction management device 200 to display a screen for adding detail information (step S1902).

[0257] In other words, the buyer terminal 300 sends a change request to the transaction management device 200 requesting a change to the order information details for the invoice details that do not match the order information details.

[0258] The transaction management device 200 receives this change request (addition request) via the input reception unit 263 and sends an instruction to the buyer terminal 300 to display an additional screen for adding the details information of the purchase order (step S1903). In other words, the display control unit 265 causes the buyer terminal 300 to display a screen for adding the details information of the purchase order to be matched with the invoice information.

[0259] The buyer terminal 300 receives this display instruction and the display control unit 340 displays an additional screen for adding detailed information (step S1904).

[0260] Next, when the buyer terminal 300 receives an operation to instruct the addition of detailed information on the additional screen (step S1905), the display control unit 340 displays the input field for adding detailed information (step S1906).

[0261] Next, when the buyer terminal 300 receives an operation to instruct the display of the selection screen (step S1907), it sends a request to the transaction management device 200 to display the selection screen (step S1908).

[0262] When the transaction management device 200 receives a request to display a selection screen, it generates screen data to display a selection screen for the itemized information included in the purchase order information, according to the selected invoice information (step S1909). Details of the process in step S1909 will be described later.

[0263] Next, the transaction management device 200, via the display control unit 265, transmits a display instruction to the buyer terminal 300 for the selection screen based on the screen data generated by the screen generation unit 266 (step S1910).

[0264] The buyer terminal 300 receives this display instruction and displays the selection screen (step S1911).

[0265] Next, the buyer terminal 300 accepts an operation to select detailed information from the selection screen (step S1912). Subsequently, when the buyer terminal 300 accepts an operation to instruct a rematch (step S1913), it sends a match request to the transaction management device 200 (step S1914).

[0266] When the transaction management device 200 receives a matching request, the matching unit 269 of the transaction management unit 260 performs a rematch between the order information, which includes the selected detail information, and the invoice information (step S1915). Subsequently, the transaction management device 200 sends an instruction to the buyer terminal 300 to display the matching results (step S1916).

[0267] The buyer terminal 300 receives this display instruction and the display control unit 340 causes the rematch result to be displayed on the buyer terminal 300 (step S1917).

[0268] Next, the processing of the screen generation unit 266 will be explained with reference to Figure 20. Figure 20 is a flowchart illustrating the process of generating a selection screen. Figure 20 shows the details of the processing of the screen generation unit 266 in step S1909 of Figure 19.

[0269] In this embodiment, the transaction management unit 260 of the transaction management device 200, upon receiving a request to display a selection screen, identifies the order associated with the invoice information selected as the matching target (step S2001).

[0270] Here, the selected invoice information is the invoice image data displayed in the display area 132 of screen 131D in Figure 18. The screen generation unit 266 refers to the invoice management database 230 and the purchase order management database 220 to identify the purchase order information, including the corresponding purchase order number, that matches the selected invoice information.

[0271] Subsequently, the screen generation unit 266 refers to the order form management database 220 and determines whether there is claim information that has been matched with the specified order form information (step S2002).

[0272] In this embodiment, for example, when the selected claim information is the claim information of an installment invoice, there may be claim information that has been matched with the specified order form information.

[0273] For example, if the selected claim is an installment invoice and the claim information of another installment invoice different from this installment invoice has been matched with the order form information specified in step S2001, there will be matched claim information.

[0274] In step S2002, if there is no matched claim information, the screen generation unit 266 generates screen data for displaying a selection screen including a list of detail information included in the specified order form information (step S2003) and ends the process.

[0275] Specifically, the screen generation unit 266 may refer to the order form management database 220, acquire all the detail information included in the order form information specified in step S2001, and generate screen data for displaying a list of the acquired detail information.

[0276] At this time, the screen generation unit 266 may generate the screen data such that the detail information in which the character string of the product name is closest to the character string indicating the product name included in the detail information of the claim information to be matched is at the top among the detail information included in the specified order form information.

[0277] In step S2002, if there is matched claim information, the screen generation unit 266 extracts the claim number, issue date, and matching result of the claim information that has been matched (step S2004).

[0278] Specifically, the screen generation unit 266 refers to the order management database 220 to identify the order information and corresponding invoice number identified in step S2001. Next, the screen generation unit 266 refers to the invoice management database 230 to obtain the invoice number and issue date from the corresponding invoice number and corresponding invoice information. Next, the screen generation unit 266 refers to the matching management database 240 to obtain the matching results corresponding to the order number and invoice number.

[0279] Next, the screen generation unit 266 generates screen data for a selection screen (step S2005) that includes a list of detail information contained in the order information identified in step S2001, and the matched invoice number, issue date, and match result obtained in step S2004, and then terminates the process.

[0280] The following describes an example of how the buyer terminal 300 displays when adding detailed information, referring to Figures 21 to 27.

[0281] Figure 21 is the fifth figure showing an example of the display on the buyer's terminal. The screen 131E shown in Figure 21 is an example of an additional screen for detailed information displayed on the buyer's terminal 300 in step S1904 of Figure 19. In this embodiment, when the operation button 144-4 is operated on screen 131D in Figure 18, screen 131D transitions to screen 131E.

[0282] Screen 131E includes display areas 132 and 133D, and operation buttons 28 and 29, with tab 139 selected. Display area 133D includes display area 144C, where operation button 144-5 is displayed below detail information 144-2. Operation button 144-5 is used to display the additional input field for detail information.

[0283] When operation button 144-5 is pressed on screen 131E, screen 131E transitions to screen 131F as shown in Figure 22.

[0284] Figure 22 is the sixth figure showing an example of the display on the buyer's terminal. Screen 131F shown in Figure 22 is another example of the additional detail information screen displayed on the buyer's terminal 300 in step S1906 of Figure 19.

[0285] Screen 131F includes display areas 132 and 133E, and operation buttons 28 and 29, with tab 139 selected. Display area 133E includes display area 144D, and in display area 144D, below detail information 144-2, the additional detail information input field 144-6 is displayed.

[0286] Additionally, the additional input field 144-6 displays the operation button 144-7. The operation button 144-7 is used to display the screen for selecting the details to be added.

[0287] In this embodiment, when the operation of selecting operation button 144-7 is performed, screen 131F transitions to screen 131G shown in Figure 23.

[0288] In addition, the user of the buyer terminal 300 can manually enter details into the additional input field 144-6 without operating the operation button 144-7.

[0289] Figure 23 is the seventh figure showing an example of the display on the buyer's terminal. Screen 131G shown in Figure 23 is an example of the selection screen for itemized information displayed on the buyer's terminal 300 in step S1911 of Figure 19. Note that screen 131G shown in Figure 23 is an example of the selection screen displayed on the buyer's terminal 300 in step S2002 of Figure 20 when no matching invoice information exists.

[0290] Screen 131G includes display areas 132 and 133F, and operation buttons 28 and 29, with tab 139 selected. Display area 133F includes display area 144E, and display area 144E includes display area 150.

[0291] On screen 131G, the invoice information to be matched is the invoice information whose image data is displayed in display area 132. Specifically, the invoice information identified by invoice number "30126" is selected.

[0292] Furthermore, in screen 131G, the display area 145 displays the details of the order information for each product name. In the example in Figure 23, the display area 145 associates the order information identified by order number "190186" with the invoice information. Therefore, the display area 150 displays a list of the details information included in the order information identified by order number "190186".

[0293] Display area 150 includes display fields 151, 152, etc., and each display field displays detailed information for each product name included in the order information. Specifically, each display field includes the product name, unit price, quantity, and amount. In addition, each display field may also display the order number and the date the order number was issued.

[0294] The display area 150 includes all product names included in the order information and their corresponding display fields. In this embodiment, the display order of the detail information displayed in the display area 150 may be set so that the detail information that is similar to the product name (string) included in a certain detail information of the invoice information comes first. In other words, the display area 150 displays a list of detail information in order from the detail information containing the product name with the most matching characters to the product name of a certain detail information of the invoice information.

[0295] In the example in Figure 23, among the item information in the invoice information, the product name of a certain item information that is matched with item information 144-2 (the item information that has been matched with item information 144-2) is "reception table". Therefore, in the display area 150, the item information containing the product name "table", which has the most characters matching "reception table" among the item information in the purchase order information, is displayed in the first display field 151.

[0296] In this embodiment, as described above, among the detailed information included in the order form information, a list of the detailed information included in the order form information is displayed in order from a certain detailed information that is a matching target in the invoice information and detailed information that is highly likely to have similar contents.

[0297] Therefore, in this embodiment, it is possible to present to the user of the buyer terminal 300, in order, from the detailed information highly likely to match the detailed information included in the invoice information, and it is possible to reduce the load on the user for the selection operation of the detailed information of the order form information.

[0298] Note that in this embodiment, among the two pieces of detailed information, the more detailed information has more matching character strings in the character string of the product name, the more similar they are to each other, but it is not limited to this. For example, when there are items indicating the product category, etc. in the two pieces of detailed information, the degree of similarity between the two may be determined using this item.

[0299] In this embodiment, when the detailed information to be matched with the detailed information of the invoice information is selected in the display area 150 on the screen 131G, the screen transitions to a screen in a state where the selected detailed information is input in the additional input field 144-6 shown in the screen 131F of FIG. 22.

[0300] At this time, the matching result 144-3 is the result of matching the detailed information 144-2 and the newly selected (added) detailed information with the detailed information of the invoice information.

[0301] Thus, according to this embodiment, it becomes possible to manually add the detailed information of the order form information to be matched with the detailed information of the invoice information.

[0302] Note that when detailed information is selected in the display area 150, the detailed information 144-2 may be deleted and the selected detailed information may be displayed as the detailed information 144-2.

[0303] Furthermore, the display modes of the display area 150 are not limited to the example shown in Figure 23. Other display modes of the display area 150 will be described below with reference to Figures 24 and 25.

[0304] Figure 24 is the first diagram showing an example of the display format of the list of detailed information. In Figure 24, display area 150A is an example of a selection screen displayed on the buyer terminal 300 when multiple purchase order information is identified in step S2001 of Figure 20, and when no matching invoice information exists in step S2002.

[0305] In step S2001, multiple purchase order information is identified when, specifically, the invoice image data displayed in display area 132 is the invoice image data for a consolidated invoice.

[0306] In the example in Figure 24, it is shown that the invoice identified by invoice number "30126" is a consolidated invoice associated with the purchase order identified by purchase order number "190186" and the purchase order identified by purchase order information "190187" (see Figure 6B). In this case, when the invoice information selected for matching is the invoice information of a consolidated invoice, in this embodiment, a list of detailed information may be displayed for each purchase order in the display area 150A.

[0307] Display area 150A includes display fields 155, 156, etc. Display field 155 displays a list of itemized information included in the order information identified by order number "190186", the order number, and the order issue date. Display field 156 displays a list of itemized information included in the order information identified by order number "190187", the order number, and the issue date.

[0308] In this embodiment, by displaying a list of detailed information along with the order number and issue date for each order, the user of the buyer terminal 300 can understand that the invoice information is a consolidated invoice.

[0309] Furthermore, in this embodiment, when displaying a list of detailed information in display fields 155 and 156, as explained in Figure 23, the list of detailed information may be displayed in order from the detailed information containing the product name with the most matching characters to the detailed information of the invoice.

[0310] By displaying a list of detailed information in this way, it becomes easier for users of the buyer terminal 300 to find the detailed information that needs to be matched.

[0311] Furthermore, the display area 150A includes a search key input field 157. In this embodiment, when a search key is entered in the input field 157 and the operation to execute the search process is performed, the detailed information of the invoice information and the corresponding purchase order information may be searched using the search key, and the detailed information containing the search key may be extracted. For example, the product name may be entered as the search key.

[0312] Figure 25 is a second diagram showing an example of the display format of the list of detailed information. In Figure 25, display area 150B is an example of a selection screen displayed on the buyer terminal 300 when multiple purchase order information is identified in step S2001 of Figure 20, and when matched invoice information exists in step S2002.

[0313] In step S2002, if there is matching invoice information, specifically, it means that the invoice image data displayed in display area 132 is the invoice image data for an installment payment invoice.

[0314] In the example in Figure 25, the invoice identified by invoice number "30126" and the invoice identified by invoice number "30127" are installment payment invoices associated with the purchase order identified by purchase order number "190186" (see Figure 5B). In addition, in the example in Figure 25, it is assumed that the invoice information identified by invoice number "30127" and the purchase order information identified by purchase order number "190186" have been matched.

[0315] In Figure 25, it is assumed that in both the invoice identified by invoice number "30126" and the invoice identified by invoice number "30127," the quantity of the product name "reception table" was 1.

[0316] Display area 150B includes display fields 151A, 152, etc., and each display field displays detailed information for each product name included in the order information, as well as the order number and issue date.

[0317] Furthermore, in display area 150B, if the itemized information included in the purchase order information has already been matched with the itemized information of other invoices, the invoice number and issue date that identify the other invoices, along with the result of the itemized information match, will be displayed.

[0318] In the example in Figure 25, the itemized information of the invoice identified by invoice number "30127," which includes the product name "reception table," and the itemized information of the purchase order identified by purchase order number "190186," which includes the product name "table," have already been matched.

[0319] Therefore, in display field 151A, the invoice number "30127", issue date, and matching result are displayed along with the itemized information including the product name "Table" in the order information.

[0320] Specifically, display field 151A includes display field 151-1. Display field 151-1 displays the invoice number "30127" of the invoice information that has been matched with the purchase order information identified by purchase order number "190186", and the issue date of the invoice identified by this invoice number, "2020 / 4 / 20".

[0321] Furthermore, display field 151-1 shows the number of items in the detail information containing the product name "Table" in the order information, and the number of items that have been successfully matched in the past, as a result of the matching. Display field 151-1 shows "1 / 2" for the number of items matched. Therefore, in the example in Figure 25, it can be seen that of the two items in the detail information containing the product name "Table" in the order information, one item has been successfully matched with the invoice information identified by invoice number "30127".

[0322] In this embodiment, when the invoice information to be matched is an installment payment invoice, the information identifying the installment payment invoice that has been previously matched with the purchase order information (invoice number and issue date), along with the match result, is displayed together with a list of the details of the purchase order information.

[0323] Therefore, according to this embodiment, if the invoice is an installment payment invoice, the user of the buyer terminal 300 can easily confirm the invoice information that has already been matched. Furthermore, in this embodiment, the user of the buyer terminal 300 can be aware of the progress of matching the installment payment invoice with the purchase order.

[0324] Furthermore, if the invoice is a split payment invoice, and the invoice information on the first split payment invoice is associated with the purchase order information, the number of items included in the details of the invoice information will not match the number of items in the purchase order information. Therefore, the result of matching the first split payment invoice with the purchase order will be "requires verification".

[0325] In this embodiment, if the document status of the first installment payment invoice is set to "Draft" or "Confirmed," the matching result between this installment payment invoice and the purchase order will not be changed unless manually modified by the user.

[0326] Furthermore, in this embodiment, when the invoice information of the second installment invoice is associated with the purchase order information, if the sum of the number of items included in the details information of this invoice information and the number of items included in the details information of the first installment invoice information matches the number of sales representatives included in the details information of the purchase order information, then the matching of these details information is considered successful.

[0327] In this embodiment, if the document status of the first installment payment invoice is "unprocessed," the matching result between the first installment payment invoice and the purchase order may be updated from "requires confirmation" to "successful."

[0328] Furthermore, if the document status of the first installment invoice is "Save as draft" or "Confirmed," the user can simply operate operation button 144-1 to instruct a rematch. When operation button 144-1 is operated on the buyer terminal 300, in this embodiment, with the second installment invoice and the purchase order already associated, the first installment invoice and the purchase order are matched again, and the match result is updated from "Requires confirmation" to "Successful."

[0329] Next, with reference to Figures 26 and 27, we will explain an example of how the buyer terminal 300 displays after the user (tenant) of the buyer terminal 300 has confirmed the matching results.

[0330] Figure 26 is the eighth figure showing an example of a buyer terminal display. The screen 131H shown in Figure 26 is an example of a screen that is displayed after the tenant has confirmed or re-matched the matching results displayed in the display area 144B in the screen 131D shown in Figure 18.

[0331] The screen 131H shown in Figure 26 includes display areas 132 and 133G, and operation buttons 28 and 29. In addition, tab 139 is selected in screen 131H.

[0332] Display area 133G includes display areas 134D, 135, 136, and 137B. Display area 134D also includes display areas 144F and 145.

[0333] In Figure 26, in display area 144F, checks are entered in the checkboxes associated with each detail item, indicating that the tenant has confirmed the information.

[0334] Furthermore, in the example shown in Figure 26, the display area 137B displays "Verified," indicating that the verification process for matching the detailed information has been completed.

[0335] Figure 27 is the ninth figure showing an example of a buyer terminal display. Screen 131I shown in Figure 27 is an example of a confirmation screen for invoice information for an invoice whose document status is "confirmed" and which has also been matched with the purchase order information.

[0336] The screen 131I shown in Figure 27 includes display areas 132 and 133H, and operation buttons 28 and 29. In screen 131I, tab 138 is selected. Display area 133H has display areas 134, 135, 136A, and 137A.

[0337] In the example in Figure 27, "Confirmed" is displayed in display area 136A, and "Successful" is displayed in display area 137A.

[0338] Therefore, it can be seen that the invoice image data displayed in the display area 132 is in a finalized state and that the matching with the corresponding purchase order has been successful.

[0339] In this embodiment, the document status and the progress of the matching process are displayed, making it easy for tenants to understand the status of invoice information and purchase order information.

[0340] Furthermore, 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 that accepts input of information to identify the purchase order information to be associated with the invoice information.

[0341] Furthermore, in this embodiment, if the order form or invoice is in paper format, document recognition is performed on the order form image data or invoice image data to obtain the order form information and invoice information.

[0342] Therefore, in this embodiment, even if the purchase order or invoice is in paper format, the person in charge of matching does not need to visually check the correspondence, and the correspondence between invoice information and purchase order information can be easily made.

[0343] In this embodiment, the transaction management device 200 is assumed to have a document recognition unit 264 that implements document recognition functionality, but it is not limited to this. The document recognition unit 264 may be provided outside the transaction management device 200. Another configuration of the transaction management system will be described below with reference to Figure 28.

[0344] Figure 28 shows another example of the system configuration of a transaction management system. The transaction management system 100A shown in Figure 21 includes a transaction management device 200A, a buyer terminal 300, and a document recognition device 500.

[0345] The transaction management device 200A includes a customer management database 210, a purchase order management database 220, an invoice management database 230, a matching management database 240, and a transaction management unit 260A.

[0346] Transaction management unit 260A is the same as transaction management unit 260, except that it does not have a document recognition unit 264. Document recognition device 500 has a document recognition unit 264.

[0347] In the transaction management system 100A, for example, when the transaction management device 200A receives document image data from the buyer terminal 300, it may transmit this document image data to the document recognition device 500 for document recognition. The transaction management device 200A may then receive the document information acquired through document recognition from the document recognition device 500.

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

[0349] Furthermore, each function of the embodiments described above can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute 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 execute each of the functions described above.

[0350] Furthermore, the apparatus described in the embodiments represents only one of several computing environments for carrying out the embodiments disclosed herein.

[0351] In one embodiment, the transaction management system 200 includes a plurality of computing devices, such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link, including a network or shared memory, and perform the processing disclosed herein. Similarly, the transaction management system 200 may include a plurality of computing devices configured to communicate with each other.

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

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

[0354] Here, machine learning is a technique for enabling computers to acquire human-like learning abilities. It refers to a technique in which a computer autonomously generates algorithms necessary for judgment, such as data identification, from pre-inputted training data, and applies these algorithms to new data to make predictions. The learning method for machine learning can be supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or deep learning, or a combination of these learning methods; the learning method for machine learning is not restricted.

[0355] Although the present invention has been described above based on various embodiments, the present invention is not limited to the requirements shown in the above embodiments. These points can be modified as long as they do not impair the spirit of the present invention, and can be appropriately determined according to their application. [Explanation of symbols]

[0356] 100, 100A Transaction Management System 200, 200A Transaction Management Device 210 Order Management Database 220 Order Management Database 230 Invoice Management Database 240 Matching Management Database 260 Transaction Management Department 263 Input Reception Section 264 Document Recognition Unit 265 Display Control Unit 266 Screen generation section 267 Storage Control Unit 268 Correspondence section 269 ​​Butt joint 240 Output section 300 Buyer terminals (terminal devices) 400 Seller terminals (terminal devices) [Prior art documents] [Patent Documents]

[0357] [Patent Document 1] Japanese Patent Application Publication No. 11-232306

Claims

1. An input receiving unit receives a change instruction from a terminal device to change the detail information included in the first report information that does not match the detail information included in the first report information, among the detail information included in the second report information associated with the first report information. A display control unit that, in response to a change instruction from the input receiving unit, displays a selection screen on the terminal device for selecting the detail information to be matched with the detail information whose matching result does not match from among the detail information included in the first report information, It has, The display control unit, Upon receiving the aforementioned change instruction, the terminal device displays an additional screen for adding detail information included in the first report information to be matched. An information processing device that, in the aforementioned additional screen, receives an operation to instruct the display of the selection screen, and displays the selection screen on the terminal device.

2. The information processing apparatus according to claim 1, further comprising a matching unit that matches the detail information selected in the selection screen with detail information for which the matching results do not match.

3. The display control unit, The information processing apparatus according to claim 1 or 2, which displays a list of detail information included in the first form information on the selection screen.

4. The display control unit, in the selection screen, The information processing apparatus according to claim 3, which displays a list of detail information included in the first report information in order of similarity between a specific string in the detail information included in the first report information and a specific string in the detail information for which the matching result does not match.

5. When multiple first document information items are associated with the second document information item, The display control unit, in the selection screen, The information processing apparatus according to claim 3 or 4, which displays a list of detail information contained in each of the multiple first report information items.

6. When a plurality of second report information is associated with the first report information, and among the plurality of second report information, there is a second report information for which the matching with the first report information has been completed, The display control unit, in the selection screen, An information processing device according to any one of claims 3 to 5, which displays a list of detail information contained in the first document information, information identifying the second document information for which matching with the first document information has been completed, and information indicating the result of the matching.

7. An information processing method using an information processing device, wherein the information processing device is For detail information contained in the second document information associated with the first document information, if the matching result with the detail information contained in the first document information does not match, the terminal device receives a change instruction to change the detail information contained in the first document information to be matched. In response to the change instruction, the terminal device is shown a selection screen for selecting the detail information to be matched with the detail information whose matching results do not match, from among the detail information included in the first report information. Upon receiving the aforementioned change instruction, the terminal device displays an additional screen for adding detail information included in the first report information to be matched. An information processing method that, in the additional screen, receives an operation to instruct the display of the selection screen, and displays the selection screen on the terminal device.

8. The aforementioned information processing device The information processing method according to claim 7, wherein the detail information selected on the selection screen is matched with the detail information for which the matching results do not match.

9. The aforementioned information processing device The information processing method according to claim 7 or 8, wherein a list of detail information included in the first form information is displayed on the selection screen.

10. The aforementioned information processing device In the aforementioned selection screen, The information processing method according to claim 9, which displays a list of detail information included in the first report information in order of similarity between a specific string in the detail information included in the first report information and a specific string in the detail information for which the matching result does not match.

11. When multiple first document information items are associated with the second document information item, The aforementioned information processing device In the aforementioned selection screen, The information processing method according to claim 9 or 10, which displays a list of detail information contained in the first report information for each of the multiple first report information items.

12. When a plurality of second report information is associated with the first report information, and among the plurality of second report information, there is a second report information for which the matching with the first report information has been completed, The aforementioned information processing device In the aforementioned selection screen, The information processing method according to any one of claims 9 to 11, which displays a list of detail information contained in the first report information, information identifying the second report information for which matching with the first report information has been completed, and information indicating the result of the matching.

13. For detail information contained in the second report information associated with the first report information, if the matching result with the detail information contained in the first report information does not match, a change instruction is received to change the detail information contained in the first report information to be matched. In response to the aforementioned change instruction, the terminal device is shown a selection screen for selecting the detail information to be matched with the detail information whose matching results do not match, from among the detail information included in the first report information. Upon receiving the aforementioned change instruction, the terminal device displays an additional screen for adding detail information included in the first report information to be matched. A program that, in the aforementioned additional screen, receives an operation to instruct the display of the selection screen and causes the selection screen to be displayed on the terminal device. The program causes the information processing device to execute the process.

14. An information processing system in which terminal devices and information processing devices are connected via a network, The aforementioned information processing device is An input receiving unit receives a change instruction from the terminal device to change the detail information included in the first report information that does not match the detail information included in the first report information, among the detail information included in the second report information associated with the first report information. A first display control unit, which, in response to a change instruction from the input receiving unit, displays a selection screen on the terminal device for selecting detail information to be matched with detail information whose matching results do not match from among the detail information included in the first report information, It has, The first display control unit, Upon receiving the aforementioned change instruction, the terminal device displays an additional screen for adding detail information included in the first report information to be matched. In the aforementioned additional screen, an operation to instruct the display of the selection screen is received, and the selection screen is displayed on the terminal device. The aforementioned terminal device is An operation receiving unit that receives an operation to send the aforementioned change instruction to the information processing device, An information processing system comprising: a second display control unit that causes the aforementioned selection screen to be displayed on a display device.

Images