Transaction management system, transaction management device, transaction management method, and program

Abstract

To reduce the burden of coordination work associated with transactions.SOLUTION: A transaction management system is provided, comprising an issued order information acquisition unit for acquiring issued order information from an orderer terminal device, a received order information acquisition unit for acquiring received order information from an order receiver terminal device, a search information acquisition unit for acquiring search information, and a generation unit configured to generate collation information including issued order information and received order information corresponding to the search information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a transaction management system, a transaction management device, a transaction management method, and a program. [Background technology]

[0002] When a business transaction is carried out between an ordering company that procures materials and an order-receiving company that receives the materials, various forms such as purchase orders, sales orders, delivery notes, and invoices are used. These forms may be sent and received by email or fax. In recent years, systems that use EDI (Electronic Data Interchange) to electronically send and receive each form via a dedicated line or the Internet are becoming available. For example, Patent Document 1 describes a communication system that configures a system for ordering products without using a dedicated line. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Utility Model Registration No. 3108363 Summary of the Invention [Problem to be solved by the invention]

[0004] However, even if documents can be handled electronically, there are cases where changes to the order quantity or unit price occur after an order is placed. In such cases, the ordering company and the receiving company use telephone, fax, email, etc. to make adjustments between the staff members to see if changes are possible. In such cases, changes to payments and invoices occur as a result of the adjustments, but these confirmations must be made by the staff members, which places a heavy burden on the staff members.

[0005] One aspect of the present invention has been made in consideration of the above circumstances, and its purpose is to provide a transaction management system, transaction management device, transaction management method, and program that can reduce the burden of adjustment work in transactions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, a transaction management system according to one embodiment of the present invention is a transaction management system that includes an order information acquisition unit that acquires order information from an orderer terminal device, an order information acquisition unit that acquires order information from a contractor terminal device, a search information acquisition unit that acquires search information, and a generation unit that generates matching information including the order information and the order information corresponding to the search information.

[0007] In addition, a transaction management device according to one embodiment of the present invention is a transaction management device that includes an order information acquisition unit that acquires order information from an orderer terminal device, an order information acquisition unit that acquires order information from a contractor terminal device, a search information acquisition unit that acquires search information, and a generation unit that generates matching information including the order information and the order information corresponding to the search information.

[0008] In addition, a transaction management method according to one embodiment of the present invention is a transaction management method executed by a computer, which has an order information acquisition process for acquiring order information from an orderer terminal device, an order information acquisition process for acquiring order information from a contractor terminal device, a search information acquisition process for acquiring search information, and a generation process for generating matching information including the order information and the order information corresponding to the search information.

[0009] In addition, a program related to one embodiment of the present invention is a program for causing a computer to execute an order information acquisition step of acquiring order information from an orderer terminal device, an order information acquisition unit step of acquiring order information from a contractor terminal device, a search information acquisition step of acquiring search information, and a generation step of generating matching information including the order information and the order information corresponding to the search information. Effect of the Invention

[0010] According to the present invention, the burden of adjustment work in transactions can be reduced. [Brief description of the drawings]

[0011] [Figure 1] A system configuration diagram showing an example of the configuration of a transaction management system according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of the configuration of a transaction management device according to an embodiment of the present invention. [Diagram 3] FIG. 4 is a diagram showing an example of order information according to the embodiment; [Figure 4] FIG. 4 is a diagram showing an example of order information according to the embodiment. [Diagram 5] FIG. 4 is a diagram showing an example of a display screen according to the embodiment. [Figure 6] FIG. 11 is a diagram showing another example of the display screen according to the embodiment. [Figure 7] FIG. 11 is a diagram showing another example of the display screen according to the embodiment. [Figure 8] FIG. 11 is a diagram showing another example of the display screen according to the embodiment. [Figure 9] A sequence diagram showing an example of a transaction management process in a transaction management system according to this embodiment. [Figure 10] 13 is a flowchart showing an example of a transaction management process in the transaction management device according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0013] First, the configuration of the transaction management system SYS according to this embodiment will be described with reference to FIG. FIG. 1 is a system configuration diagram showing an example of the configuration of a transaction management system SYS according to this embodiment. The transaction management system SYS includes a transaction management device 100, an orderer terminal device 200, and a contractor terminal device 300. The transaction management device 100, the orderer terminal device 200, and the contractor terminal device 300 are connected to each other via a network NW so as to be able to communicate with each other. Here, the orderer terminal device 200 is a terminal device used by the orderer. The orderer is, for example, a manufacturer. The contractor terminal device 300 is a terminal device used by the contractor. The contractor is, for example, a supplier. Note that the orderer and contractor need only have an ordering and receiving relationship, and the orderer does not have to be a manufacturer, and the contractor does not have to be a supplier. Note that there may be more than one orderer and / or contractor. Also, the transaction management device 100 may function by being configured on the cloud.

[0014] Transaction management device 100 transmits information related to commercial transactions between purchaser terminal device 200 and seller terminal device 300. For example, transaction management device 100 acquires various information, such as order information, transmitted from purchaser terminal device 200 via network NW. Transaction management device 100 acquires various information, such as order information, from seller terminal device 300 via the network.

[0015] Order information is information that represents the order details of a product, such as a service, an item, or materials. The information that represents the order details of a product includes information that represents the product, the product quantity, the product unit price, etc. More specifically, the information that represents the product is information such as product identification information, the number of products ordered, and the number of products in stock. In this embodiment, an example will be described in which the order information is payment information. Payment information will be described later.

[0016] Furthermore, the order information is information that represents the order contents of a product, such as a service, an item, or materials. The information that represents the order contents of a product includes information that represents the product, the product quantity, the product unit price, etc. More specifically, the information that represents the product is information such as product identification information, the number of products ordered, and the number of products shipped. In this embodiment, an example of the case where the order information is billing information will be described. The order information will be described later.

[0017] Transaction management device 100 generates matching information for matching order information with order information. In response to a request from purchaser terminal device 200 or vendor terminal device 300, transaction management device 100 transmits the generated matching information to purchaser terminal device 200 or vendor terminal device 300 that is the request source.

[0018] The orderer terminal device 200 is a terminal device equipped with an input device (mouse, keyboard, touch panel, etc.), an output device (display, etc.), a central processing unit, etc. The orderer terminal device 200 is a terminal device such as a computer, a tablet, a smartphone, etc. Purchaser terminal device 200 accepts input of order information from a purchaser. Purchaser terminal device 200 transmits the accepted order information to transaction management device 100 via network NW.

[0019] The contractor terminal device 300 is a terminal device equipped with an input device (mouse, keyboard, touch panel, etc.), an output device (display, etc.), a central processing unit, etc. The contractor terminal device 300 is a terminal device such as a computer, a tablet, a smartphone, etc. The vendor terminal device 300 receives input of order information from the vendor. The vendor terminal device 300 transmits the received order information to the transaction management device 100 via the network NW.

[0020] Here, an account in the transaction management system SYS is assigned to each of the orderer terminal device 200 and the orderee terminal device 300. Each account is managed by the transaction management device 100 using a login ID, a password, and the like. It should be noted that one or both of the orderer terminal device 200 and the contractor terminal device 300 may be a plurality of terminal devices. In this case, it is sufficient that an account is assigned to each terminal device.

[0021] Here, an orderer (e.g., a manufacturer) manufactures a product using materials procured from a customer (e.g., a supplier) and delivers the product to the delivery destination. If there is a change in the order content received from the delivery destination, the order content to the supplier may also change. For example, if there is a change in the quantity to be delivered, it may be necessary to make adjustments to the supplier to change the materials to be ordered, increase or decrease the quantity, or change the delivery date in order to accommodate the change.

[0022] Changes in the order contents are not limited to changes in the order from the delivery destination, but may also include changes in the order quantity in response to changes in market needs.

[0023] Conventionally, such adjustments have been made by telephone or fax, but in this embodiment, the manufacturer can make adjustments by using the orderer terminal device 200 and communicating with the contractor terminal device 300 via the transaction management device 100.

[0024] In this way, the transaction management system SYS obtains order information from the purchaser terminal device 200 and obtains order information from the vendor terminal device 300. When search information is obtained from the purchaser terminal device 200 or the vendor terminal device 300, verification information is generated that includes the order information and the order information that correspond to the search information. The search information will be described later. In this way, the transaction management system SYS can process payments and invoices based on the matching information, thereby reducing the burden of adjustment work in transactions.

[0025] Next, the configuration of the transaction management device 100 will be described.

[0026] FIG. 2 is a block diagram showing an example of the configuration of the transaction management device 100 according to this embodiment. Transaction management device 100 includes a communication unit 11, a memory unit 12, an input unit 13, an output unit 14, and a control unit 15.

[0027] The communication unit 11 receives various information from the orderer terminal device 200 or the contractor terminal device 300 via the network NW. In addition, the communication unit 11 transmits various information to the orderer terminal device 200 or the contractor terminal device 300 via the network NW.

[0028] The storage unit 12 is configured by, for example, a storage medium such as a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit 12 may also be configured by, for example, a non-volatile memory. The storage unit 12 stores applications, programs, various data, and the like executed by the control unit 15. The storage unit 12 includes a user data storage unit 121, a payment data storage unit 122, a billing data storage unit 123, and a matching information storage unit .

[0029] The user data storage unit 121 stores user information. The user information is information (also referred to as user information) about a user who uses the transaction management system SYS. The user information includes a user ID, a user name, a user's affiliation, a login ID, a password, and the like. The user ID is identification information for identifying a user. The user ID may be any character string that can identify a user. The user name is the name of a user associated with the user ID. The user name may be displayed when logging in using the user ID on a display screen in the transaction management system. The user's affiliation is the name of a company to which the user belongs or identification information for identifying the company. The login ID and password are an ID and password for logging in to a transaction site, and are assigned in advance to each user. These user data are registered in advance, for example, by user registration.

[0030] The payment data storage unit 122 stores payment data. The payment data is information related to payment. The payment data is information that associates a manufacturer company code, a supplier company code, a manufacturer product code, a closing date, an arrival date, a payment quantity, a payment unit price, a payment amount, and a payment location. The manufacturer company code is identification information that identifies the manufacturer who places the order. The supplier company code is identification information that identifies the supplier who receives the order. The manufacturer product code is identification information that identifies the product at the manufacturer. The closing date is date information that indicates the billing closing date. The arrival date is information that indicates the arrival date of the product. The payment quantity is information that indicates the quantity of the product to be paid for. The payment unit price is information that indicates the unit price of the product to be paid for. The payment amount is information that indicates the product price to be paid for. The payment location is information that indicates the payee to whom the product price is paid, such as identification information that identifies the payee's business establishment.

[0031] The billing data storage unit 123 stores billing data. The billing data is information related to billing. The billing data is information in which a manufacturer company code, a supplier company code, a manufacturer product code, a closing date, a delivery date, a billing quantity, a billing unit price, a billing amount, and a billing location are associated with each other. The manufacturer company code is identification information that identifies the manufacturer who places the order. The supplier company code is identification information that identifies the supplier who receives the order. The manufacturer product code is identification information that identifies the product at the manufacturer. The closing date is information that represents the closing date for billing. The delivery date is information that represents the delivery date when the product is delivered. The billing quantity is information that represents the quantity of the product that is the subject of the billing. The billing unit price is information that represents the unit price of the product that is the subject of the billing. The billing amount is information that represents the price of the product that is the subject of the billing. The billing location is information that represents the billing destination to which the product price is billed, such as identification information that identifies the business establishment of the billing destination.

[0032] The matching information storage unit 124 stores the matching information. The matching information is information in which payment data and billing data are associated with each other. The matching information also includes information on the matching result by the purchaser or the seller.

[0033] The input unit 13 has a function of accepting input. The input unit 13 accepts information input by an input device such as a mouse, a keyboard, or a touch panel that is provided as hardware in the transaction management device 100. The input unit 13 outputs the input information to the control unit 15.

[0034] The output unit 14 has a function of outputting various information. The output unit 14 is realized, for example, by a display device such as a display or a touch panel, or an audio output device such as a speaker, which are provided as hardware in the transaction management device 100. The output unit 14 outputs, for example, an image or a sound in response to an input from the control unit 15.

[0035] Control unit 15 has a function of controlling the overall operation of transaction management device 100. Control unit 15 is realized, for example, by causing a CPU (Central Processing Unit) provided as hardware in transaction management device 100 to execute a program. The control unit 15 includes a payment data acquisition unit 151, a billing data acquisition unit 152, and a matching information generation unit 153.

[0036] The payment data acquisition unit 151 acquires payment data from the orderer terminal device 200 via the communication unit 11. The payment data acquisition unit 151 stores the acquired payment data in the payment data storage unit 122.

[0037] The billing data acquisition unit 152 acquires billing data from the contractor terminal device 300 via the communication unit 11. The billing data acquisition unit 152 causes the billing data storage unit 123 to store the acquired billing data.

[0038] The matching information generating unit 153 reads the payment data from the payment data storage unit 122 and reads the billing data from the billing data storage unit 123. The matching information generating unit 153 generates the matching information by associating the read payment data with the billing data. Specifically, the matching information generating unit 153 generates the matching information by associating the payment data with information of each item in the billing data. The matching information generating unit 153 generates the matching information so that the contractor or the purchaser can confirm the items that match between the payment data and the billing data and the items that differ between the payment data and the billing data. For example, the matching information generating unit 153 generates the matching information so that the text color of the different items can be presented using a text color different from the text color of the matching items. The matching information generating unit 153 stores the generated matching information in the matching information storage unit 124.

[0039] The matching information generating unit 153 acquires search information from the purchaser terminal device 200 or the contractor terminal device 300 via the communication unit 11. The search information is information for searching payment data and billing data. The search information includes at least one of the following information, for example: closing date, payment date, matching status, classification, supplier company code, ordering company name, order receiving company code, order receiving company name, etc.

[0040] Here, the matching status is information that indicates the state of the payment data and billing data, such as unmatched, matched, manufacturer matched, supplier matched, etc. In other words, the matching status is information that indicates the matching result. Unmatched indicates a state in which neither the manufacturer nor the supplier has matched the billing data with the payment data. Matched indicates a state in which the billing data and payment data have been matched at both the manufacturer and the supplier. Manufacturer matched indicates a state in which the billing data and payment data have been matched at the manufacturer. Supplier matched indicates a state in which the billing data and payment data have been matched at the supplier.

[0041] The category is information that indicates the category of the product, such as paper container, plastic, cardboard, etc.

[0042] When the matching information generating unit 153 acquires the search information, it reads out matching information corresponding to the search information from the matching information storage unit 124. The matching information generating unit 153 transmits the matching information to the purchaser terminal device 200 or the contractor terminal device 300 via the communication unit 11.

[0043] When the matching status is updated in the matching information transmitted to the orderer terminal device 200 or the contractor terminal device 300, the matching information generation unit 153 updates the matching information stored in the matching information storage unit 124. The matching information generation unit 153 stores the updated matching information in the matching information storage unit 124.

[0044] Next, an example of payment data will be described.

[0045] FIG. 3 is a diagram showing an example of order information according to the present embodiment. As described above, the order information according to this embodiment is payment data. The payment data is information in which a manufacturer company code, a supplier company code, a manufacturer product code, a closing date, a delivery date, a payment quantity, a payment price, a payment amount, and a payment location are associated with each other. In the example shown, the payment data has a "manufacturer company code" of "XXX", a "supplier company code" of "YYY", a "manufacturer product code" of "makeritem1", a "closing date" of "4 / 20 / 2022", a "received date" of "3 / 30 / 2022", a "payment quantity" of "2000", a "payment price" of "500", a "payment amount" of "1000000", and a "payment location" of "Warehouse A". Here, in the "payee" field, for example, the payee's establishment name, payee's establishment code, etc. are stored.

[0046] Next, an example of the billing data will be described.

[0047] FIG. 4 is a diagram showing an example of order information according to the present embodiment. As described above, the order information according to this embodiment is billing data. The billing data is information in which a manufacturer company code, a supplier company code, a manufacturer product code, a closing date, a delivery date, a billed quantity, a billed unit price, and a billed amount are associated with each other. In the example shown, the billing data has a "manufacturer company code" of "XXX", a "supplier company code" of "YYY", a "manufacturer product code" of "makeritem1", a "closing date" of "4 / 20 / 2022", a "delivery date" of "3 / 30 / 2022", a "billing quantity" of "2500", a "billing unit price" of "500", a "payment amount" of "1,250,000", and a "billing location" of "Warehouse A".

[0048] Next, examples of display screens will be described.

[0049] 5 to 8 are diagrams showing examples of display screens according to this embodiment. The example shown in FIG. 5 is an example of a display screen that is displayed when search information is entered in a web browser after a user ID and password have been entered. In the illustrated example, input windows are displayed for each item of search information, such as "Closing date," "Date range," "Delivery location," "Supplier," "Verification status," and "Classification." In addition, operators are displayed for narrowing down the search target of verification information to either "Payment request" or "Arrival already received." When search information is entered into an input window for at least one or more items in the purchaser terminal device 200 or the contractor terminal device 300, and the ``search'' operator is selected, the transaction management device 100 reads out matching information corresponding to the entered search information from the matching information memory unit 124.

[0050] FIG. 6 is an example of a display screen displayed after FIG. The example shown in FIG. 6 is an example in which, in addition to each input window for search information shown in FIG. 5 and the information input in the input window, collation information corresponding to the search information is displayed. The verification information in the illustrated example is displayed when the manufacturer inputs search information, and is verification information related to payments to three suppliers, "Supplier 1," "Supplier 2," and "Supplier 3," corresponding to the manufacturer's search information. The illustrated verification information associates a verification status, a total quantity, and a total amount for each ordering company, i.e., each of the supplier companies, "Supplier 1," "Supplier 2," and "Supplier 3." The total quantity displays the paid quantity and the invoiced quantity so that they can be compared, and the total amount displays the paid amount and the invoiced amount so that they can be compared. The illustrated verification information also includes a grand total calculated by adding up the total quantities and total amounts for each supplier. The grand total includes the sum of the paid quantity, invoiced quantity, paid amount, and invoiced amount.

[0051] In the illustrated example, the quantities and amounts that differ between payment and invoice are displayed in a different display format from items that do not have discrepancies, so that the discrepancies can be visually recognized. Furthermore, in the reconciliation status, items for which reconciliation has not been completed, i.e., reconciliation statuses that have not been reconciled, for example, supplier reconciled and unreconciled reconciliation statuses, are displayed in a different display format from the reconciled reconciliation status, so that the items can be visually recognized as not being completed.

[0052] In addition, when one of the company names "Supplier 1," "Supplier 2," or "Supplier 3" is selected in the summary display for each supplier in FIG. 6, the details of the matching information for the selected supplier are displayed.

[0053] FIG. 7 shows an example of a case where, in the example shown in FIG. 6, an operation is performed to select the operator for "Supplier 1," and a link item corresponding to that operator is displayed, and details of "Supplier 1" are displayed. 7, for each product, for example, for each product name corresponding to a product ID, the billed quantity, payment quantity, billed amount, and payment amount are displayed in a list by arrival date (or shipping date). In this list display, items where there is a difference between the billed quantity and payment quantity, or the billed amount and payment amount, are displayed in a different display mode from items where there is no difference, so that the difference can be visually recognized. In this way, the orderer or the contractor can confirm which item has the discrepancy.

[0054] Here, when one of the product names "Manufacturer's Product 1," "Manufacturer's Product 2," or "Manufacturer's Product 3" is selected in the summary display for each product name in FIG. 7, a breakdown of the verification information for the selected product is displayed.

[0055] FIG. 8 shows an example of a case where an operation to select an operator for "Manufacturer's Product 2" is performed in the example shown in FIG. 7, and a link item corresponding to the operator is displayed, and details of "Manufacturer's Product 2" are displayed. In the illustrated example, reconciliation information including each of the items invoiced quantity, invoiced unit price, invoiced amount, paid quantity, paid unit price, and paid amount is displayed in detail for each "date." In this detailed display, the invoiced quantity and paid quantity, the invoiced unit price and paid unit price, and the invoiced amount and paid amount are displayed so that they can be compared. Items where there is a difference between the invoiced quantity and paid quantity, the invoiced unit price and paid unit price, and the invoiced amount and paid amount are displayed in a different display mode from items where there is no difference, so that the existence of a difference can be visually recognized.

[0056] Here, in each of the display screen examples of Figures 6, 7, and 8, to make it possible to visually see any discrepancies between each payment item and each billing item, for example, as shown in Figures 6, 7, and 8, the text of the items where there are discrepancies is displayed in bold. Instead of or in addition to displaying the text of items where differences occur in bold, the text color or font size may be changed, or the text may be displayed in a different manner from that of items where differences do not occur.

[0057] Next, the flow of the transaction management process according to this embodiment will be described.

[0058] FIG. 9 is a sequence diagram showing an example of a transaction management process in the transaction management system SYS according to this embodiment. In step ST101, purchaser terminal device 200 transmits login information including a user ID and a password for connecting to transaction management system SYS to transaction management device 100 by inputting the information into, for example, a Web browser.

[0059] In step ST102, the transaction management device 100 checks whether the login information matches the login information stored in the user data storage unit 121, and transmits purchaser management information corresponding to the user information included in the login information to the purchaser terminal device 200. The purchaser management information is, for example, an input screen for search information for the purchaser's verification information, a payment data upload screen, and the like.

[0060] In step ST103, purchaser terminal device 200 transmits the payment data to transaction management device 100 by uploading the payment data file input by the purchaser's operation.

[0061] In step ST104, the order taker terminal device 300 transmits login information, including a user ID and password for connecting to the transaction management system SYS, to the transaction management device 100 by inputting the login information into, for example, a web browser.

[0062] In step ST105, the transaction management device 100 checks whether the login information matches the login information stored in the user data storage unit 121, and transmits the contractor management information corresponding to the user information included in the login information to the contractor terminal device 300. The contractor management information is, for example, an input screen for search information for the contractor's verification information, a screen for uploading billing data, and the like.

[0063] In step ST106, the contractor terminal device 300 transmits the billing data to the transaction management device 100 by uploading the billing data file input by the contractor operation.

[0064] In step ST107, the vendor terminal device 300 accepts the search information input from the vendor, and transmits the accepted search information to the transaction management device 100.

[0065] In step ST108, transaction management device 100 reads out matching information corresponding to the search information from matching information storage unit 124 based on the search information. Transaction management device 100 transmits the read matching information to vendor terminal device 300.

[0066] In step ST109, the contractor terminal device 300 displays the verification information and accepts the verification result of the verification information by the contractor.

[0067] In step ST110, when the matching status is updated as a matching result from the seller, the seller terminal device 300 transmits information on the updated matching status to the transaction management device 100.

[0068] In step ST111, purchaser terminal device 200 accepts input of search information from the purchaser, and transmits the accepted search information to transaction management device 100.

[0069] In step ST112, transaction management device 100 reads out matching information corresponding to the search information from matching information storage unit 124 based on the search information. Transaction management device 100 transmits the read matching information to purchaser terminal device 200.

[0070] In step ST113, the purchaser terminal device 200 displays the collation information and accepts the result of the collation of the collation information by the purchaser.

[0071] In step ST114, when the matching status is updated as a matching result from the purchaser, purchaser terminal device 200 transmits information on the updated matching status to transaction management device 100.

[0072] The processes from step ST104 to step ST106 may be performed before the processes from step ST101 to step ST103. Either or both of the processes from step ST101 to step ST103 and the processes from step ST104 to step ST106 may be performed at a timing different from the timing of the processes from step ST107 onward.

[0073] Furthermore, the processes from step ST111 to step ST114 may be performed before the processes from step ST107 to step ST110. The processes from step ST107 to step ST110 and the processes from step ST111 to step ST114 may be performed at different timings.

[0074] FIG. 10 is a flowchart showing an example of a transaction management process in the transaction management device 100 according to this embodiment. In step S101 , transaction management device 100 acquires search information from purchaser terminal device 200 or seller terminal device 300 .

[0075] In step S102, the transaction management device 100 obtains corresponding matching information from the matching information storage unit 124 based on the search information.

[0076] In step S103, transaction management device 100 transmits the matching information to purchaser terminal device 200 or seller terminal device 300 that has accepted the search information.

[0077] In step S104, the transaction management device 100 acquires the result of matching against the matching information from the purchaser terminal device 200 or the seller terminal device 300.

[0078] Thus, the transaction management system SYS of this embodiment comprises an order information acquisition unit (payment data acquisition unit 151) that acquires order information from the orderer terminal device 200, an order information acquisition unit (billing data acquisition unit 152) that acquires order information from the contractor terminal device 300, a search information acquisition unit (matching information generation unit 153) that acquires search information, and a generation unit (matching information generation unit 153) that generates matching information including order information and order information corresponding to the search information.

[0079] This allows the payment data to be compared with the billing data, thereby reducing the burden of adjustment work in transactions.

[0080] Although each embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes, etc. are possible within the scope that does not deviate from the gist of the present invention.

[0081] For example, in each of the above-described embodiments, an example configured using transaction management device 100 has been described, but one aspect of the present invention may also be realized using multiple devices including other devices that can realize part of transaction management device 100.

[0082] In addition, the program that runs on the transaction management device 100 in one aspect of the present invention may be a program that controls one or more processors such as a CPU (Central Processing Unit) so as to realize the functions shown in each of the above-mentioned embodiments and modifications related to one aspect of the present invention (a program that makes a computer function). The computer here also includes a quantum computer. The information handled by each of these devices is temporarily stored in a RAM (Random Access Memory) during processing, and then stored in various storage devices such as a flash memory or an HDD (Hard Disk Drive), and may be read, modified, or written by the CPU or the like as necessary.

[0083] In addition, a part or the whole of the transaction management device 100 in each of the above-mentioned embodiments and modifications may be realized by a computer having one or more processors. In that case, the program for realizing the control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to realize the control function.

[0084] The term "computer system" as used herein refers to a computer system built into the transaction management device 100, and includes hardware such as the OS and peripheral devices. Also, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.

[0085] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that stores a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such a case. The above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0086] Also, a part or all of the transaction management device 100 in each of the above-mentioned embodiments and modifications may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Also, each functional block of the transaction management device 100 in each of the above-mentioned embodiments and modifications may be individually formed into a chip, or may be integrated into a chip in part or in whole. Also, the integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit and / or a general-purpose processor. Also, if an integrated circuit technology that can replace LSI appears due to advances in semiconductor technology, it is possible to use an integrated circuit based on that technology.

[0087] Although the embodiments and modifications have been described above in detail with reference to the drawings as one aspect of the present invention, the specific configuration is not limited to the embodiments and modifications, and includes design changes within the scope of the gist of the present invention. In addition, one aspect of the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in the above embodiments and modifications are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0088] SYS Transaction Management System 100 Transaction management device 11 Communications Department 12 Storage section 121 User data storage unit 122 Payment data storage unit 123 Billing data storage unit 124 Matching information storage unit 13 Input section 14 Output section 15 Control section 151 Payment Data Acquisition Department 152 Billing Data Acquisition Department 153 Matching information generation unit 200 Orderer terminal device 300 Order-receiving terminal device

Claims

1. an order information acquisition unit that acquires order information from the orderer terminal device; an order information acquisition unit that acquires order information from an order recipient terminal device; a search information acquisition unit that acquires search information; a generation unit that generates matching information including the order information and the order receipt information corresponding to the search information; A transaction management system comprising:

2. the generating unit generates verification information indicating that the numerical information does not match when the numerical information included in the order information corresponding to the search information does not match the numerical information included in the order information corresponding to the search information. The transaction management system according to claim 1 .

3. The order information is payment data including at least the quantity of the product to be paid and the unit price of the product, The order information is billing data including at least the quantity of the product to be billed and the unit price of the product. The transaction management system according to claim 2 .

4. an order information acquisition unit that acquires order information from the orderer terminal device; an order information acquisition unit that acquires order information from an order recipient terminal device; a search information acquisition unit that acquires search information; a generation unit that generates matching information including the order information and the order receipt information corresponding to the search information; A transaction management device comprising:

5. 1. A computer-implemented method for managing transactions, comprising: an order information acquisition step of acquiring order information from an orderer terminal device; an order information acquisition step of acquiring order information from an order recipient terminal device; a search information acquisition process for acquiring search information; a generation step of generating matching information including the order information and the order receipt information corresponding to the search information; A transaction management method having the above.

6. On the computer, an order information acquisition step of acquiring order information from an orderer terminal device; an order information acquisition unit step of acquiring order information from the order recipient terminal device; a search information acquisition step of acquiring search information; a generating step of generating matching information including the order information and the order receipt information corresponding to the search information; A program to execute.

Images