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

Abstract

To make it easier to associate business forms to each other.SOLUTION: An information processing device is provided, comprising a display control unit configured to display on a terminal device a reception screen for receiving an input of information for identifying first business form information to be associated with second business form information from the first business form information stored in a storage unit, and an association unit for associating the second business form information with the first business form information identified based on the information for identifying the first business form information.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

[0002] Conventionally, when matching two documents, a technique is known in which documents having similar visual layouts are matched together. Summary of the Invention [Problem to be solved by the invention]

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

[0004] The disclosed technology aims to more easily associate forms with each other. [Means for solving the problem]

[0005] The disclosed technology includes a display control unit that displays on a terminal device a reception screen that receives input of information that identifies first form information to be associated with second form information from among the first form information stored in a storage unit, and an association unit that associates the first form information identified based on the identifying information with the second form information. the reception screen is a screen for receiving input of search conditions for the first form information to be associated with the second form information, and includes an area for displaying the second form information and an area for receiving input of the search conditions, and the association unit associates the first form information identified based on the results of searching the storage unit using the search conditions with the second form information; It is an information processing device. [Effects of the Invention]

[0006] Forms can be more easily associated with each other. [Brief explanation of the drawings]

[0007] [Figure 1]A figure showing an example of the system configuration of a transaction management system of the first embodiment. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a transaction management device. [Figure 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 10 is a diagram illustrating an example of an order destination management database. [Figure 5] FIG. 10 is a diagram illustrating an example of an order form management database. [Figure 6] FIG. 10 is a diagram illustrating an example of an invoice management database. [Figure 7] FIG. 10 is a diagram illustrating an example of a matching management database. [Figure 8] FIG. 2 is a diagram explaining the functions of each device included in the transaction management system. [Figure 9] This is a first sequence diagram explaining the operation of the transaction management system. [Figure 10] 10 is a first flowchart illustrating the processing of the transaction management device. [Figure 11] FIG. 10 is a diagram illustrating an example of a confirmation screen for order form information. [Figure 12] 10 is a second flowchart illustrating the processing of the transaction management device. [Figure 13] FIG. 10 is a diagram showing an example of a confirmation screen for invoice information. [Figure 14] This is a second sequence diagram explaining the operation of the transaction management system. [Figure 15] FIG. 10 is a first diagram showing an example of a display on a buyer terminal. [Figure 16] FIG. 10 is a second diagram showing an example of a display on the buyer terminal. [Figure 17] FIG. 10 is a third diagram showing an example of a display on a buyer terminal. [Figure 18] FIG. 4 is a fourth diagram showing an example of a display on a buyer terminal. [Figure 19] FIG. 5 is a fifth diagram showing an example of a display on a buyer terminal. [Figure 20] FIG. 6 is a sixth diagram showing an example of a display on a buyer terminal. [Figure 21]FIG. 10 is a diagram illustrating another example of the system configuration of a transaction management system. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

[0011] In the following description, the report information input from the terminal device 300 is referred to as first report information, a report including the first report information is referred to as the first report, and report image data including the first report information is referred to as the first report image data.

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

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

[0014] In this manner, in this embodiment, the input of second form information is accepted, and a screen for selecting first form information corresponding to the second form information is displayed, thereby associating the first form with the second form. Therefore, in this embodiment, tasks such as visually checking the form information of the two forms are not required, and the forms can be easily associated. Furthermore, since the correspondence between forms is easy in this embodiment, the workload of the matching work can be reduced.

[0015] The terminal device 300 in this embodiment is a terminal device that is mainly used by an order source that places an order via the transaction management device 200. In other words, the terminal device 300 is a terminal device that is used by a buyer that purchases a product or the like. In the following description, the terminal device 300 may be referred to as a buyer terminal 300.

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

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

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

[0019] In the following description, an order form is an example of a first form, and an invoice is an example of a second form.

[0020] Furthermore, the terminal device 300 in this embodiment is a terminal device that is mainly used by an order source that places an order via the transaction management device 200. In other words, the terminal device 300 is a terminal device that is used by a buyer that purchases a product or the like. In the following description, the terminal device 300 may be referred to as a buyer terminal 300.

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

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

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

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

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

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

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

[0028] In this embodiment, the invoice management information is information for managing invoice information, and includes invoice information. In this embodiment, the invoice information is information extracted from an invoice that a buyer receives from a seller, and an invoice in this embodiment is issued by a seller in response to a purchase order issued by a buyer and given to the buyer.

[0029] The invoice information may be obtained by executing a form recognition process on the invoice image data in the transaction management device 200. Alternatively, the invoice information may be obtained as a result of an OCR process performed by an image forming device or the like.

[0030] The matching management database 240 stores information indicating the results of matching order information with invoice information.

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

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

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

[0034] The matching process involves checking the contents of an order against the contents of the corresponding order to see if they match.

[0035] 1, order destination management database 210, purchase order management database 220, invoice management database 230, and matching management database 240 are provided in transaction management device 200, but this is not limiting. Some or all of these databases may be provided in other devices. Transaction management device 200 may also be realized by multiple information processing devices.

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

[0037] Figure 2 shows an example of the hardware configuration of a transaction management device. Transaction management device 200 is constructed by a computer, and as shown in Figure 2, includes 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.

[0038] Of these, the CPU 201 controls the overall operation of the transaction management device 200. The ROM 202 stores programs used to drive the CPU 201, such as an IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data, such as programs. The HDD controller 205 controls the reading and writing of various data from and to the HD 204 under the control of the CPU 201. The display 206 displays various information, such as a cursor, menu, window, text, or image. The external device connection I / F 208 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and a printer. 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 FIG. 2.

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

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

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

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

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

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

[0045] Of these, the long-distance communication circuit 312 is a circuit that communicates with other devices via a communication network. The CMOS sensor 313 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 301. The image sensor I / F 314 is a circuit that controls the driving of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts an electrical signal into physical vibrations to produce sound such as music or voice. The sound input / output I / F 317 is a circuit that processes the input and output of sound signals between the microphone 315 and the speaker 316 under the control of the CPU 301.

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

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

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

[0049] The order destination management database 210 of this embodiment is provided for each tenant, for example. The order destination management database 210 of this embodiment includes information items such as name, address, telephone number, email address, and name of person in charge, and these items are associated with tenant IDs (tenant identification information) and tenant names.

[0050] In this embodiment, information including values ​​of items such as name, address, telephone number, email address, and person in charge in the order destination management database 210 may be expressed as order destination information. The tenant ID and tenant name are information for identifying a tenant. The value of the item "name" indicates the name of the business partner (billing destination), and the values ​​of the items "address," "telephone number," "email address," and "person in charge" respectively indicate the address, telephone number, email address, and name of the person in charge of the transaction of the billing destination.

[0051] It should be noted that the information items included in the order destination information are not limited to the example shown in Fig. 4. The information items included in the order destination information do not have to include all the items shown in Fig. 4, and may include items other than the items shown in Fig. 4.

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

[0053] 5 is a diagram showing an example of the order form management database 220. Like the order destination management database 210, the order form management database 220 of this embodiment may be provided for each tenant.

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

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

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

[0057] The value of the item "Order Form Number" is form identification information for identifying the order form, order form information, and order form management information. In other words, the value of the item "Order Form Number" is identification information for identifying the first form information.

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

[0059] In this embodiment, when a value for the item "corresponding invoice information" is stored in the order form management database 220, it indicates that the order form information and invoice information have been associated with each other.

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

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

[0062] The values ​​of the items "total amount" and "order date" indicate the total amount and order date written on the order form, respectively.

[0063] The value of the item "Form Status" indicates the progress of the form recognition. In this embodiment, the value of the item "Form Status" includes four states: unprocessed, saved as draft, confirmed, and externally output. Each state is as follows:

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

[0065] Draft saved state (state 2) This is the state when the document information is being checked, etc., and the document management information (order form management information, invoice management information) has not yet been finalized.

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

[0067] The value of the item "information status" indicates the status of the form information (order form information, invoice information) in the transaction management system 100. Specifically, the status of the form information includes the following four states.

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

[0069] Draft saved state (state 2) This is the state when the document information is being checked, etc., and the contents of the document information (order form information, invoice information) have not yet been finalized.

[0070] Confirmed state (state 3): The state in which the confirmation of the ledger information and other tasks have been completed and the ledger information (order form information, invoice information) has been confirmed.

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

[0072] The value of the item "Form Image Path" indicates the storage location of the order form image data.

[0073] The item "detail information" may be associated with items that indicate the breakdown of the order amount, such as items "product code," "product name," and "quantity."

[0074] It should be noted that the information items included in the purchase order management information are not limited to the example shown in Fig. 5. The information items included in the purchase order management information do not have to include all of the items shown in Fig. 5, and may include items other than those shown in Fig. 5.

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

[0076] In the following description, information including the items "biller" and "billing number" in the billing management database 230 and values ​​of other items will be referred to as billing management information.

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

[0078] The value of the item "biller" indicates the name of the tenant that has made the bill. In other words, the value of the item "biller" indicates the name of the tenant that has created the invoice information.

[0079] The value of the item "invoice number" is identification information for identifying the invoice, invoice information, and invoice management information. In other words, the value of the item "invoice number" is identification information for identifying the second form information.

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

[0081] In this embodiment, when a value for the item "corresponding order form information" is stored in the invoice management database 230, it indicates that the association between the invoice information and the order form information has been completed.

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

[0083] The value of the item "Total Amount" indicates the total amount of the invoice. The value of the item "Issuance Date" indicates the date on which the invoice identified by the invoice number was issued.

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

[0085] It should be noted that the information items included in the invoice information are not limited to the example shown in Fig. 6. The information items included in the invoice information do not have to include all the items shown in Fig. 6, and may include items other than the items shown in Fig. 6.

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

[0087] The matching management database 240 contains information items such as purchase order number, processing date and time, total amount, and detailed information, and the item "purchase order number" is associated with the other items.

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

[0089] The item "detailed information" is associated with items that indicate the breakdown of the total amount, such as items "product code," "product name," "quantity," etc. In the matching management database 240, the values ​​of these items indicate the results of matching detailed information included in the invoice information and detailed information included in the order form information that have matching product names.

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

[0091] In this embodiment, a case where the matching result is a match may be expressed as "success", and a case where the matching result is a mismatch may be expressed as "confirmation required".

[0092] It should be noted that the information items included in the matching management database 240 are not limited to the example shown in Fig. 7. The information items included in the matching management database 240 do not have to include all the items shown in Fig. 7, and may include items other than the items shown in Fig. 7.

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

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

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

[0096] The form recognition unit 264 extracts form information from the form image data. Specifically, the form recognition unit 264 performs character recognition processing on the form image data to obtain text data, extracts items and item values ​​included in the form image from the obtained text data, and sets the information in which the items and item values ​​are associated as form information. In the following description, extracting items and their item values ​​included in the form image and converting the items and item values ​​into text data and associating them is referred to as form recognition.

[0097] In this embodiment, when the input receiving unit 263 receives input of invoice image data, the form recognition unit 264 acquires invoice information from the invoice image data. Also, in this embodiment, when the input receiving unit 263 receives input of order form image data, the form recognition unit 264 acquires order form information from the order form image data.

[0098] Display control unit 265 controls the display on buyer terminal 300. Display control unit 265 may also control the display on seller terminal 400. Storage control unit 266 updates each database in accordance with the processing of transaction management unit 260.

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

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

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

[0102] Next, the functions of buyer terminal 300 will be described. Buyer terminal 300 of this embodiment has a display unit 330 and a communication unit 340. Display unit 330 displays information on the display of buyer terminal 300. Communication unit 340 transmits and receives information between buyer terminal 300 and other devices.

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

[0104] Figure 9 is a first sequence diagram illustrating the operation of the transaction management system. Figure 9 shows the operation from step S901 to step S908 of transaction management system 100 until the order form information of the purchase order issued by the buyer is stored in order form management database 220. FIG. 9 also shows the operations from step S909 to step S917 in transaction management system 100 until invoice information of an invoice received by a buyer from a seller is stored in invoice management database 230.

[0105] The operation of storing the order form information in the order form management database 220 and the operation of storing the invoice information in the invoice management database 230 may be performed at independent times.

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

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

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

[0109] Next, transaction management apparatus 200 causes display control unit 265 to send an instruction to buyer terminal 300 to display a confirmation screen for confirming the purchase order information (step S904).

[0110] The buyer terminal 300 receives the instruction to display the confirmation screen, and causes the display unit 330 to display the confirmation screen for the order form information (step S905).

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

[0112] In response to this request, the transaction management device 200 causes the storage control unit 266 to confirm the status of the order form information stored in the order form management database 220 in step S903 (step S908). Specifically, the storage control unit 266 sets the values ​​of the items "document status" and "information status" in the order form management information including the order form information stored in the order form management database 220 to "confirmed."

[0113] The above is the operation for storing order form information in order form management database 220. Next, the operation for storing invoice information in invoice management database 230 will be described.

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

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

[0116] Next, transaction management apparatus 200 causes display control unit 265 to send an instruction to buyer terminal 300 to display a confirmation screen for confirming the invoice information (step S913).

[0117] The buyer terminal 300 receives the instruction to display the confirmation screen, and causes the display unit 330 to display the confirmation screen for the invoice information (step S914).

[0118] Next, when buyer terminal 300 receives an operation from the tenant instructing confirmation of the invoice information (step S915), buyer terminal 300 transmits a request to transaction management apparatus 200 to confirm the invoice information (step S916).

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

[0120] The above is the operation for storing invoice information in the invoice management database 230. Next, the processing of the storage control unit 266 will be described.

[0121] 10 is a first flowchart illustrating the processing of the transaction management device, showing details of the processing of the storage control unit 266 that stores the order form information in the order form management database 220 in step S903 of FIG.

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

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

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

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

[0126] In step S1002, if the order form is a paper medium, the transaction management device 200 causes the form recognition unit 264 to perform form recognition on the order form image data, and extracts the order form information from the order form image data (step S1003).

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

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

[0129] A screen 111 shown in FIG. 11 includes display areas 112, 113, and 114, and operation buttons 26 and 27.

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

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

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

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

[0134] 12 is a second flowchart illustrating the processing of the transaction management device, showing details of the processing of the storage control unit 266 that stores invoice information in the invoice management database 230 in step S912 of FIG.

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

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

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

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

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

[0140] The billing information may also be billing information created using another application.

[0141] In step S1202, if the invoice is a paper medium, the transaction management device 200 causes the form recognition unit 264 to perform form recognition on the invoice image data, and extracts the order form information from the invoice image data (step S1203).

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

[0143] If there is no corresponding order form information in step S1204, transaction management device 200 proceeds to step S1206, which will be described later.

[0144] In step S1204, if there is corresponding order form information, transaction management device 200 causes association unit 267 to associate the invoice information with the order form information (step S1205).

[0145] Specifically, the transaction management device 200 uses the association unit 267 to identify purchase order information stored in the purchase order management database 220 whose purchase order number value matches the corresponding purchase order number assigned to the invoice information. Then, the transaction management device 200 uses the storage control unit 266 to set the value of the "corresponding invoice number" item in the purchase order management information including the identified purchase order information to the invoice number included in the invoice information.

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

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

[0148] Next, the invoice information confirmation screen of this embodiment will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of the invoice information confirmation screen. Note that the example of Fig. 13 may be an example of the invoice information confirmation screen when the invoice is on paper.

[0149] A screen 131 shown in FIG. 13 includes display areas 132 and 133 and operation buttons 28 and 29.

[0150] In the display area 132, the bill image data is displayed.

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

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

[0153] Input fields for journal information for an invoice, etc. are displayed in the display area 135. In this embodiment, after the operation button 140 is operated to confirm the invoice information, input of journal information, etc. can be performed.

[0154] The form status of the invoice is displayed in display area 136. In the example of Fig. 13, "Unprocessed" is displayed in display area 136, which indicates that the status of the invoice has not been determined.

[0155] The progress of the matching is displayed in display area 137. In the example of Fig. 13, "Confirmation Required" is displayed in display area 137, which indicates that the matching results have not yet been confirmed.

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

[0157] In this embodiment, when the bill information confirmation screen is displayed, the screen is displayed with tab 138 selected.

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

[0159] Next, with reference to FIG. 14, the matching of order form information and invoice information in this embodiment will be described.

[0160] 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 matching (step S1401). Specifically, when the buyer terminal 300 receives the selection of a tab on the invoice information confirmation screen to display the matching results with the purchase order information, it is deemed to have received the operation to instruct matching.

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

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

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

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

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

[0166] Note that checking refers to checking the order details in the purchase order information against the billing details in the invoice information to see if the order details and the order details match.

[0167] Upon receiving the information indicating the matching result and the display instruction, the buyer terminal 300 displays the matching result on the display unit 330 (step S1406).

[0168] The following processing from step S1407 to step S1423 is performed when it is determined in step S1403 that there is no purchase order information to be matched.

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

[0170] Upon receiving this display instruction, buyer terminal 300 displays a search screen for purchase order information on display unit 330 (step S1408). Next, when a tenant or the like inputs search conditions for purchase order information (step S1409), buyer terminal 300 transmits a search request to transaction management device 200 (step S1410).

[0171] When transaction management device 200 receives the search request, association unit 267 searches order form management database 220 using the search conditions (step S1411).

[0172] At this time, the association unit 267 searches the order form management database 220 for order form information that matches the search conditions from the order form information whose value in the item "information status" is "confirmed."

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

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

[0175] In this way, the search screen displayed in step S1408 is an example of a reception screen that receives the selection of invoice information and corresponding purchase order information.

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

[0177] At this time, the transaction management device 200 causes the storage control unit 266 to store the matching results in the order form management database 220, the invoice management database 230, and the matching management database 240, respectively.

[0178] Specifically, the storage control unit 266 stores information indicating the results of matching on a form-by-form basis, i.e., an invoice and an order form, as the value of the item "confirmation status" in the order form management database 220 and the invoice management database 230. For example, if the matching between the forms is successful, the storage control unit 266 sets the value of the item "confirmation status" to "success," and if the matching between the forms is unsuccessful, the storage control unit 266 sets the value of the item "confirmation status" to "confirmation required." Details regarding success and failure of matching on a form-by-form basis will be described later.

[0179] The storage control unit 266 also stores the matching results for each detailed information unit included in the invoice information and the order form information in the matching management database 240. Details regarding success and failure of matching for each detailed information unit will be described later.

[0180] Upon receiving the information indicating the matching result, the buyer terminal 300 displays this information (step S1415).

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

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

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

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

[0185] When the input receiving unit 263 of the transaction management device 200 receives a notification specifying the order form information, the associating unit 267 associates the specified order form information with the invoice information (step S1420).

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

[0187] Next, transaction management device 200 causes output unit 269 to transmit information indicating the matching result and an instruction to display this information to buyer terminal 300 (step S1422).

[0188] Upon receiving the information indicating the matching result and the display instruction, the buyer terminal 300 causes the display unit 330 to display the information indicating the matching result (step S1423).

[0189] In this manner, in this embodiment, if the invoice information and the order form information are not matched before receiving a matching instruction, a matching screen for matching the invoice information and the order form information is displayed on the buyer terminal 300.

[0190] Furthermore, the only purchase order information displayed on the matching screen is that whose information status is confirmed. Therefore, in this embodiment, purchase order information that may be changed in the future can be prevented from being selected as a matching target. In other words, in this embodiment, form information that has not been confirmed can be prevented from being selected as a matching target.

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

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

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

[0194] 15 includes display areas 132, 133A, and operation buttons 28, 29. Invoice image data is displayed in the display area 132.

[0195] Display area 133A has display areas 134A, 135, 136, and 137, and display area 134A includes input fields 141 and 142, an operation button 143, and a display area.

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

[0197] Therefore, the screen 131A of this embodiment can be said to be an example of a reception screen that receives input of information for identifying purchase order information that is to be associated with invoice information.

[0198] 15, the search conditions are the purchase order number and the import date and time, but are not limited to this. In this embodiment, the items to be input as search conditions can be changed arbitrarily by the tenant's operation.

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

[0200] The display area 144 is a display area for displaying the matching results. In the example of Fig. 15, the order form information to be matched has not been specified, so the display area 144 is blank.

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

[0202] Specifically, a screen 131B shown in FIG. 16 is an example of a screen displayed on the buyer terminal 300 in step S1415 of FIG.

[0203] 16 includes display areas 132 and 133B and operation buttons 28 and 29. On screen 131B, tab 139 is in a selected state.

[0204] Display area 133B has display areas 134B, 135, 136, and 137A, and information showing the matching result is displayed in display area 134B.

[0205] Specifically, the order number and the import date and time entered as search conditions in input fields 141 and 142 are displayed in display area 134B.

[0206] Display area 134B also has display area 144A. Display area 144A displays the detailed information of the order form information identified by the order form number entered in input field 141 and the results of matching each detailed information with the detailed information included in the invoice information.

[0207] In display area 144A, a notification that "matching successful" is displayed for all of the detailed information included in the order form information, indicating that the detailed information included in the invoice information matches.

[0208] Here, the success and failure of matching of detail information units will be explained.

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

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

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

[0212] Next, the success and failure of matching on a form-by-form basis will be explained.

[0213] In this embodiment, if the matching results for all of the detailed information are "successful," the progress status of the matching between the forms displayed in the display area 137A will be "successful." Also, in this embodiment, if the matching results for all of the detailed information include even one item that is "confirmation required," the progress status of the matching between the forms will also be "confirmation required."

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

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

[0216] The screen 131C includes a display area 170. In the display area 170, a list of the order form information extracted as the search results and operation buttons 171 are displayed.

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

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

[0219] If the match is successful, a screen with the same layout as the screen shown in FIG. 16 is displayed.

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

[0221] 18 includes display areas 132 and 133C and operation buttons 28 and 29. Furthermore, on screen 131D, tab 139 is in a selected state.

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

[0223] The order form number and the import date and time, which are search conditions, are displayed in the display area 145. The display area 145 also displays detailed information about the order form information for each product name.

[0224] Display area 144B displays the results of matching the detailed information of the invoice information with the detailed information of the order form information for each item of detailed information.

[0225] In this embodiment, for example, the display area 144B may display detail information corresponding to the product name that does not match the details of the invoice information, among the detail information of the order form information.

[0226] In addition, the display area 144B displays a notification "Confirmation Required" for each item of detailed information, indicating that the tenant needs to confirm the contents. In addition, the display area 144B displays a check box associated with each item of detailed information. This check box is checked when the tenant or the like confirms the matching results of the corresponding item of detailed information.

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

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

[0229] 19 includes display areas 132 and 133D and operation buttons 28 and 29. Furthermore, on screen 131E, tab 139 is in a selected state.

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

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

[0232] In the example of FIG. 19, the display area 137B displays "Confirmed," indicating that the confirmation of the result of matching the detailed information has been completed.

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

[0234] 20 includes display areas 132 and 133E and operation buttons 28 and 29. Furthermore, tab 138 is in a selected state on screen 131F. Display area 133E has display areas 134, 135, 136A, and 137A.

[0235] In the example of FIG. 20, "Confirmed" is displayed in display area 136A, and "Success" is displayed in display area 137A.

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

[0237] In this manner, in this embodiment, the form status and the progress of the reconciliation are displayed, so that the tenant can easily grasp the status of the invoice information and the purchase order information.

[0238] Furthermore, in this embodiment, if the invoice information and the purchase order information are not associated with each other, the buyer terminal 300 displays a reception screen for receiving input of information specifying the purchase order information to be associated with the invoice information.

[0239] In this embodiment, when an order form or invoice is on paper media, form recognition is performed on the order form image data or invoice image data to obtain order form information and invoice information.

[0240] Therefore, in this embodiment, even if the order form or invoice is on paper, the person in charge of the matching work does not need to perform tasks such as visually checking the correspondence, and the invoice information can be easily matched with the order form information.

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

[0242] 21 is a diagram showing another example of the system configuration of a transaction management system. Transaction management system 100A shown in FIG. 21 includes transaction management device 200A, buyer terminal 300, and document recognition device 500.

[0243] Transaction management device 200A has order destination management database 210, order form management database 220, invoice management database 230, matching management database 240, and transaction management section 260A.

[0244] The transaction management unit 260A is similar to the transaction management unit 260 except that it does not have the form recognition unit 264. The form recognition device 500 has the form recognition unit 264.

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

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

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

[0248] Additionally, the devices described in the embodiments are merely representative of one of several computing environments for implementing the embodiments disclosed herein.

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

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

[0251] The tables in the statement may be generated by machine learning. Also, by classifying keywords and items that may be included in the transaction details using machine learning, it is possible to eliminate the need for a correspondence table.

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

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

[0254] 100, 100A trading management system 200, 200A Transaction Management Device 210 Order Management Database 220 Order Management Database 230 Invoice Management Database 240 Reconciliation Management Database 260 Transaction Management Department 263 Input Reception Unit 264 Document Recognition Unit 265 Display control unit 266 Storage control unit 267 Mapping Section 268 Butt joint 269 ​​Output Section 300 Buyer terminal (terminal device) 400 Seller terminal (terminal device) [Prior art documents] [Patent documents]

[0255] [Patent Document 1] Special Announcement No. 11-232306

Claims

1. a display control unit that displays, on the terminal device, a reception screen that receives input of information that identifies the first form information to be associated with the second form information from the first form information stored in the storage unit; a correlation unit that correlates the first form information identified based on the identifying information with the second form information, The reception screen is a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions; The association unit The information processing device associates the first form information identified based on the result of searching the storage unit using the search conditions with the second form information.

2. The display control unit When there are a plurality of pieces of the specified first form information, a selection screen including the plurality of pieces of the specified first form information is displayed on the terminal device; The association unit 2. The information processing apparatus according to claim 1, wherein the first form information selected on the selection screen is associated with the second form information.

3. a matching unit that matches first form information associated with the second form information with the second form information; The information processing apparatus according to claim 1 or 2, wherein the display control unit causes the terminal device to display information indicating a result of the matching performed by the matching unit.

4. The display control unit 4. The information processing apparatus according to claim 3, wherein information indicating the result of the matching is displayed on the terminal device together with the first form information and second form image data including the second form information.

5. The association unit When a request for registration of the second form information is received, it is determined whether or not first form information that can be associated with the second form information exists, and if it is determined that first form information exists, it associates the first form information with the second form information; The display control unit An information processing device as described in claim 3, which accepts a request to display information indicating the results of the matching by the matching unit, and displays the reception screen on the terminal device if there is no first report information corresponding to the second report information.

6. The determination by the association unit is An information processing device as described in claim 5, wherein the second report information is created using an application provided by the information processing device, and the process is performed depending on whether or not identification information identifying the first report information is assigned to the second report information.

7. The information processing apparatus according to claim 1 , wherein the search based on the search condition is performed only on first form information whose state has been confirmed in the storage unit.

8. An information processing method by an information processing device, the information processing device comprising: displaying on the terminal device a reception screen for receiving input of information for identifying the first form information to be associated with the second form information from the first form information stored in the storage unit; Correlating the first form information identified based on the identifying information with the second form information; The reception screen is a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions; The association is An information processing method for associating first form information identified based on a result of searching the storage unit using the search conditions with second form information.

9. The information processing device, When there are a plurality of pieces of the specified first form information, a selection screen including the plurality of pieces of the specified first form information is displayed on the terminal device; 9. The information processing method according to claim 8, wherein the first form information selected on the selection screen is associated with the second form information.

10. The information processing device, comparing first form information associated with the second form information with the second form information; 10. The information processing method according to claim 8, wherein information indicating the result of the matching is displayed on the terminal device.

11. The information processing device, 11. The information processing method according to claim 10, wherein information indicating the result of the matching is displayed on the terminal device together with the first form information and second form image data including the second form information.

12. 12. The information processing method according to claim 11, wherein the search based on the search condition is performed only on the first form information whose state has been confirmed in the storage unit.

13. displaying on the terminal device a reception screen for receiving input of information for identifying the first form information to be associated with the second form information from the first form information stored in the storage unit; Correlating the first form information identified based on the identifying information with the second form information; The reception screen is a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions; The association is A program that causes an information processing device to execute a process of associating first form information identified based on the results of searching the storage unit using the search conditions with second form information.

14. An information processing system including an information processing device and a terminal device, The information processing device includes: a display control unit that displays, on the terminal device, a reception screen that receives input of information that identifies first form information to be associated with second form information from the first form information stored in the storage unit; a correlation unit that correlates the first form information identified based on the identifying information with the second form information, The reception screen is a screen for receiving input of search conditions for the first form information to be associated with the second form information, the screen including an area for displaying the second form information and an area for receiving input of the search conditions; The association unit associates the first form information identified based on the result of searching the storage unit using the search conditions with the second form information; The terminal device An information processing system having a display unit that displays the reception screen.

Images