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

Abstract

To allow for easily associating related business documents with each other.SOLUTION: An information processing device is provided, comprising: a generation unit configured to generate transmission guidance information corresponding to a second business document issued for a first business document; and a registration unit configured to register, in a storage unit, information representing the second business document transmitted according to the transmission guidance information in association with information on the first business document included in first business document image data.SELECTED DRAWING: Figure 13

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] There has been known an order management system including a buyer device, a seller device, and a management device that manages order transactions between the buyer device and the seller device. As one of the order processing workflows performed on the buyer side, there has also been known a matching operation that verifies whether the contents of an order (purchase order) made by a buyer match the contents of an order (invoice) received from a seller. Summary of the Invention [Problem to be solved by the invention]

[0003] In the conventional technology described above, the contents of the order and the contents of the order are associated in the management device, making it easy to match them up. However, in the conventional technology, if the buyer's device and the seller's device are not included in the same system, it becomes difficult to associate the purchase order and the invoice.

[0004] In this way, in the past, if the issuers of multiple documents that are related to each other and that are expected to be reconciled, such as purchase orders and invoices, were not included in the same system, it was difficult to match the related documents together, and the reconciliation process became complicated.

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

[0006] The disclosed technology is an information processing device that communicates with a first terminal device and a second terminal device, and that responds to a second form issued in response to a first form including first form information input from the first terminal device: Indicates the destination of the second form Sending information In response to the transmission method of the second form designated in the first terminal device, a generating unit that generates the transmission guide information and identification information that identifies the first form; 、 a storage unit that stores the above in association with each other; an output unit that outputs the generated transmission guide information; Based on the transmission guide information, the second terminal device To the destination indicated by the transmission guide information Information indicating the second form that has been sent; 、 Identification information for identifying the first form; 、 and a registration unit that associates the information with the information stored in the storage unit. [Effects of the Invention]

[0007] Related documents can be easily associated with each other. [Brief explanation of the drawings]

[0008] [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. 2 illustrates an example of an order destination management database according to the first embodiment. [Figure 5] FIG. 2 illustrates an example of an order form database according to the first embodiment. [Figure 6] FIG. 2 illustrates an example of a storage management database according to the first embodiment; [Figure 7] FIG. 10 is a diagram illustrating another example of the storage management database according to the first embodiment. [Figure 8] FIG. 2 illustrates an example of a matching management database according to the first embodiment; [Figure 9] A diagram explaining the functions of each device included in the transaction management system of the first embodiment. [Figure 10] This is a first sequence diagram explaining the operation of the transaction management system of the first embodiment. [Figure 11]A second sequence diagram explaining the operation of the transaction management system of the first embodiment. [Figure 12] FIG. 10 is a diagram illustrating the creation of an order form. [Figure 13] FIG. 10 is a first diagram illustrating uploading of an invoice. [Figure 14] FIG. 10 is a second diagram illustrating uploading of an invoice. [Figure 15] FIG. 10 illustrates an example of a list screen according to the first embodiment; [Figure 16] FIG. 10 is a diagram illustrating an example of a matching screen according to the first embodiment. [Figure 17] A figure showing an example of the system configuration of a transaction management system of the second embodiment. [Figure 18] FIG. 10 illustrates an example of a history management database according to the second embodiment; [Figure 19] FIG. 11 illustrates an example of an invoice database according to the second embodiment. [Figure 20] FIG. 10 is a diagram illustrating the functions of a transaction management device according to a second embodiment. [Figure 21] A sequence diagram explaining the operation of the transaction management system of the second embodiment. [Figure 22] 10 is a flowchart illustrating a process of a matching management unit according to the second embodiment. [Figure 23] FIG. 11 is a first diagram illustrating an example of a list screen according to the second embodiment. [Figure 24] FIG. 11 is a first diagram illustrating an example of a matching screen according to the second embodiment. [Figure 25] FIG. 11 is a second diagram illustrating an example of the list screen according to the second embodiment. [Figure 26] FIG. 11 is a second diagram illustrating an example of the matching screen according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] (First embodiment) The first embodiment will be described below with reference to the drawings. Fig. 1 is a diagram showing an example of the system configuration of a transaction management system according to the first embodiment.

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

[0011] The transaction management device 200 of this embodiment creates form image data of a form based on form information input from the terminal device 300. Furthermore, when the transaction management device 200 acquires form image data of a form issued for this form from the terminal device 400, it manages the form image data created based on the form information input from the terminal device 300 and the form image data acquired from the terminal device 400 in association with each other.

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

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

[0014] When outputting the first form image data, the transaction management device 200 of this embodiment also outputs transmission guidance information for transmitting the second form image data from the terminal device 400.

[0015] The transmission guidance information in this embodiment is information generated according to the second form, and is information regarding the transmission of the second form that is notified to the sender of the second form. Specifically, for example, the transmission guidance information is information generated according to the transmission method of the second form image data. Examples of transmission guidance information include the address of the transmission screen used to transmit the second form and information indicating the destination of the second form. Furthermore, the transmission guidance information is information generated according to the transmission method of the second form image data, and is information associated with the storage destination (memory area) of the second form image data.

[0016] Then, when the transaction management device 200 receives the second form image data sent from the terminal device 400 based on the transmission guidance information, it associates the received second form image data with the first form information and stores it in the memory unit.

[0017] In this embodiment, this allows the second report image data obtained from an external device of the transaction management system 100 to be automatically associated with the first report information generated within the transaction management system 100.

[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 who purchases a product or the like. In the following description, the terminal device 300 may be referred to as a buyer's terminal 300.

[0021] In this embodiment, the order source is, for example, a business that places an order with various ordering destinations. In this embodiment, the business may be an individual or an organization such as a company or corporation. In the following description of the embodiment, the 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 seller terminal 400.

[0023] The transaction management device 200 of this embodiment includes an order destination management database 210 , an order form database 220 , a storage 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 database 220 stores order form information indicating the contents of orders input from the buyer terminal 300.

[0025] The storage management database 230 stores identification information for specifying order form information and invoice image data in association with each other. The matching management database 240 stores information indicating the results of matching the order form information with the invoice image data.

[0026] The transaction management unit 260 outputs the order form information input from the buyer terminal 300 and transmission guidance information for transmitting the invoice image data. Specifically, the transaction management unit 260 may transmit the order form information and transmission guidance information to the buyer terminal 300, or may transmit the order form information and transmission guidance information to the seller terminal 400. The transaction management unit 260 may also output the order form information and transmission guidance information as printed matter.

[0027] In addition, when the transaction management unit 260 receives invoice image data sent from the seller terminal 400 based on the transmission guidance information, it associates the invoice image data with the order form information corresponding to the transmission guidance information and stores them in the storage management database 230.

[0028] In this embodiment, this configuration makes it possible to easily associate order form information with invoice image data. In other words, it makes it possible to easily associate related forms with each other. Furthermore, in this embodiment, since it is easy to associate related forms with each other, the burden of matching work is also reduced.

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

[0030] 1, the order destination management database 210, the order form database 220, the storage management database 230, the matching management database 240, and the history management database 250 are provided in the transaction management device 200, but this is not limiting. Some or all of these databases may be provided in other devices.

[0031] Transaction management device 200 may also be realized by a plurality of information processing devices. Next, the hardware configuration of transaction management device 200 of this embodiment will be described below.

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

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

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

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

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

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

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

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

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

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

[0042] 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 the order destination management database of the first embodiment.

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

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

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

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

[0047] 5 is a diagram showing an example of the order form database according to the first embodiment. The order form database 220 according to this embodiment may be provided for each tenant, similar to the order destination management database 210.

[0048] The order form database 220 includes information items such as order number, matching result, confirmation status, order destination, total amount, order date, desired delivery date, delivery location, document image path, and detailed information, and each item is associated with a tenant ID and tenant name.

[0049] Furthermore, the item "order form number" is associated with other items in the order form database 220. In this embodiment, information in the order form 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 information.

[0050] In this embodiment, when values ​​for the information items included in the order form image are input from the terminal device 400, an order form number is generated, and the order form information including the order form number is stored in the order form database 220. The information items included in the order form image include the order recipient, total amount, order date, desired delivery date, delivery location, and detailed information.

[0051] The value of the item "order form number" is form identification information for identifying the form (order form). In other words, the value of the item "order form number" is identification information for identifying the first form information.

[0052] The value of the "Matching result" field indicates the result of the matching between the tenant's order information and the invoice image. Specifically, if the value of the "Matching result" field is "○", it indicates that the order details and the invoice details match, and if the value is "×", it indicates that the order details and the invoice details do not match.

[0053] 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," this indicates that the buyer's visual matching work has been completed. Also, for example, if the value of the "Confirmation Status" item is "Unprocessed," this indicates that the buyer's visual matching work has not been performed, and if the value of the "Confirmation Status" item is "Unbilled," this indicates that the invoice image data corresponding to the purchase order information has not been received. A state in which the invoice image data has not been received means that the purchase order number and invoice image data are not associated in the storage management database 230.

[0054] The items "matching result" and "confirmation status" may be items of information stored in the matching management database 240, which will be described later.

[0055] The value of the "Orderer" field indicates the name of the orderer specified by the order number. The values ​​of the "Total Amount," "Order Date," and "Desired Delivery Date" fields indicate the total amount, order date, and desired delivery date, respectively, as stated on the order.

[0056] The value of the item "Delivery location" indicates the location where the ordered product will be delivered. The value of the item "Form image path" indicates the storage location of the order form image data.

[0057] The item "Detail Information" corresponds to items that indicate the breakdown of the order amount, such as the items "Product Code," "Product Name," and "Quantity," and the value of the item "Order Information" indicates the breakdown of the order amount.

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

[0059] Fig. 6 is a diagram showing an example of the storage management database according to the first embodiment. In the storage management database 230 shown in Fig. 6, the storage destination of the invoice image data indicated by the transmission guide information is indicated by a URL (Uniform Resource Locator).

[0060] The storage management database 230 of this embodiment has information items such as a URL, an order number, and invoice image data, and the order number is associated with the other items.

[0061] The value of the "URL" item indicates the storage location of the corresponding invoice image data. In other words, the value of the "URL" item is transmission guide information that specifies the storage location of the invoice image data (second form image data). The value of the "Invoice Image Data" item indicates the invoice image data.

[0062] In the example of Figure 6, it can be seen that the storage location of the invoice image data for purchase order number "1901985" is specified as "https: / / xxxxxx / xxxxxxxxx".

[0063] 6, when the transaction management device 200 receives invoice image data for purchase order number "1901985" from the seller terminal 400, it stores the received invoice image data in the memory area associated with "https: / / xxxxxx / △△△△△△." In other words, the transmission guide information in this embodiment can also be said to be information that specifies the memory area in which the second form image data is stored.

[0064] 6, an example in which the transmission guide information is a URL has been described, but the transmission guide information does not have to be a URL and may be, for example, an email address, etc. The storage management database 230 in the case in which the transmission guide information is an email address will be described below.

[0065] Fig. 7 is a diagram showing another example of the storage management database according to the first embodiment. The storage management database 230A shown in Fig. 7 includes email addresses, order form numbers, and invoice images as information items.

[0066] In the storage management database 230A, the value of the item "email address" indicates the storage destination of the corresponding invoice image data. In other words, the value of the item "email address" is transmission guide information for transmitting the invoice image data (second form image data).

[0067] 8 is a diagram illustrating an example of the matching management database according to the first embodiment. The matching management database 240 according to this embodiment may be provided for each tenant.

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

[0069] The value of the item "Processing Date and Time" indicates the date and time when the matching operation was performed. The value of the item "Total Amount" indicates, for example, the order amount included in the order form information.

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

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

[0072] 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 reception unit 263, a display control unit 264, an update unit 265, an information generation unit 266, an image generation unit 267, an output unit 268, a registration unit 269, and a matching management unit 270.

[0073] 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 various information inputs and requests from the buyer side terminal 300.

[0074] The display control unit 264 controls the display on the buyer terminal 300. The display control unit 264 may also control the display on the seller terminal 400. The update unit 265 updates each database in accordance with the processing of the transaction management unit 260.

[0075] The information generation unit 266 generates an order form number to be assigned to the order form. The information generation unit 266 also generates transmission guidance information in response to operations on the buyer terminal 300. The transmission guidance information may be, for example, a URL or an email address. In this embodiment, the transmission guidance information is generated by the information generation unit 266 of the transaction management device 200, but this is not limited to this. For example, the process of generating the URL or email address that will serve as the transmission guidance information may be performed by a device external to the transaction management system 100. In this case, the transaction management device 200 can cooperate with the external device and obtain the URL or email address generated by the external device as the transmission guidance information.

[0076] The image generating unit 267 generates order form image data (first form image data). The image generating unit 267 may also generate a two-dimensional code or the like including the transmission guide information generated by the information generating unit 266, and include the code in the order form image data.

[0077] The output unit 268 outputs the order form image data and transmission guide information. Specifically, the output unit 268 may transmit the order form image data and transmission guide information to the seller terminal 400, or may transmit to an image forming device or the like an instruction to print an order form in which the transmission guide information has been added to the order form image data. In other words, the output unit 268 of this embodiment outputs the first form image data and transmission guide information for transmitting the second form image data. Furthermore, the output unit 268 does not have to directly transmit the order form image data and the transmission guide information to the seller terminal 400. For example, the output unit 268 may send an email containing the order form image data and the transmission guide information to the seller's email address, and the seller terminal 400 may receive the order form image data and the transmission guide information by receiving the email from a mail server. Note that the output unit 268 does not have to transmit the order form image data when transmitting the transmission guide information to the seller terminal 400. In this case, the output unit 268 may transmit the order form image data separately to the seller terminal 400, or may transmit the order form information and the order form identification information to the seller terminal 400 together with the transmission guide information.

[0078] The registration unit 269 associates the purchase order number with the invoice image data transmitted from the seller terminal 400 and stores them in the storage management database 230. In other words, the registration unit 269 associates the second form image data transmitted based on the transmission guide information with the first form information and stores them in the memory unit (storage management database 230).

[0079] The matching management unit 270 performs various processes for performing matching work. Specifically, the matching management unit 270 causes the display control unit 264 to display a matching screen for performing matching work on the buyer side terminal 300, and acquires various information according to the results of the matching work.

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

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

[0082] 10 is a first sequence diagram illustrating the operation of the transaction management system of the first embodiment. FIG. 10 shows the operation up to the issuance of a purchase order in transaction management system 100.

[0083] In the transaction management system 100 of this embodiment, when the buyer terminal 300 receives a request to display an order form issuance screen in response to an operation from a tenant (step S1001), it sends a request to create an order form to the transaction management device 200 (step S1002).

[0084] When the transaction management device 200 receives a purchase order creation request via the input receiving unit 263, the display control unit 264 sends an instruction to the buyer terminal 300 to display an order form creation screen (step S1003). When the buyer terminal 300 receives the instruction to display the creation screen, the display unit 330 displays the order form creation screen on the display (step S1004). On this order form creation screen, a storage location for invoice image data is specified. The order form creation screen will be described in detail later.

[0085] Next, the buyer terminal 300 accepts input of purchase order information (step S1005), and then accepts input of an instruction to issue a purchase order from the tenant (step S1006).

[0086] When the buyer terminal 300 receives the instruction to issue a purchase order, it transmits the input purchase order information and a purchase order issuance request including the purchase order information to the transaction management device 200 (step S1007). This issuance request may include information identifying the tenant using the buyer terminal 300. The information identifying the tenant may be, for example, a tenant ID or a tenant name.

[0087] When transaction management device 200 receives the issuance request and order form information through input receiving unit 263, update unit 265 stores the order form information in order form database 220 (step S1008).

[0088] Next, the transaction management device 200 causes the information generation unit 266 to generate an order number and include it in the order information stored in the order database 220 in step S1008 (step S1009).

[0089] At this time, the information generating unit 266 generates transmission guide information based on the method of transmitting the invoice image data specified on the order form creation screen.

[0090] Next, the transaction management device 200 causes the update unit 265 to associate the transmission guidance information with the order number and store it in the storage management database 230 (step S1010).

[0091] Next, the transaction management device 200 generates order form image data using the image generation unit 267 (step S1011). At this time, the transaction management device 200 may generate a two-dimensional code indicating the transmission guidance information stored in the storage management database 230 in step S1010 and include it in the order form image.

[0092] Next, transaction management device 200 outputs the order form image data and transmission guidance information via output unit 268 (step S1012).

[0093] Next, with reference to FIG. 11, the operation of transaction management device 200 when invoice image data is transmitted from seller terminal 400 to transaction management device 200 will be described.

[0094] FIG. 11 is a second sequence diagram illustrating the operation of the transaction management system of the first embodiment.

[0095] 11 shows the process in steps S1101 to S1106 when the transmission guide information is a URL, and the process in steps S1107 to S1111 shows the process in steps S1107 to S1111 when the transmission guide information is an email address.

[0096] In this embodiment, when seller terminal 400 accepts an operation to open a URL that is transmission guidance information (step S1101), it transmits a display request for an invoice image data upload screen to transaction management apparatus 200 (step S1102).

[0097] Transaction management apparatus 200 receives this display request and causes seller terminal 400 to display an upload screen for the invoice image data (step S1103). Details of the upload screen will be described later.

[0098] Next, seller terminal 400 accepts an operation to instruct uploading of invoice image data (step S1104) and transmits the invoice image data to transaction management device 200 (step S1105). At this time, the invoice image data may be associated with a URL, which is transmission guidance information, and transmitted to transaction management device 200.

[0099] When the invoice image data is sent to the URL that is the transmission guidance information, the transaction management device 200 causes the registration unit 269 to associate the sent invoice image data with the transmission guidance information (URL) and the order form number and store it in the storage management database 230 (step S1106).

[0100] In this embodiment, the storage destination of the invoice image data associated with the URL that is the transmission guide information is the storage management database 230.

[0101] Next, a case where the transmission guide information is an email address will be described. In this embodiment, the seller terminal 400 accepts an operation to create an email addressed to the email address that is the transmission guide information (step S1107), and further accepts an operation to attach invoice image data (step S1108).

[0102] Next, when seller terminal 400 receives an instruction to send an email with invoice image data attached (step S1109), it sends the invoice image data to the email address (step S1110).

[0103] Next, the transaction management device 200 causes the registration unit 269 to associate the invoice image data attached to the email with the transmission guide information (email address) and the order form number, and store the associated data in the storage management database 230 (step S1111). In this embodiment, the storage destination for the invoice image data associated with the email address, which is the transmission guide information, is the storage management database 230.

[0104] In this embodiment, as described above, invoice image data is uploaded to the transaction management device 200. Note that in this embodiment, uploading invoice image data to the transaction management device 200 means transmitting the invoice image data from the seller terminal 400 to the transaction management device 200.

[0105] An example of an order form creation screen and order form image data of this embodiment will be described below with reference to Fig. 12. Fig. 12 is a diagram for explaining order form creation. Fig. 12(A) shows an example of an order form creation screen, and Fig. 12(B) is a diagram showing an example of order form image data.

[0106] 12A is an example of an order form creation screen displayed on the buyer terminal 300 in step S1003 of FIG.

[0107] Input fields for inputting purchase order information are displayed in the display area 122. In the display area 122, the input fields are input fields for inputting values ​​of items included in the purchase order information.

[0108] Display area 123 displays a selection field for selecting a method for sending the purchase order from the buyer to the seller. Specifically, display area 123 displays "send by email" and "send by mail" as options for the method for sending the purchase order. Display area 123 also displays input field 123a, where an email address can be entered when "send by email" is selected.

[0109] Display area 124 displays options for selecting a method for sending an invoice from the seller to the buyer. Specifically, display area 124 displays "Web" and "Email" as options for sending an invoice.

[0110] In this embodiment, the invoice image data transmission method indicated by the option "Web" is a method of transmitting invoice image data so that the invoice image data is stored in a storage destination corresponding to a specified URL. Also, the invoice image data transmission method indicated by the option "Email" is a method of transmitting invoice image data so that the invoice image data is stored in a storage destination associated with an email address.

[0111] In this embodiment, when the option "Web" is selected, for example, the transaction management device 200 generates a URL that serves as the transmission guidance information using the information generation unit 266. Also, when the option "Email" is selected, for example, the transaction management device 200 generates an email address that serves as the transmission guidance information using the information generation unit 266. The URL and email address that serve as the transmission guidance information may be input at the buyer terminal 300. Furthermore, the invoice transmission method previously registered in association with the seller may be displayed in the display area as the default value of the selected option, or the invoice transmission method previously registered in association with the seller may be fixed and not displayed in the display area 124 on the screen 121.

[0112] Operation button 125 is an operation button for causing buyer terminal 300 to send a purchase order form issuance request to transaction management device 200 .

[0113] In this embodiment, when the values ​​of the items included in the order form information are entered and the order form delivery method and invoice delivery method are selected, and then the operation button 125 is operated, the buyer's terminal 300 sends a purchase order issuance request to the transaction management device 200.

[0114] An order form image 126 shown in FIG. 12(B) is an example of an order form image indicated by the order form image data generated in step S1011 of FIG.

[0115] The order form image 126 includes order form information 122A, an order form number 127, and a two-dimensional code 129.

[0116] Order form information 122A is the order form information entered in display area 122, and order form number 127 is the order form number generated by information generation unit 266 in step S1009 of Fig. 10. Two-dimensional code 129 is the two-dimensional code generated in step S911 of Fig. 10, and includes transmission guide information that indicates the storage destination of the invoice image data specified on screen 121.

[0117] In the example of FIG. 12(B), a QR code (registered trademark) is used as an example of a two-dimensional code, but the two-dimensional code is not limited to a QR code. Also, in FIG. 12(B), the transmission guide information is included in the order form image 126 as a two-dimensional code, but this is not limiting. The transmission guide information may be included in the order form image data by a method other than a two-dimensional code. Also, the transmission guide information does not have to be included in the order form image data.

[0118] In this embodiment, if the option "Email" is selected in the display area 123 of the screen 121, the order form image data showing the order form image 126 is sent to the email address entered in the input field 123a.

[0119] In this embodiment, if the option "by mail" is selected in the display area 123 of the screen 121, the order form image 126 is printed by an image forming device or the like and mailed to the buyer.

[0120] In this manner, in this embodiment, order form image data showing an order form generated based on the input order form information and transmission guide information generated according to the transmission method of the invoice image data are output.

[0121] When the transaction management device 200 of this embodiment receives invoice image data based on the transmission guide information, it stores this invoice image data in the storage management database 230 in association with the transmission guide information and the order number.

[0122] Next, uploading of an invoice by a seller will be described with reference to Figure 13. Figure 13 is the first diagram for explaining uploading of an invoice. Screen 131 shown in Figure 13(A) shows an example of a screen displaying a cover letter to be sent together with the order form image data. Screen 135 shown in Figure 13(B) shows an example of a screen for performing an operation to upload an invoice.

[0123] The screen 131 shown in FIG. 13(A) may be displayed on the seller terminal 400 together with the order form image 126 shown in FIG. 12(B), for example.

[0124] Screen 131 includes display areas 126A, 132, and 133. Display area 126A displays the file name of the order form image data indicating order form image 126. Display area 132 displays information related to sending the order form. Display area 133 displays transmission guide information indicating the storage destination of invoice image data. Screen 131 displays the transmission guide information when the "Web" option for the invoice sending method is selected on screen 121.

[0125] When seller terminal 400 receives an operation to select the transmission guide information displayed in display area 133 on screen 131 , seller terminal 400 transitions screen 131 to screen 135 .

[0126] In this embodiment, by selecting the transmission guidance information displayed in display area 133 on screen 131, the storage destination of the invoice image data selected by an operation on screen 135 is specified as the storage destination indicated by the transmission guidance information.

[0127] Screen 135 is an example of a screen for performing an operation to send invoice image data in response to the transmission guidance information displayed in display area 133, and is displayed on seller terminal 400.

[0128] Screen 135 includes display area 134 displaying order form information 122A, operation button 136, display area 137, and operation button 138. When operation button 136 is operated on screen 135, a list of invoice image data to be uploaded is displayed in display area 137.

[0129] For example, when the invoice image data to be uploaded is selected from the list of invoice image data displayed in the display area 137 and the operation button 138 is operated, the seller terminal 400 transmits the selected invoice image data to the transaction management device 200.

[0130] At this time, the invoice image data transmitted from seller terminal 400 to transaction management device 200 is associated with the transmission guide information and transmitted to transaction management device 200.

[0131] Figure 14 is a second diagram illustrating uploading an invoice. Screen 131A shown in Figure 14(A) shows an example of a screen displaying a cover letter sent together with the order form image data. Screen 131B shown in Figure 14(B) shows another example of a screen displaying a cover letter sent together with the order form image data.

[0132] When the seller terminal 400 receives an operation on the screen 131A to select an email address displayed in the display area 133A, it may display an email creation screen for sending invoice image data to the transaction management device 200 to this email address.

[0133] In screen 131A shown in Fig. 14(A), the transmission guide information displayed in display area 133A is an email address. In screen 131B shown in Fig. 14(B), the buyer's email address is displayed in display area 133B, and a message indicating that the email address displayed in display area 133B has been designated as the transmission guide information is displayed in display area 139.

[0134] When the seller terminal 400 receives an operation to reply to the email address (sending guidance information) of the buyer terminal 300 on screen 131B, it may display an email creation screen for sending invoice image data to the transaction management device 200.

[0135] In this way, in this embodiment, an email address may be specified in the transmission guidance information. An example of the storage management database when an email address is specified in the transmission guidance information is shown below.

[0136] Next, the processing by the matching management unit 270 of the transaction management device 200 of this embodiment will be described with reference to FIGS.

[0137] In this embodiment, when the matching management unit 270 receives an instruction to start matching work between order form information and invoice image data at the buyer's terminal 300, it causes the buyer's terminal 300 to display a matching screen including the order form information and invoice image data.

[0138] 15 is a diagram showing an example of a list screen according to the first embodiment. Screen 161 shown in FIG. 15 is an example of a screen displayed on buyer terminal 300, and shows a list of purchase order information. In this embodiment, transaction management device 200 may receive a request from buyer terminal 300 to display a list of purchase order information, and cause display control unit 264 to display screen 161 on buyer terminal 300.

[0139] The screen 161 includes a display area 162 , a group of operation buttons 163 , an input field 164 , and operation buttons 165 and 166 .

[0140] Display area 162 shows a list of order form information stored in order form database 220. Display area 162 displays order form information in association with check boxes for selecting order form information.

[0141] The operation button group 163 is an operation button for displaying a matching screen for each piece of purchase order information.

[0142] In the input field 164, extraction conditions for narrowing down the list of order form information to be displayed in the display area 162 are input.

[0143] Operation buttons 165 and 166 are operation buttons for the buyer to notify the seller of the results of the matching work.

[0144] When one of the operation buttons 163 on screen 161 is selected, a matching screen is displayed that includes the order form information displayed in association with the selected operation button and the invoice image data associated with this order form information. Note that operation buttons 163 do not need to be displayed, for example, if the order form number and the invoice image data are not associated in the storage management database 230, that is, if the transaction management device 200 has not received the invoice image data from the seller terminal 400.

[0145] Furthermore, on the screen 161, the operation button group 163 does not need to be displayed for purchase order information in which the value of the item "confirmation status" included in the purchase order information is "confirmed."

[0146] Operation button 165 is an operation button for notifying the seller corresponding to the selected order form information in display area 162 of the matching results. When operation button 165 is selected while order form information is selected in display area 162, buyer terminal 300 transmits a request to transaction management device 200 to send a notification to the seller corresponding to the selected order form information.

[0147] Upon receiving this request, the transaction management device 200 refers to the order destination management database 210 and notifies the order destination corresponding to the selected order form information of the matching result. The matching result may be entered on the matching screen described below. In this embodiment, order form information whose "Confirmation Status" field has a value of "Unprocessed" may be made unselectable in the display area 162.

[0148] Operation button 166 is an operation button for sending a notification all at once to the ordering parties corresponding to the order form information whose "Matching result" field has a value of "X." Order form information whose "Matching result" field has a value of "X" is order form information that has been determined to be inconsistent with the invoice image data during matching.

[0149] When operation button 166 is operated, buyer terminal 300 sends a request to transaction management device 200 to send a notification of the matching result to the order recipient corresponding to the order form information in which the value of the item "Matching result" is "X".

[0150] Upon receiving this request, transaction management device 200 refers to order destination management database 210 and notifies the order destination corresponding to the order form information for which the matching result is determined to be a mismatch of the matching result.

[0151] Next, the matching screen of this embodiment will be described with reference to Fig. 16. Fig. 16 is a diagram showing an example of the matching screen of the first embodiment.

[0152] Screen 171 shown in FIG. 16 is an example of a matching screen displayed on buyer terminal 300 when operation button 163 corresponding to order form information including order form number "190186" is operated on screen 161 in FIG.

[0153] Screen 171 has display areas 122B, 172, 173, and operation buttons 174 and 175. Display area 122B displays purchase order information that is the subject of matching work. Display area 172 displays invoice image data associated with the purchase order information displayed in display area 122B.

[0154] The display area 173 includes a display area 173a and a remarks field 173b. The display area 173a displays, for example, the item names of the items included in the order form information, and selection fields and input fields corresponding to the item names.

[0155] In this embodiment, in the display area 173a, an item for which the value included in the order form information and the value included in the invoice image data do not match as a result of the matching process may be selected, and the information written on the invoice may be entered. At this time, in the display area 173a, the value included in the invoice image data may be entered in the input field corresponding to the selected item.

[0156] In the example of Figure 16, the order amount displayed in display field 122a of display area 122B does not match the total billed amount displayed in display field 172a of display area 172. Also, in the example of Figure 16, the unit price for detail 1 displayed in display field 122b does not match the unit price displayed in display field 172b of display area 172, and the amount for detail 1 displayed in display field 122c does not match the amount displayed in display field 172c.

[0157] Therefore, on screen 171, the items "Order amount," "Unit price for item 1," and "Amount for item 1" are selected in display area 173, and the values ​​shown in the invoice image data are entered in the corresponding input fields.

[0158] Further, detailed information about the parts that are determined not to match in the matching process is input to the remarks column 173b. Further, the content of the notification to be sent to the order recipient may be input to the remarks column 173b.

[0159] Operation button 174 is an operation button for temporarily saving the content input in display area 173. Operation button 175 is an operation button for transitioning screen 171 to screen 161.

[0160] In this embodiment, for example, when operation button 175 is operated with a value entered in one of the input fields in display area 173a, screen 171 transitions to screen 161. At this time, the value of the item "Matching result" of the purchase order information including purchase order number "190186" on screen 161 may be displayed as "X" indicating a mismatch.

[0161] As described above, in this embodiment, the image data of the invoice issued in correspondence with the purchase order including the purchase order information entered by the buyer is associated with the purchase order information, which makes it easy to check the contents of the order against the contents of the invoice.

[0162] Furthermore, in this embodiment, transmission guidance information for transmitting an invoice issued in correspondence with a purchase order is generated, and invoice image data transmitted based on the transmission guidance information is stored in correspondence with the purchase order information. Therefore, according to this embodiment, it is possible to easily associate the purchase order information with the invoice image data. Although this embodiment describes outputting the purchase order image data together with the transmission guidance information, it is not necessary to output the purchase order image data, or it is possible to output the purchase order information, rather than the purchase order image data, together with the transmission guidance information. Furthermore, this embodiment describes storing the invoice image data transmitted based on the transmission guidance information in correspondence with the purchase order information, but it is also possible to store the invoice information transmitted based on the transmission guidance information in correspondence with the purchase order information or the purchase order image data.

[0163] (Second embodiment) The second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that form recognition is performed on invoice image data transmitted based on transmission guide information to obtain invoice information, and the invoice information is then matched with order form information. Therefore, the following description of the second embodiment will focus on the differences from the first embodiment, and components having the same functional configuration as those in the first embodiment will be assigned the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

[0164] 17 is a diagram showing an example of the system configuration of a transaction management system according to the second embodiment. Transaction management system 100A of this embodiment includes transaction management device 200A and terminal device (buyer terminal) 300.

[0165] Transaction management device 200A of this embodiment has order destination management database 210, order form database 220, storage management database 230, matching management database 240, history management database 250, invoice database 280, and transaction management section 260A.

[0166] The history management database 250 stores history information indicating the issuance history of purchase orders, the transmission history of invoices, and the like.

[0167] The invoice database 280 stores the results of performing form recognition on the invoice image data stored in the storage management database 230 as invoice information.

[0168] The transaction management unit 260A performs form recognition on the invoice image data and cross-checks the order form information and invoice information.

[0169] 18 is a diagram showing an example of the history management database of the second embodiment. The history management database 250 of this embodiment includes transmission history information 250-1 indicating the history of transmission processes of invoice image data from the seller terminal 400, and transmission image information 250-2 indicating the invoice image data transmitted for each transmission process.

[0170] The transmission history information 250-1 includes information items such as a URL, an order number, and an invoice upload ID. The transmission image information 250-2 includes information items such as an invoice upload ID, an invoice image, an upload date and time, and a reissue notification.

[0171] In the transmission history information 250-1 and the transmission image information 250-2, the item "bill upload ID" is associated with other items.

[0172] The value of the item "invoice upload ID" is identification information for identifying the transmission process (upload) of invoice image data, and is generated every time invoice image data is uploaded from the seller terminal 400.

[0173] The value of the item "Upload date and time" indicates the date and time when the invoice image data was uploaded. The value of the item "Reissue notification" indicates the date and time when the transaction management device 200 notified the seller terminal 400 that the invoice had been reissued.

[0174] In the example of Figure 8, there are invoice upload IDs "190186001" and "190186002" for order number "190186." Therefore, in the example of Figure 8, it can be seen that invoice image data has been uploaded twice for order number "190186."

[0175] In addition, in the example of Figure 8, it can be seen that the first invoice image data upload for purchase order number "190186" was made on July 20, 2018, and that a notification of invoice reissue was sent for this invoice image data on August 1, 2020.

[0176] 19 is a diagram showing an example of the invoice database of the second embodiment. The invoice database 280 of this embodiment includes information items such as purchase order number, invoice ID, invoice destination, invoice amount, invoice date, payment due date, statement information, and transfer destination information, and each item is associated with the item "invoice ID" and the item "purchase order number."

[0177] In the following description, information in the invoice database 280 that includes the values ​​of the items "invoice ID" and "order form number" and the values ​​of other items associated with the items "invoice ID" and "order form number" may be referred to as invoice information.

[0178] The value of the "Invoice ID" item is the document identification information used to identify the invoice. The value of the "Invoice recipient" item indicates the name of the invoice recipient for the invoice identified by the invoice ID. The values ​​of the "Invoice amount," "Invoice date," and "Payment due date" items indicate the invoice amount, invoice date, and payment due date, respectively, listed on the invoice.

[0179] The item "Detailed information" corresponds to items that indicate the breakdown of the billing amount, such as the items "Product code," "Product name," and "Quantity," and the value of the item "Detailed information" indicates the breakdown of the billing amount.

[0180] The item "Transfer destination information" corresponds to items indicating the transfer destination of the invoice amount, such as the items "Bank name," "Branch," "Account type," and "Account number," and the value of the item "Transfer destination information" indicates the transfer destination of the invoice amount.

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

[0182] Next, the function of transaction management device 200A of this embodiment will be described with reference to Fig. 20. Fig. 20 is a diagram for explaining the function of transaction management device 200A of the second embodiment.

[0183] The transaction management unit 260A of the transaction management device 200A of this embodiment has a transmitting unit 261, a receiving unit 262, an input accepting unit 263, a display control unit 264, an updating unit 265, an information generating unit 266, an image generating unit 267, an output unit 268, a registration unit 269, and a matching management unit 270A.

[0184] The matching management unit 270A of this embodiment includes a form recognition unit 271, a recognition result storage unit 272, a matching unit 273, a history management unit 274, and a matching result output unit 275.

[0185] The form recognition unit 271 of this embodiment performs form recognition processing to extract the names of items (item names) and the values ​​of these items (item values) included in the form image indicated by the form image data, convert the items and the item values ​​into text data, and associate them. Specifically, the form recognition unit 271 extracts the item names and the item values ​​included in the invoice image indicated by the invoice image data, converts them into text data, and associates them.

[0186] The recognition result storage unit 272 stores the results of form recognition performed by the form recognition unit 271 on the invoice image data in the matching result output unit 275. In the following description, the results of form recognition performed by the form recognition unit 271 may be referred to as invoice information.

[0187] The matching unit 273 matches the order form information with the invoice information. Specifically, the matching unit 273 determines whether all items and item values ​​included in the order form information match the items and item values ​​included in the invoice information.

[0188] The history management unit 274 manages the history of invoice image data sent in response to order information. Specifically, the history management unit 274 manages the history management database 250.

[0189] The matching result output unit 275 stores the result of the matching process by the matching unit 273 in the matching management database 240. The matching result output unit 275 also outputs a notification according to the result of the matching process.

[0190] Next, the operation of the transaction management system 100A of this embodiment will be described with reference to Figure 21. Figure 21 is a sequence diagram explaining the operation of the transaction management system of the second embodiment. Figure 21 shows the operation when the reconciliation management unit 270A performs reconciliation processing in the transaction management system 100A.

[0191] In transaction management system 100A, transaction management device 200A registers the invoice image data transmitted from seller terminal 400 in storage management database 230 (step S2101).

[0192] Next, buyer terminal 300 accepts a request to display a list screen of order form information (step S2102), and then transmits a request to display a list screen of order form information to transaction management device 200A (step S2103).

[0193] Transaction management device 200A receives this display request, and causes display control unit 264 to send an instruction to buyer terminal 300 to display the list screen of order form information, causing buyer terminal 300 to display the list screen of order form information (step S2104).

[0194] Next, the buyer terminal 300 accepts the selection of the order form information to be matched on the order form information list screen (step S2105). Upon accepting the selection, the buyer terminal 300 transmits a request to the transaction management device 200A to match the selected order form information with the invoice information associated with the order form information (step S2106).

[0195] Upon receiving the matching request, transaction management device 200A causes matching unit 273 to perform matching processing between the order form information and the invoice information (step S2107). The matching processing performed by matching unit 273 will be described in detail below.

[0196] Next, transaction management device 200A causes matching result output unit 275 to output the matching result from matching unit 273 to display control unit 264, and display control unit 264 sends a display instruction for a matching screen including the matching result to buyer terminal 300 (step S2108). Upon receiving the display instruction, buyer terminal 300 displays the matching screen (step S2109).

[0197] Next, when buyer terminal 300 receives an operation from the buyer indicating that the matching results have been confirmed (step S2110), it sends a notification to transaction management device 200A indicating that the buyer's visual matching work has been completed (step S2111). At this time, the buyer may input the results of the matching work on the matching screen, and in that case, the information input on the matching screen is also sent to transaction management device 200A along with the notification indicating the completion of the matching work.

[0198] Transaction management device 200A stores the reconciliation results in reconciliation management database 240 via update unit 265 (step S2112).

[0199] Next, transaction management device 200A causes display control unit 264 to send an instruction to buyer terminal 300 to display a list screen of order form information reflecting the matching results (step S2113).

[0200] The buyer terminal 300 receives this display instruction and displays a list screen of the order form information reflecting the matching results (step S2114).

[0201] Next, the matching process by the matching unit 273 will be described with reference to Fig. 22. Fig. 22 is a flowchart illustrating the matching process of the second embodiment. Fig. 22 shows details of the process by the matching management unit 270A in step S2107 of Fig. 21.

[0202] In the matching management unit 270A of the transaction management device 200A, the document recognition unit 271 acquires the invoice image data corresponding to the selected order form information from the storage management database 230, and performs document recognition to acquire the invoice information (step S2201).

[0203] Next, the document recognition unit 271 stores the invoice information in the invoice database 280 (step S2202). Next, the matching management unit 270A refers to the order form database 220 and acquires the order form information to be matched, selected in step S2105 (step S2203).

[0204] Next, the matching management unit 270A uses the matching unit 273 to compare the values ​​of each item included in the order form information and the invoice information (step S2204).The matching unit 273 then determines whether or not there are any mismatched items (step S2205).

[0205] In step S2205, if there are any mismatched items, the matching result output unit 275 sets the value of the item "Matching result" in the order form information to "X" (step S2206), sets the value of the item "Confirmation status" to "Unprocessed" (step S2207), and terminates the processing.

[0206] In step S2205, if there are no mismatched items, that is, if all If the items match, the matching result output unit 275 sets the value of the item "matching result" of the order form information to "○" (step S2208), and the process proceeds to step S2207.

[0207] Next, examples of display of the order form information list screen and matching screen of this embodiment will be described with reference to FIGS.

[0208] Fig. 23 is a first diagram showing an example of a list screen according to the second embodiment. The list screen 161A shown in Fig. 23 is an example of a list screen of purchase order information displayed on the buyer terminal 300 in step S2102 of Fig. 21.

[0209] The screen 161A includes a display area 162A, an operation button group 163A, an input field 164, and operation buttons 165 and 166.

[0210] On screen 161A, display area 162A displays a list of order form information and invoice information extracted from invoice image data corresponding to the order form information. Also displayed in display area 162A are check boxes for selecting order form information and invoice information associated with the order form information.

[0211] The operation button group 163A is for executing a matching process with invoice information for each order form information and for instructing the display of a matching screen. The operation button group 163A of this embodiment includes, for example, operation buttons 163a, 163b, and 163c.

[0212] 24 is a first diagram showing an example of a matching screen in the second embodiment. A screen 171A shown in FIG. 24 is an example of a screen displayed on the buyer terminal 300 in step S2109 of FIG.

[0213] More specifically, screen 171A shown in Figure 24 is an example of a matching screen that is displayed on the buyer's terminal 300 when operation button 163c corresponding to order form information including order form number "190186" is operated on screen 161A in Figure 23.

[0214] The screen 171A has display areas 122C, 172A, 173A, and operation buttons 174 and 175.

[0215] Display area 122C displays the order form information that is the subject of the matching operation. Display area 122C also includes operation button 122d. In this embodiment, when operation button 122d is operated, buyer terminal 300 may send a request to acquire order form image data of the order form information displayed in display area 122C to transaction management device 200A, and may acquire and display the order form image data.

[0216] The display area 172A displays the invoice information extracted from the invoice image data by the document recognition unit 271. Specifically, the display area 172A displays the invoice information obtained from the invoice image data for the order form information including the order form number "109186."

[0217] Display area 172A also includes operation button 172d. When operation button 172d is operated, buyer terminal 300 may transmit a request to acquire invoice image data of the invoice information displayed in display area 172A to transaction management device 200A, and acquire and display the invoice image data.

[0218] Display area 173A displays the result of matching performed by matching unit 273 between the order form information displayed in display area 122C and the invoice information displayed in display area 172A.

[0219] Display area 173A includes display column 173c and display column 173b. Display column 173c displays the values ​​of items included in the order form information and the values ​​of items included in the invoice information, side by side for each item. Display column 173c also displays check boxes corresponding to each item, and as a result of the matching process by matching unit 273, a check mark is displayed in the check box corresponding to an item whose values ​​do not match.

[0220] In this embodiment, the invoice information is obtained from the invoice image data, the values ​​of corresponding items in the order form information and the invoice information are compared, and items with mismatched values ​​are identified and displayed. Therefore, according to this embodiment, the buyer can easily visually determine whether the order details and the invoice details match.

[0221] Figure 25 is a second diagram showing an example of the list screen of the second embodiment. The list screen 161B shown in Figure 25 shows the list screen after a cross-checking process between the selected order form information and invoice information found mismatched items, so a notification to that effect was sent to the order recipient (invoice source) and the invoice image data was received again. The destination of the communication can be obtained from the order recipient management database 210.

[0222] Screen 161B includes a display area 162A, a group of operation buttons 163B, and an input field 164. On screen 161B, group of operation buttons 163B includes an operation button 163b′ for sending a request to the seller to reissue the invoice, and an operation button 163c for instructing execution of matching processing and display of a matching screen.

[0223] Furthermore, on screen 161B, if the value of the item "Matching result" in the order form information is "○" and the value of the item "Confirmation status" is "Confirmed," the operation buttons for instructing the execution of matching processing and the display of the matching screen do not need to be displayed.

[0224] On screen 161B, the result of matching between the purchase order information including purchase order number "109184" and the invoice information is "○", and the confirmation status is "Confirmed." Therefore, on screen 161B, the operation buttons included in operation button 163B are not displayed.

[0225] Furthermore, on screen 161B, if the value of the item "Matching result" is "X" and the value of the item "Confirmation status" is "Confirmed", an operation button for sending a request to reissue the invoice may be displayed.

[0226] On screen 161B, the result of matching between the purchase order information including purchase order number "109186" and the invoice information is "X", and the confirmation status is "Confirmed." Therefore, on screen 161B, an operation button 163c' is displayed for sending a request to reissue an invoice for the purchase order information including purchase order number "109186."

[0227] In this embodiment, the operation buttons included in the operation button group 163B can be changed in accordance with the result of the matching process by the matching unit 273 and the state of the buyer's visual confirmation of the matching result.

[0228] Furthermore, on screen 161B, the display of operation buttons 165 and 166 has been erased from display area 167 where they were previously displayed. By doing so on screen 161B, this can contribute to reducing the occurrence of human error, such as mistakenly sending a notification requesting the reissuance of an invoice even though the matching results match.

[0229] Figure 26 is a second diagram showing an example of the matching screen in the second embodiment. Screen 171B shown in Figure 26 shows the matching screen when operation button 163c' is selected on screen 161B in Figure 25 and an invoice is reissued for purchase order information including purchase order number "109186."

[0230] The screen 171B has display areas 122C, 172B, 173B, and operation buttons 174 and 175.

[0231] In response to a request for reissuance of an invoice, display area 172B displays invoice information acquired from the invoice information image data of the reissued invoice.

[0232] Specifically, the invoice information displayed in display area 172B has the invoice date of "2018 / 8 / 2," which indicates that it was acquired later than the invoice information displayed in display area 172A of screen 171A in Figure 24.

[0233] Additionally, display area 172B displays form image path 172e of invoice image data issued for the order form information displayed in display area 122C. When form image path 172e is selected on screen 171B, invoice image data of a previously issued invoice may be displayed.

[0234] Display area 173B includes a display field 173c, a remarks field 173b, and an operation button 173e. Operation button 173e is an operation button for requesting the reissuance of an invoice for the purchase order information displayed in display area 122C.

[0235] In this embodiment, by providing an operation button 173e on screen 171B, when requesting reissue of an invoice, it is possible to request reissue of the invoice without returning from the matching screen to the list screen.

[0236] Here, with reference to FIG. 18, the management of the transmission history of invoice image data when an invoice is reissued will be described.

[0237] The examples in Figures 23 to 26 above show a case where the contents of the invoice originally issued for purchase order information including purchase order number "109186" did not match the contents of the purchase order, and the invoice was reissued.

[0238] In this case, the history management unit 274 of the matching management unit 270A assigns an invoice upload ID to each transmission process (upload) of invoice image data for the order number "109186" and associates it with the order number and transmission guide information.

[0239] Then, the history management unit 274 associates the invoice upload ID, the invoice image data, and the upload date and time.

[0240] In this embodiment, the invoice image data of the reissued invoice is transmitted from the seller terminal 400 to the transaction management device 200A based on transmission guidance information for transmitting the original invoice image data.

[0241] 18, there are two invoice upload IDs corresponding to the order number "109186." Therefore, in this case, the order number "109186" is associated with the invoice upload IDs "1091860001" and "1091860002," indicating that the invoice image data was sent twice.

[0242] Furthermore, the transmitted image information 250-2 in the history management database 250 indicates that the invoice image data transmitted in the transmission process corresponding to the invoice upload ID "1091860002" is newer than the invoice image data transmitted in the transmission process corresponding to the invoice upload ID "1091860001."

[0243] That is, the invoice information displayed in display area 172 of screen 171A in Fig. 24 was obtained from the invoice image data sent in the transmission process corresponding to invoice upload ID "1091860001." Also, the invoice information displayed in display area 172B of screen 171B in Fig. 26 was obtained from the invoice image data sent in the transmission process corresponding to invoice upload ID "1091860002."

[0244] In this way, in this embodiment, even if the matching results are not consistent and the invoice is reissued, it is possible to manage the invoice image data issued in the past and the date and time when the transmission process was performed.

[0245] In the above-described embodiment, the first and second forms to be matched are an order form and an invoice, respectively, but this is not limiting. The above-described embodiments can be applied to any form as long as the form requires a matching operation to determine whether the contents of both forms match. Specifically, for example, the first form to be matched may be an order form and the second form may be a delivery note. Alternatively, the first form may be an estimate and the second form may be an order form.

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

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

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

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

[0250] The correspondence table 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 correspondence table.

[0251] 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 classification from training data that is input in advance, and applies these to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods; the learning method for machine learning is not important.

[0252] 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]

[0253] 100, 100A trading management system 200, 200A Transaction Management Device 210 Order Management Database 220 Order Form Database 230 Storage Management Database 240 Reconciliation Management Database 250 History Management Database 260 Transaction Management Department 266 Information generation section 267 Image Generation Unit 268 Output Section 269 ​​Registration Department 270, 270A Matching management department 271 Document Recognition Unit 272 Recognition result storage unit 273 Butt joint 274 History Management Department 275 Matching result output section 280 Invoice Database 300 Terminal device (buyer's terminal) 400 Terminal Device (Seller's Terminal) [Prior art documents] [Patent documents]

[0254] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-196525

Claims

1. An information processing device that communicates with a first terminal device and a second terminal device, a generating unit that generates transmission guidance information indicating a transmission destination of a second form that is issued in response to a first form including first form information input from the first terminal device, in accordance with a transmission method of the second form specified in the first terminal device; a storage unit that stores the transmission guide information and identification information that identifies the first form in association with each other; an output unit that outputs the generated transmission guide information; An information processing device having a registration unit that, based on the transmission guidance information output by the output unit, corresponds information indicating the second form sent from the second terminal device to the destination indicated in the transmission guidance information and identification information that identifies the first form and registers them in the memory unit.

2. The output unit outputting first form image data showing the first form and transmission guide information corresponding to a second form issued for the first form; The registration unit The information processing apparatus according to claim 1 , wherein second form image data indicating the second form and first form information included in the first form image data are registered in the storage unit in association with each other.

3. 3. The information processing apparatus according to claim 2, wherein the first form image data includes the first form information and the transmission guide information.

4. 4. The information processing apparatus according to claim 2, further comprising a display control unit that displays a screen including the first form information and the second form image data associated with the first form information on a display unit.

5. a form recognition unit that performs form recognition on the second form image data and acquires second form information; a matching unit that matches the first form information with the second form information, The display control unit The information processing apparatus according to claim 4 , wherein the display unit displays a screen including the first form information, the second form information, and the matching result.

6. 6. The information processing apparatus according to claim 5, further comprising a matching result output unit that transmits a notification according to the result of matching the first form information with the second form information to the issuer of the second form.

7. The transmission guidance information is The information processing apparatus according to claim 2 , wherein the information is associated with a storage location of the second form image data.

8. An information processing method by an information processing device that communicates with a first terminal device and a second terminal device, the information processing device comprising: generating transmission guide information indicating a transmission destination of a second form issued in response to a first form including first form information input from the first terminal device, in accordance with a transmission method of the second form specified in the first terminal device; storing the transmission guidance information and identification information for identifying the first form in a storage unit in association with each other; outputting the generated transmission guidance information; An information processing method in which, based on the output transmission guidance information, information indicating the second form sent from the second terminal device to the destination indicated in the transmission guidance information is associated with identification information identifying the first form and registered in the memory unit.

9. An information processing device that communicates with a first terminal device and a second terminal device, generating transmission guide information indicating a transmission destination of a second form issued in response to a first form including first form information input from the first terminal device, in accordance with a transmission method of the second form specified in the first terminal device; storing the transmission guidance information and identification information for identifying the first form in a storage unit in association with each other; outputting the generated transmission guide information; A program that executes a process that, based on the output transmission guidance information, associates information indicating the second form sent from the second terminal device to the destination indicated in the transmission guidance information with identification information that identifies the first form and registers them in the memory unit.

10. An information processing system including an information processing device, a first terminal device, and a second terminal device, The information processing device includes: a generating unit that generates transmission guidance information indicating a transmission destination of a second form that is issued in response to a first form including first form information input from the first terminal device, in accordance with a transmission method of the second form specified in the first terminal device; a storage unit that stores the transmission guide information and identification information that identifies the first form in association with each other; an output unit that outputs the generated transmission guide information; a registration unit that associates information indicating the second form transmitted from the second terminal device to the destination indicated by the transmission guidance information output by the output unit with identification information specifying the first form and registers the information in the storage unit, The terminal device An information processing system having a display unit that displays a screen having an input field for the first form information and a selection field for selecting a transmission method for the second form image data.

Images