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

Abstract

To reduce the workload when information on issued business documents are modified.SOLUTION: An information processing device is provided, comprising: a first registration unit configured to register information on a business document of a first type according to first input information from a terminal deice used by a first user; a display control unit configured to make a terminal device used by a second user display an input screen for receiving input of information on a business document of a second type corresponding to the business document of the first type in accordance with the information on the business document of the first type; and a second registration unit configured to register the information on the document of the second type according to second input information entered on the input screen. When information not matching the information on the business document of the first type corresponding to the business document of the second type is present in the second input information, the display control unit makes the terminal device used by the second user display a registration screen for registering notification information on the unmatched information.SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] 2. Description of the Related Art Transactions are collated between a party that provides goods or services (hereinafter referred to as the seller) and a party that uses the goods or services (hereinafter referred to as the buyer) using documents such as purchase orders and invoices.

[0003] For example, a system is known in which purchase detail data and invoice detail data are automatically matched to create a list of items that have not been matched due to document submission errors, and for items on the unmatched list, both parties confirm the cause and manually process the items to confirm payment (see, for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] For example, when a seller issues an invoice to a buyer, the invoice amount may be changed from the amount stated on the purchase order due to a price increase, decrease, discount, shortage, etc. In such cases, the amount stated on the invoice and the amount stated on the purchase order may not match, resulting in a problem in which the buyer cannot match the purchase order and the invoice.

[0005] In such a case, for example, the seller could reissue a purchase order that matches the changed amount, but this would be extremely time-consuming.Also, the buyer and seller could exchange emails or phone calls regarding the change in amount, and the buyer could enter and manage the details of the exchange as additional information on the purchase order, but this would still be time-consuming.

[0006] Similar issues arise not only when a seller issues an invoice to a buyer, but also when the order details listed on a purchase order are changed when the seller issues an invoice to a buyer, or when the quotation details listed on a quotation are changed when the buyer issues an order to a seller.

[0007] An embodiment of the present invention has been made in consideration of the above problems, and reduces the workload when information on a form to be issued is changed. [Means for solving the problem]

[0008] In order to solve the above problem, an information processing device according to one embodiment of the present invention has a first registration unit that registers information of a first type of form based on first input information from a terminal device used by a first user, a display control unit that displays an input screen on a terminal device used by a second user that accepts input of information of a second type of form corresponding to the first type of form based on the information of the first type of form, and a second registration unit that registers the information of the second type of form based on second input information input to the input screen, and when the second input information contains information that does not match the information of the first type of form corresponding to the second type of form, the display control unit displays a registration screen on the terminal device used by the second user that registers notification information regarding the mismatched information. Effect of the Invention

[0009] According to one embodiment of the present invention, it is possible to reduce the workload when information on a form to be issued is changed. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system according to an embodiment. [Diagram 2] FIG. 1 is a diagram for explaining an overview of a transaction flow according to an embodiment. [Diagram 3]FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer according to an embodiment. [Figure 4] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. [Diagram 5] A diagram showing an example of transaction management information according to one embodiment. [Figure 6] FIG. 13 is a diagram illustrating an example of tenant management information according to an embodiment. [Figure 7] FIG. 11 is a sequence diagram illustrating an example of an order process according to an embodiment. [Figure 8] FIG. 13 is a diagram illustrating an example of a screen for creating an order form according to an embodiment. [Figure 9] FIG. 13 is a diagram illustrating an example of a purchase order sending screen according to an embodiment. [Figure 10] FIG. 2 is a diagram illustrating an example of an order DB according to an embodiment. [Figure 11] FIG. 13 is a diagram illustrating an example of a purchase order receipt screen according to an embodiment. [Figure 12] FIG. 13 is a diagram illustrating an example of a receipt order DB according to an embodiment. [Figure 13] FIG. 11 is a sequence diagram illustrating an example of a billing process according to an embodiment. [Figure 14] FIG. 13 is a diagram illustrating an example of a receipt order list screen according to an embodiment. [Figure 15] FIG. 1 shows an example of an invoice creation screen according to one embodiment. [Figure 16] FIG. 2 shows an example of an invoice creation screen according to an embodiment. [Figure 17] 11 is a flowchart illustrating an example of an invoice editing process according to an embodiment. [Figure 18] FIG. 13 is a diagram illustrating an example of a registration screen for notification information according to an embodiment. [Figure 19] 13 is a flowchart illustrating another example of an invoice editing process according to an embodiment. [Figure 20] FIG. 13 is a diagram showing another example of the registration screen for notification information according to an embodiment. [Figure 21] FIG. 1 illustrates an example of an invoice according to an embodiment. [Figure 22] FIG. 13 is a diagram showing an example of an invoice sending screen according to an embodiment. [Figure 23] FIG. 2 is a diagram illustrating an example of an issued invoice DB according to an embodiment. [Figure 24] 11A and 11B are diagrams illustrating examples of issue notification information and receipt notification information according to an embodiment. [Diagram 25] FIG. 13 is a diagram illustrating an example of a received invoice DB according to an embodiment. [Figure 26] 11 is a flowchart illustrating an example of a matching process according to an embodiment. [Figure 27] FIG. 11 is a sequence diagram illustrating an example of a confirmation process according to an embodiment. [Figure 28] FIG. 13 is a diagram illustrating an example of an invoice list screen according to an embodiment. [Figure 29] FIG. 13 is a diagram illustrating an example of a confirmation screen according to an embodiment. [Diagram 30] FIG. 11 is a diagram illustrating an example of notification information according to an embodiment. [Diagram 31] 13A and 13B are diagrams illustrating another example of a confirmation screen and notification information according to an embodiment. [Diagram 32] FIG. 11 is a diagram illustrating an example of output information according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0012] <System configuration> 1 is a diagram showing an example of a system configuration of an information processing system according to an embodiment. The information processing system 1 is a system that manages transactions carried out between a party that provides a product or service (hereinafter referred to as a seller) and a party that uses the provided product or service (hereinafter referred to as a buyer) using documents such as purchase orders and invoices. The information processing system 1 has a transaction management system 100, a terminal device 101, and a terminal device 102 that are communicatively connected to each other via a communication network 2 such as the Internet or a LAN (Local Area Network).

[0013] The transaction management system (information processing device) 100 is an information processing device having a computer configuration, or a system including multiple information processing devices. The transaction management system 100 has a function of a web server that manages transactions between sellers and buyers, for example, by providing an input screen (web page, etc.) for inputting information on forms such as purchase orders (or purchase orders) and invoices. The transaction management system 100 also has a function of storing and managing the form information entered on the input screen in a storage unit, etc.

[0014] The terminal device 101 is an information terminal having a web browser function, such as a PC (Personal Computer), a tablet terminal, or a smartphone, used by a user (first user) on the buyer 10 side. The user on the buyer 10 side is not limited to one user, but may include one or more users having a predetermined role in the organization of the buyer 10 side. Furthermore, the terminal device 101 may be any terminal used by the user on the buyer 10 side. For example, the terminal device 101 may be a shared terminal used by the user on the buyer 10 side, or may be a personal terminal. Therefore, the terminal device 101 used by the user (first user) on the buyer 10 side is not limited to one terminal, and a different terminal may be used each time the transaction management system 100 is accessed.

[0015] In addition, the terminal device 101 used by the user on the buyer 10 side is also used when exchanging information with a core system 3 such as an accounting system, a settlement system, or an order / receive system, directly or via the transaction management system 100.

[0016] The terminal device 102 is an information terminal having a web browser function, such as a PC, a tablet terminal, or a smartphone, used by a user (second user) on the seller 20 side. The user on the seller 20 side is not limited to one user, and may include one or more users having a predetermined role in the organization of the seller 20 side. Furthermore, the terminal device 102 may be any terminal used by the user on the seller 20 side. For example, the terminal device 102 may be a shared terminal used by the user on the seller 20 side, or may be a personal terminal. Therefore, the terminal device 102 used by the user (second user) on the seller 20 side is not limited to one terminal, and a different terminal may be used each time the transaction management system 100 is accessed.

[0017] The core system 3 is a business system, such as an accounting system, a settlement system, or an order receiving and placing system, used by the organization of the buyer 10, and in this embodiment, is assumed to be a system external to the information processing system 1. However, this is not limited to this, and for example, at least a part of the functions of the core system 3 may be included in the information processing system 1.

[0018] (Outline of transaction flow) 2 is a diagram for explaining an outline of a transaction flow according to an embodiment. Note that, in this embodiment, documents such as a quotation, a purchaser (or a purchase order), and an invoice are transmitted and received as electronic data.

[0019] For example, in response to a request for quotation from the buyer 10, the seller 20 sends a quotation to the buyer 10 including information such as the item, unit price, quantity, and total amount of the requested product (or service) (step S1).

[0020] Based on the quotation, the buyer 10 determines the items, unit price, quantity, etc. of the products to be ordered, and transmits an order form (or purchase order) or the like including this information to the seller 20 (step S2). The order amount, which is the total amount of the order forms, is registered in the accounting system 201, which is a part of the core system 3, for example, as accounts payable, which is an accounting item.

[0021] Thereafter, the seller 20 provides the goods, etc. ordered by the orderer, etc. to the buyer 10, and then sends an invoice to the buyer 10 including information such as the item, unit price, quantity, and total amount of the provided goods, etc. (step S3).

[0022] When the buyer 10 receives the invoice, it checks (compares) the information on the order form (e.g., order amount, etc.) against the information on the invoice (e.g., invoice amount, etc.), and if there are no errors between the information on the order form and the information on the invoice, it makes payment to the seller 20 (step S4).

[0023] Here, "matching" refers to, for example, comparing information on a purchase order or the like (e.g., item, unit price, quantity, total amount, etc.) with information on an invoice (e.g., item, unit price, quantity, total amount, etc.) to check for errors in the information. Basically, "matching" is used in the same sense as "collation," but it can also mean, for example, when the two pieces of information do not match, investigating where the error is and making the two consistent, so "collation" is used in the following explanation.

[0024] If there is a discrepancy between the information on the order form and the information on the invoice, the buyer 10 cannot make the payment. In such a case, for example, in the conventional technology shown in Patent Document 1, the buyer 10 and the seller 20 confirm the cause of the discrepancy between the information on the order form and the information on the invoice, and then the payment is finalized by manually processing the discrepancy.

[0025] Therefore, in the conventional system, if the seller 20 changes the invoice amount for some reason, the buyer 10 contacts the seller 20 to confirm the reason for the change in the amount, and then performs the payment process. Thus, in the conventional technology, in the information processing system 1 that collates the forms issued by the buyer 10 and the forms issued by the seller 20, if the invoice amount is changed by the seller 20, the workload of the buyer 10 increases.

[0026] Therefore, the transaction management system 100 according to this embodiment determines whether or not information such as the amount stated on the purchase order has been changed when the seller 20 creates an invoice, and if so, has the seller 20 register notification information regarding the change. Furthermore, the transaction management system 100 enables the notification information regarding the change entered by the seller 20 to be displayed on the buyer's 10 terminal device 101 when the buyer 10 receives the invoice. This allows the buyer 10 to easily determine the appropriateness of the invoice amount when the seller 20 changes the amount on the invoice, without having to contact the seller 20.

[0027] Thus, according to this embodiment, in the information processing system 1 which compares documents issued by the buyer 10 with documents issued by the seller 20, the workload on the buyer's side can be reduced when the invoice amount is changed.

[0028] <Hardware configuration> The terminal device 101, the terminal device 102, and the transaction management system 100 each have the hardware configuration of a general computer 300, for example, as shown in Figure 3. Alternatively, the transaction management system 100 is composed of multiple computers 300.

[0029] Fig. 3 is a diagram showing an example of a hardware configuration of a computer according to an embodiment. For example, as shown in Fig. 3, a computer 300 includes a CPU (Central Processing Unit) 301, a ROM (Read Only Memory) 302, a RAM (Random Access Memory) 303, a HD (Hard Disk) 304, a HDD (Hard Disk Drive) controller 305, a display 306, an external device connection I / F (Interface) 307, a network I / F 308, a keyboard 309, a pointing device 310, a DVD-RW (Digital Versatile Disk Rewritable) drive 312, a media I / F 314, and a bus line 315.

[0030] Of these, the CPU 301 controls the overall operation of the computer 300. The ROM 302 stores programs used to start up the CPU 301, such as an IPL (Initial Program Loader). The RAM 303 is used as a work area for the CPU 301. The HD 304 stores various data such as programs. The HDD controller 305 controls reading and writing of various data from and to the HD 304 under the control of the CPU 301.

[0031] The display 306 displays various information such as a cursor, a menu, a window, characters, or an image. The external device connection I / F 307 is an interface for connecting various external devices. In this case, the external devices include, for example, a USB (Universal Serial Bus) memory, a printer, etc. The network I / F 308 is an interface for data communication using the communication network 2.

[0032] The keyboard 309 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. The pointing device 310 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 312 controls reading and writing of various data from a DVD-RW 311 as an example of a removable recording medium. The DVD-RW 311 may be another removable recording medium. The media I / F 314 controls reading and writing (storing) of data from a medium 313 such as a flash memory. The bus line 315 is an address bus, a data bus, various control signals, etc. for electrically connecting the above-mentioned components.

[0033] <Functional configuration> FIG. 4 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment.

[0034] (Functional configuration of transaction management system) The transaction management system (information processing device) 100 realizes a functional configuration as shown in Fig. 4, for example, by executing a predetermined program on a computer 300 as shown in Fig. 3, or on multiple computers 300. In the example of Fig. 4, the transaction management system 100 has a communication unit 401, a memory unit 402, a display control unit 403, a first registration unit 404, a second registration unit 405, an information transmission unit 406, and a matching unit 407. Note that at least a portion of the above functional configurations may be realized by hardware.

[0035] The communication unit 401, for example, uses the network I / F 308, etc. to connect the transaction management system 100 to the communication network 2, and executes communication processing to communicate with the terminal devices 101, 102, the core system 3, etc.

[0036] The storage unit 402 executes a storage process for storing various information such as transaction management information and tenant management information in a storage device such as the HD 304.

[0037] 5 is a diagram showing an example of transaction information according to an embodiment. The storage unit 402 stores transaction management information 500, such as an issued purchase order DB (Database) 501, a received purchase order DB 502, an issued invoice DB 503, and a received invoice DB (Database) 504, for each tenant that is a contractor such as a company.

[0038] 5, transaction management information 500a of Company A, which is an example of the buyer 10, includes an issued order DB 501a, a received order DB 502a, an issued invoice DB 503a, and a received invoice DB 504a, etc. Also, transaction management information 500b of Company B, which is an example of the seller 20, includes an issued order DB 501b, a received order DB 502b, an issued invoice DB 503b, and a received invoice DB 504b, etc.

[0039] For example, the transaction management system 100 registers information on a purchase order issued by a user of Co., Ltd. A to Co., Ltd. B in the issued purchase order DB 501a. In addition, when a user of Co., Ltd. B performs a receiving operation on the purchase order, the transaction management system 100 copies the information on the purchase order from the issued purchase order DB 501a to the received purchase order DB 502b. Similarly, the transaction management system 100 registers information on an invoice issued by a user of Co., Ltd. B to Co., Ltd. A in the issued invoice DB 503b. In addition, when a user of Co., Ltd. A performs a receiving operation on the invoice, the transaction management system 100 copies the information on the invoice from the issued invoice DB 503b to the received invoice DB 504a. Incidentally, Co., Ltd. A and Co., Ltd. B can be either buyers 10 or sellers 20.

[0040] 5 is an example. For example, the transaction management system 100 may store the transaction management information of each tenant in common transaction management information and identify the information of each tenant by identification information for identifying the tenant.

[0041] FIG. 6 shows an example of tenant management information according to an embodiment. The storage unit 402 stores information on each tenant in, for example, tenant management information 600 as shown in FIG. 6. In the example of FIG. 6, the tenant management information 600 includes information such as a tenant name (company name), a "user ID", a "password", an "email address", and "account information". The "tenant name" is information indicating the name of a tenant, such as a company name. The tenant name may be a tenant ID or the like for identifying a tenant. The "user ID" is identification information for identifying a user registered in each tenant. The "password" is an example of authentication information for a user corresponding to the user ID. The "email address" is an email address of a user corresponding to the user ID. The "account information" is information on the transfer destination of each tenant. The tenant management information 600 is, for example, registered in advance in the transaction management system 100 by an administrator or the like who manages the transaction management system 100.

[0042] Returning now to FIG. 4, the explanation of the functional configuration of the transaction management system 100 will be continued.

[0043] The display control unit 403 executes a display control process for displaying display screens for inputting various information related to a transaction on the terminal device 101 used by a user on the buyer 10 side and the terminal device 102 used by a user on the seller 20 side. For example, the display control unit 403 displays various display screens such as an order form creation screen, an order form sending screen, an invoice list screen, an invoice confirmation screen, and notification information on the terminal device 101 used by a user on the buyer 10 side (hereinafter referred to as a buyer user). The buyer user is an example of a first user.

[0044] The display control unit 403 also causes the terminal device 102 used by the user of the seller 20 (hereinafter referred to as the seller user) to display various display screens such as a purchase order receipt screen, a received purchase order list screen, an invoice creation screen, an invoice sending screen, and notification information. The seller user is an example of a second user.

[0045] For example, the display control unit 403 creates an invoice creation screen corresponding to the order form based on the order form information registered in the received order form DB 502, and displays the created invoice creation screen on the terminal device 102. Furthermore, when the input information entered on the invoice creation screen contains information that does not match the order form information corresponding to the invoice, the display control unit 403 displays on the terminal device 102 a registration screen for registering notification information related to the mismatched information (for example, the reason for the mismatch, etc.).

[0046] As a specific example, the display control unit 403 functions as a web server that causes the web browsers of the terminal device 101, the terminal device 102, etc. to display web pages that accept input of various information related to transactions.

[0047] The first registration unit 404 executes a first registration process for registering information on a first type of form based on input information on an input screen for accepting input of information on a first type of form, which is displayed on the terminal device 101 by the display control unit 403. For example, the first registration unit 404 registers purchase order information in the issued purchase order DB 501 based on input information input by a buyer user on a purchase order creation screen, which is displayed on the terminal device 101 by the display control unit 403.

[0048] The second registration unit 405 executes a second registration process for registering information on a second type of form based on input information on an input screen that accepts input of information on a second type of form and that the display control unit 403 causes to be displayed on the terminal device 102. For example, the second registration unit 405 registers invoice information in the issued invoice DB 503 based on input information input by a seller user on an invoice creation screen that the display control unit 403 causes to be displayed on the terminal device 102. In addition, the second registration unit 405 registers notification information input on the registration screen in the issued invoice DB 503 in association with the invoice information.

[0049] The information transmitting unit 406 executes an information transmitting process for transmitting various information to, for example, the terminal device 101, the terminal device 102, or the core system 3. For example, in response to a purchase order delivery request from a buyer user, the information transmitting unit 406 transmits an e-mail to the terminal device 102 used by the seller user to display a receipt screen for the purchase order. In addition, in response to a seller user request to send an invoice, the information transmitting unit 406 transmits an e-mail to the terminal device 101 used by the buyer user to display a receipt screen for the invoice.

[0050] The collation unit 407 executes a collation process for collating invoice information with information on a purchase order corresponding to the invoice, and registers the collation result in the received invoice DB 504 or the like.

[0051] (Functional configuration of terminal device 101) The terminal device 101 realizes a functional configuration as shown in Fig. 4 by executing a predetermined program such as a web browser or an application program (hereinafter, referred to as an app) having the function of a web browser, by the CPU 301 in Fig. 3. In the example of Fig. 4, the terminal device 101 has a communication unit 411, a display unit 412, an operation reception unit 413, etc. Note that at least a part of the above functional configurations may be realized by hardware.

[0052] The communication unit 411, for example, uses the network I / F 308, etc. to connect the terminal device 101 to the communication network 2, and executes communication processing to communicate with the transaction management system 100, the core system 3, etc.

[0053] The display unit 412 is realized, for example, by a web browser executed by the CPU 301, and executes display processing to display web pages and the like provided by the display control unit 403 of the transaction management system 100.

[0054] Operation acceptance unit 413 is realized by, for example, a web browser executed by CPU 301, and accepts user input operations for a web page displayed by display unit 412, etc.

[0055] (Functional configuration of terminal device 102) The terminal device 102 realizes a functional configuration as shown in Fig. 4 by, for example, executing a predetermined program such as a web browser or an application having the function of a web browser on the CPU 301 in Fig. 3. In the example of Fig. 4, the terminal device 102 has a communication unit 421, a display unit 422, an operation reception unit 423, etc. Note that the functions of the communication unit 421, the display unit 422, and the operation reception unit 423 are similar to those of the communication unit 411, the display unit 412, and the operation reception unit 413 of the terminal device 101, and therefore a description thereof will be omitted here.

[0056] It should be noted that the core system 3 is assumed to utilize a system external to the information processing system 1, and is not involved in the processing of the transaction management method according to the embodiment, so a description thereof will be omitted here.

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

[0058] (Order Processing) Fig. 7 is a sequence diagram showing an example of order processing according to one embodiment. This process shows an example of order processing executed by the information processing system 1 when a buyer user (first user) uses the terminal device 101 to register a purchase order in the transaction management system 100. At the start of the process shown in Fig. 7, the buyer user is using the terminal device 101 to display, for example, a purchase order creation screen 800 as shown in Fig. 8, which is provided by the display control unit 403 of the transaction management system 100.

[0059] In step S701, the buyer user inputs predetermined information 801 into an order form creation screen 800 and selects the create button 802, thereby instructing the transaction management system 100 to create an order form.

[0060] In step S702, when operation acceptance section 413 of terminal device 101 accepts the selection of create button 802, it transmits the information input by the buyer user (first input information) to transaction management system 100.

[0061] In step S703, the first registration unit 404 of the transaction management system 100 registers the purchase order information in the issued purchase order DB 501a in a "temporarily saved" state based on the information received from the terminal device 101. The purchase order information is an example of information of a first type of form.

[0062] In steps S704 and S705, the display control unit 403 of the transaction management system 100 generates an order form and an order form sending screen based on the order form information registered in the issued order form DB 501a, and sends the generated order form sending screen to the terminal device 101.

[0063] In step S706, the display unit 412 of the terminal device 101 displays, for example, an order form sending screen 900 as shown in FIG.

[0064] In step S707, the buyer user selects the destination email address from the delivery information input field 901 on the order form delivery screen 900, and edits the contents of the email information input field 902 as necessary. The buyer user also checks the order form image 903, and if there are no problems, selects the send button 904 to instruct the delivery of the order form.

[0065] In step S708, when the operation acceptance unit 413 of the terminal device 101 accepts the selection of the send button 904, it sends a send request to the transaction management system 100 to request the sending of the order form.

[0066] In step S709, when the first registration unit 404 of the transaction management system 100 receives a request to send the order form from the terminal device 101, it changes the status of the order form information registered in the issued order form DB 501a from ``temporarily saved'' to ``sent.''

[0067] Fig. 10 is a diagram showing an example of an issued purchase order DB according to an embodiment. In the example of Fig. 10, an issued purchase order DB 501 includes information such as items such as "purchase order number", "status", "order destination", "total amount", "consumption tax", "issuance date", "form image path", "details information", "receipt screen URL", and remarks.

[0068] "Order number" is an identification number that identifies order information. For example, in step S703 of FIG. 7, when the first registration unit 404 registers new order information in the issued order DB 501, it assigns an order number "190188" and adds it to the order information. "Status" is information that indicates the status of the order information, and for example, it shows that the order information with order number "190188" is in the "Sent" status. Order recipient is information that indicates the name of the order recipient, etc. "Total amount" is information that indicates the total amount of the order. "Consumption tax" is information that indicates the amount of consumption tax corresponding to the total amount. "Issue date" is information that indicates the issue date of the order.

[0069] "Form image path" is information indicating the storage location and file name of an order form image 903 as shown in Fig. 9, for example. "Detail information" includes one or more of detail information 1, detail information 2, ..., etc., which store the product code, product name, quantity, unit price, amount, etc. for each product, as shown in Fig. 10. "Receipt screen URL" is URL information for the seller user to display the receipt screen of the order form.

[0070] Returning now to FIG. 7, the explanation of the sequence diagram of the order process will be continued.

[0071] In step S710, the information sending unit 406 of the transaction management system 100 sends, for example, an email 1100 as shown in FIG. 11 to the destination email address accepted on the order form sending screen 900.

[0072] In step S711, when the seller user opens, for example, an email 1100 as shown in FIG. 11 and selects link information 1101, the information processing system 1 executes the processes in and after step S712.

[0073] In steps S712 to S714, the display unit 422 of the terminal device 102 obtains, for example, an order form receipt screen 1110 as shown in Fig. 11 from the acquisition destination indicated by the link information 1101, and displays it on the display 306 etc. In the example of Fig. 11, the order form receipt screen 1110 displays an order form image 1111, a display all button, a download button, and a receive button 1112.

[0074] In step S715, when the seller user performs an operation to receive the order on the order receipt screen 1110, the information processing system 1 executes the processes of steps S716 and S717. The seller user can confirm the order details on the order image 1111 and select the receive button 1112 to receive the order.

[0075] In step S716, the operation acceptance unit 423 of the terminal device 102 transmits to the transaction management system 100 a receipt notification indicating that the seller user's operation to receive the purchase order has been accepted.

[0076] In step S717, the second registration unit 405 of the transaction management system 100 obtains information on an order form with order number "190188", for example, from the issued order form DB 501 as shown in FIG. 10, and registers it in the received order form DB 502b of the seller 20.

[0077] Fig. 12 is a diagram showing an example of a received order DB according to an embodiment. In Fig. 12, among the items included in the received order DB 502, information such as "order number", "total amount", "consumption tax", "issue date", "form image path", "details", and "remarks" is copied by the second registration unit 405 from the issued order DB 501. The second registration unit 405 adds information on "order source" by acquiring, for example, a tenant name from the source issued order DB 501. The second registration unit 405 sets information on "status" to a status of "invoice not issued".

[0078] By the above process, the information of the purchase order created by the buyer user can be registered in the seller 20's received purchase order DB 502b.

[0079] (Billing Processing) Fig. 13 is a sequence diagram showing an example of order processing according to one embodiment. This processing shows an example of billing processing executed by the information processing system 1 when a seller user (second user) registers an invoice in the transaction management system 100 using the terminal device 102. It is assumed that the order processing described in Fig. 7 has already been executed at the start of the processing shown in Fig. 13.

[0080] In step S1301, the seller user starts creating an invoice. For example, the seller user can start creating an invoice by displaying a list screen 1400 of receipt orders as shown in FIG. 14 and selecting the "Create invoice" button 1401.

[0081] In step S1302, when the operation acceptance unit 423 of the terminal device 102 accepts an operation to start invoice creation, it transmits a request to start invoice creation to the transaction management system 100.

[0082] In steps S1303 and S1304, when the display control unit 403 of the transaction management system 100 accepts a request to start creating an invoice, it creates an invoice creation screen 1500, for example, as shown in Fig. 15, and sends it to the requesting terminal device 102. The display control unit 403 uses the order number of the receipt order form selected by the seller user on the receipt order form list screen 1400 to obtain information to be displayed on the invoice creation screen 1500 from the receipt order form DB 502b.

[0083] In step S1305, the display unit 422 of the terminal device 102 displays an invoice creation screen 1500 on the display 306 or the like.

[0084] It should be noted that the seller user can change the product quantity and unit price information 1601 on the invoice creation screen 1500, for example, as shown in Fig. 16. In this case, when the seller user changes the product quantity and unit price information 1601, the display control unit 403 of the transaction management system 100 automatically recalculates and updates the amount information 1602 and the total amount 1603.

[0085] Furthermore, when a seller user changes the product quantity and unit price information 1601, for example, the display control unit 403 automatically inputs a message such as "Your order has been changed. Please check the notification information" into the remarks field 1604. As another example, the message in the remarks field 1604 may be input by the seller user.

[0086] As an example, the seller user inputs the account information of the seller 20 in the input field 1605 for the transfer destination. As another example, the display control unit 403 may obtain the account information of the seller 20 from the tenant management information 600 and set it in the input field 1605 for the transfer destination.

[0087] As a modified example, the subtotal or total amount of the amount information 1602 may be changeable on the invoice creation screen 1500. For example, assume that a seller user changes the total amount of the amount information 1602 from "1,980,000" to "1,900,000" on the invoice creation screen 1500. In this case, the display control unit 403 may display the difference of "80,000" as a discount amount or the like, for example, between the total amount and the consumption tax.

[0088] In step S1306, the information processing system 1 executes an invoice editing process as shown in FIG. 17, as an example.

[0089] FIG. 17 is a flowchart showing an example of an invoice editing process according to an embodiment.

[0090] In step S1701, the display control unit 403 of the transaction management system 100 accepts input of an item value (second input information). For example, the display control unit 403 accepts an input operation by a seller user on the invoice creation screen 1500 described in FIG.

[0091] In step S1702, when the create button 1606 is selected, the display control unit 403 executes the processes in and after step S1703.

[0092] In step S1703, the display control unit 403 executes the processes of steps S1705 to S1707 for each of the input items for which input was accepted in step S1701.

[0093] In steps S1704 and S1705, the display control unit 403 compares the pre-change value of the input item with the post-change value to determine whether they match. If the pre-change value and the post-change value do not match, the display control unit 403 shifts the process to step S1706. On the other hand, if the pre-change value and the post-change value match, the display control unit 403 stops executing the process of step S1706.

[0094] In step S1706, the display control unit 403 judges whether the item value whose pre-change value and post-change value do not match is an item value changed by the user. If the item value is changed by the user, the display control unit 403 shifts the process to step S1707. On the other hand, if the item value is not changed by the user, the display control unit 403 stops executing the process of step S1711.

[0095] In step S1708, the display control unit 403 determines whether or not there is an item to be input, which was identified in step S1707. If there is an item to be input, the display control unit 403 moves the process to step S1709. On the other hand, if there is no item to be input, the display control unit 403 ends the process of FIG.

[0096] In step S1709, the display control unit 403 causes the terminal device 102 to display, for example, a notification information registration screen 1800 as shown in FIG.

[0097] Fig. 18 shows an example of a notification information registration screen according to an embodiment. In the example of Fig. 18, by selecting a tab 1801 corresponding to a change item on a notification information registration screen 1800, a change reason, attachment processing, comment, and the like corresponding to the change item can be input. For example, when a seller user selects "out of stock" as the change reason from a plurality of candidates displayed in a column 1802 of change reason selection candidates, the selected change reason "out of stock" is displayed in a column 1803 of selected items. This allows the seller user to set the change reason to "out of stock".

[0098] Furthermore, the seller user can attach an attachment to the notification information by selecting a file selection button 1804 and selecting a file. Furthermore, the seller user can input a comment in a comment field 1805. The seller user can complete input of the notification information by selecting an OK button 1705. The comment field 1805 may be provided for each item to be changed, or one common comment field 1805 may be provided on the registration screen 1800.

[0099] When input of the notification information is completed in step S1710, the display control section 403 moves the process to step S1711.

[0100] In step S1711, the second registration unit 405 of the transaction management system 100 associates the notification information entered on the notification information registration screen 1800 with the invoice information created on the invoice creation screen 1500 and registers it in the issued invoice DB 503b on the seller 20 side.

[0101] (Modification) As a modified example, in step S1306 in FIG. 13, the information processing system 1 may execute an invoice editing process as shown in FIG.

[0102] 19 is a flowchart showing another example of an invoice editing process according to an embodiment of the present invention, in which detailed description of the same process as that described in FIG.

[0103] In step S1901, the display control unit 403 of the transaction management system 100 accepts input of item values.

[0104] In step S1902, the display control unit 403 determines whether the input item value has been confirmed. For example, the display control unit 403 may determine that the item value has been confirmed when the Enter key is pressed, or when a location other than the input field or the selection button is clicked, etc. If the item value has been confirmed, the display control unit 403 shifts the process to step S1903.

[0105] In steps S1903 and S1904, the display control unit 403 compares the pre-change value of the input item with the post-change value to determine whether they match. If the pre-change value and the post-change value do not match, the display control unit 403 shifts the process to step S1905. On the other hand, if the pre-change value and the post-change value match, the display control unit 403 ends the process of FIG. 19.

[0106] In step S1905, for example, a notification information registration screen 2000 as shown in FIG.

[0107] Fig. 20 shows another example of a notification information registration screen according to an embodiment. In the process of Fig. 19, each time a seller user changes an item value that can be changed, a notification information registration screen 2000 as shown in Fig. 20 is displayed. Therefore, the notification information registration screen 2000 does not require tabs like the notification screen registration screen 1800 shown in Fig. 18. In addition, the notification information registration screen 2000 allows the user to select the reason for change with a check box 2001 as a variation of the method for selecting the reason for change. In addition, the seller user can complete the input of the notification information by selecting an OK button 2002.

[0108] When the input of the notification information is completed in step S1906, the display control unit 403 ends the processing in FIG.

[0109] The display control unit 403 executes the process of Fig. 19 when, for example, an item value that can be changed by a seller user is changed on an invoice creation screen 1500 as shown in Fig. 16. Furthermore, when a Create button 1606 is selected on the invoice creation screen 1500, the second registration unit 405 registers the notification information entered on the notification information registration screen 2000 in the issued invoice DB 503 in association with the information of the invoice created on the invoice creation screen 1500.

[0110] Returning now to FIG. 13, the description of the sequence diagram of the billing process will be continued.

[0111] In step S1307, the display control unit 403 of the transaction management system 100 generates an invoice and an invoice sending screen based on the information registered by the second registration unit 405 in the issuance invoice DB 503, and sends the generated invoice sending screen to the terminal device 102.

[0112] For example, the display control unit 403 creates an invoice 2100 as shown in Fig. 21 using information entered on an invoice creation screen 1500 as shown in Fig. 16. In this case, since the quantity and unit price have been changed on the invoice creation screen 1500, a message prompting confirmation of the notification information is included in the remarks field.

[0113] In step S1309, the display unit 422 of the terminal device 102 displays, for example, an invoice sending screen 2200 as shown in FIG.

[0114] In step S1310, the seller user selects the destination email address from the delivery information input field 2201 on the invoice delivery screen 2200, and edits the contents of the email information input field 2202 as necessary. The seller user also checks the invoice image 2203, and if there are no problems, selects the send button 2204 to instruct the delivery of the invoice.

[0115] In step S1311, when the operation acceptance unit 423 of the terminal device 102 accepts the selection of the send button 2204, it sends a send request to the transaction management system 100 to request the sending of the invoice.

[0116] In step S1312, when the second registration unit 405 of the transaction management system 100 receives a request to send an invoice from the terminal device 102, it changes the status of the invoice information registered in the issued invoice DB 503b to "invoice issued."

[0117] In step S1313, the information sending unit 406 of the transaction management system 100 sends an e-mail to the destination e-mail address accepted on the invoice sending screen 2200.

[0118] In step S1314, the buyer user opens the e-mail and selects the link information, whereby, for example, a receipt process similar to steps S712 to S716 in FIG.

[0119] In step S1316, the first registration unit 404 of the transaction management system 100 obtains information about the invoice created in the above process, for example, from the issued invoice DB 503b on the seller 20 side, and registers it in the received invoice DB 504a on the buyer 10 side.

[0120] Fig. 23 is a diagram showing an example of an issued invoice DB according to one embodiment. This diagram shows an image of an example of an issued invoice DB 503b on the seller 20 side. In the example of Fig. 23, the issued invoice DB 503b includes information such as items such as "billing destination", "invoice number", "order number", "status", "total amount", "consumption tax", "issue date", "payment due date", "transfer destination", "form image path", "detailed information", and "remarks".

[0121] For items such as "billing destination," "total amount," "consumption tax," "payment due date," "transfer destination," and "remarks," the second registration unit 405 registers information set by the seller user on the invoice creation screen 1500 as shown in FIG. 16 in the issued invoice DB 503b. The second registration unit 405 also sets the "invoice number" item, for example, when registering invoice information in the issued invoice DB 503. For the "form image path" item, the second registration unit 405 sets information indicating the storage location and file name of the image of invoice 2100 as shown in FIG. 21, for example.

[0122] Also, for example, when notification information is input on the notification information registration screens 1800 and 2000 as shown in Figs. 18 and 20, the second registration unit 405 registers the issuance notification information 2401 as shown in Fig. 24(A) in the issuance invoice DB 503b. This issuance notification information 2401 contains notification information corresponding to the invoice information registered in the issuance invoice DB 503b shown in Fig. 23. Note that the invoice information and the notification information are associated with each other by the invoice number. In the example of Fig. 24(A), the issuance notification information 2401 stores information such as the notification target, the reason for change, the attached materials, and the comments input on the notification information registration screens 1800 and 2000. Note that the issuance notification information 2401 may be included in the issuance invoice DB 503b as shown in Fig. 23, for example.

[0123] Fig. 25 is a diagram showing an example of an invoice receipt DB according to one embodiment. This diagram shows an image of an example of an invoice receipt DB 504a on the buyer 10 side. In the example of Fig. 25, the invoice receipt DB 504a includes information such as items such as "biller", "invoice number", "purchase order number", "status", "verification result", "receipt date", "total amount", "consumption tax", "issue date", "payment due date", "transfer destination", "document image path", "detailed information", and "remarks".

[0124] The first registration unit 404 copies information from the issued invoice DB 503b as shown in FIG. 23 to the received invoice DB 504a for items such as "invoice number", "order number", "total amount", "consumption tax", "issue date", "payment due date", "transfer destination", "detailed information", and "remarks". The first registration unit 404 sets the "biller" item by acquiring it from, for example, the tenant name in the issued invoice DB 503b as shown in FIG. 23. The first registration unit 404 sets the "status" item to "unconfirmed". The matching unit 407 registers the matching result determined by the matching process described later in the "matching result" item. The "receipt date" item sets the date on which the first registration unit 404 registered the invoice information in the received invoice DB 504a.

[0125] Furthermore, when notification information is associated with invoice information registered in the received invoice DB 504a, the first registration unit 404 registers the notification information in the received invoice DB 504a in association with the invoice information. For example, the first registration unit 404 adds "biller" information to the issue notification information 2401 as shown in FIG. 24(A) to create receipt notification information 2402 as shown in FIG. 24(B), and registers the created receipt notification information 2402 in the received invoice DB 504a. Note that the invoice information and notification information are associated with each other by the invoice number.

[0126] Returning now to FIG. 13, the description of the sequence diagram of the billing process will be continued.

[0127] In step S1317, the collation unit 407 of the transaction management system 100 executes a collation process such as that shown in FIG.

[0128] 26 is a flowchart showing an example of a matching process according to an embodiment. This diagram shows an example of the process executed by the matching unit 407 of the transaction management system 100 in step S1317 of FIG.

[0129] In step S2601, the collation unit 407 acquires invoice information from the received invoice DB 504, and acquires the purchase order number included in the acquired invoice information. For example, the collation unit 407 acquires invoice information with invoice number "30126" that the first registration unit 404 registered in the received invoice DB 504a in step S1316 in Fig. 13, and acquires the purchase order number "190188" included in the acquired invoice information.

[0130] In step S2602, the collation unit 407 acquires information on the purchase order corresponding to the acquired order number from the issued purchase order DB 501. For example, the collation unit 407 acquires information on the purchase order with the purchase order number "190188" from the issued purchase order DB 501 as shown in FIG.

[0131] In steps S2603 and S2604, the collation unit 407 determines whether the total amount included in the invoice information acquired from the received invoice DB 504 matches the total amount included in the purchase order information acquired from the issued purchase order DB 501. If the total amount included in the invoice information acquired from the received invoice DB 504 matches the total amount included in the purchase order information acquired from the issued purchase order DB 501, the collation unit 407 shifts the process to step S2605. On the other hand, if the total amount included in the invoice information acquired from the received invoice DB 504 does not match the total amount included in the purchase order information acquired from the issued purchase order DB 501, the collation unit 407 shifts the process to step S2608.

[0132] In steps S2605 and S2606, the collation unit 407 compares the detailed information included in the purchase order information acquired from the issued purchase order DB 501 with the detailed information included in the invoice information acquired from the received invoice DB 504. If all of the detailed information included in the purchase order information acquired from the issued purchase order DB 501 matches the detailed information included in the invoice information acquired from the received invoice DB 504, the collation unit 407 shifts the process to step S2607. On the other hand, if there is any item that does not match the detailed information included in the purchase order information acquired from the issued purchase order DB 501 and the detailed information included in the invoice information acquired from the received invoice DB 504, the collation unit 407 shifts the process to step S2608.

[0133] In step S2607, collation section 407 determines that the collation result is "match," and moves the process to step S2612.

[0134] On the other hand, when the process proceeds to step S1608, the collation unit 407 acquires the notification information corresponding to the purchase order number acquired in step S2601 from the received invoice DB 504. For example, the collation unit 407 acquires the notification information registered in the receipt notification information 2402 shown in FIG. 24(B) by the first registration unit 404 in step S1316 in FIG. 13.

[0135] In step S2609, collating unit 407 determines whether or not notification information has been acquired (whether or not notification information corresponding to invoice information has been registered), and if notification information has not been acquired, transitions the process to step S2610. On the other hand, if notification information has been acquired, collating unit 407 transitions the process to step S2611.

[0136] In step S2610, matching unit 407 determines that the matching result is "mismatch" and moves the process to step S2612. On the other hand, in step S1611, matching unit 407 determines that the matching result is "mismatch (notification information present)" and moves the process to step S2612.

[0137] In step S2612, the collation unit 407 registers the collation result in the “collation status” item of the received invoice DB 504, for example.

[0138] Returning now to FIG. 13, the sequence diagram of the billing process will be further described.

[0139] In step S1318, the first registration unit 404 of the transaction management system 100 changes the status of the invoice information registered in the received invoice DB 504a as shown in FIG. 25, for example, to "unconfirmed."

[0140] (Confirmation process) Fig. 27 is a sequence diagram showing an example of confirmation processing according to one embodiment. This processing shows an example of confirmation processing in which a buyer user (first user) confirms the information of an "unconfirmed" invoice registered in the received invoice DB 504a using the terminal device 101. It is assumed that the invoicing processing described in Fig. 13 has already been executed at the start of the processing shown in Fig. 27.

[0141] In step S2701, the buyer user performs an operation to display the invoice list. In response, in step S2702, the operation reception section 413 of the terminal device 101 requests the transaction management system 100 to obtain the invoice list.

[0142] In step S2703, the display control unit 403 of the transaction management system 100 generates, for example, an invoice list screen 2800 as shown in Fig. 28 and transmits it to the requesting terminal device 101a. Note that the display control unit 403 generates the invoice list screen 2800 by extracting predetermined information from, for example, the received invoice DB 504a as shown in Fig. 25.

[0143] In step S2704, the terminal device 101a displays the invoice list screen 2800 received from the transaction management system 100.

[0144] In step S2705, when the operation reception unit 413 of the terminal device 101a receives an operation to display a confirmation screen, the information processing system 1 executes the processes in and after step S2706. In response to this, in step S2706, the operation reception unit 413 of the terminal device 101 requests the transaction management system 100 to acquire a confirmation screen. Note that the buyer user can perform a display operation of the confirmation screen by, for example, selecting the Confirm button 2801 on the invoice list screen 2800 as shown in FIG.

[0145] In step S2707, the display control unit 403 of the transaction management system 100 generates, for example, a confirmation screen 2900 as shown in FIG. 29, and transmits it to the requesting terminal device 101a.

[0146] 29 is a diagram showing an example of a confirmation screen according to an embodiment. The confirmation screen 2900 includes information such as purchase order information 2910, invoice information 2920, journal entry voucher 2930, and payment information 2940. For example, the display control unit 403 displays the purchase order information 2910 on the confirmation screen 2900 using purchase order information acquired from the issued purchase order DB 501a based on the purchase order number on the invoice list screen 2800.

[0147] Furthermore, the display control unit 403 displays invoice information 2902 using invoice information acquired from the received invoice DB 504a based on the invoice number on the invoice list screen 2800. Preferably, the display control unit 403 highlights information 2921, 2922 in the invoice information 2902 that differs from the order form information 2910. Furthermore, the display control unit 403 displays a "Check notification information" button 2923 on the confirmation screen 2900 when notification information is associated with the acquired invoice information.

[0148] Furthermore, the display control unit 403 uses, for example, a preset template or the like to display the journal voucher 2930 and the payment information 2904 on the confirmation screen 2900. Note that some of the information among the setting items of the journal voucher 2930 and the payment information 2904 may be automatically set by the display control unit 403. Information that is not automatically set is input by the buyer user.

[0149] Returning now to FIG. 27, the explanation of the sequence diagram of the confirmation process will be continued.

[0150] When the buyer user performs an operation to display the notification information in step S2709, the operation acceptance section 413 of the terminal device 101a requests the transaction management system 100 to display the notification information in step S2710.

[0151] In step S2710, the display control unit 403 of the transaction management system 100 generates, for example, notification information 3000 as shown in Fig. 30 and transmits it to the requesting terminal device 101a. As a result, the display unit 412 of the terminal device 101a displays the notification information 3000 on the display 306 or the like. This notification information 3000 makes it easy for the buyer user to determine the validity of information 2921, 2922 in the invoice information 2902 that differs from the order form information 2910.

[0152] The confirmation screen 2900 shown in FIG. 29 is an example. For example, the display control unit 403 may generate a confirmation screen 3100 as shown in FIG. 31 in step S2707 and display it on the terminal device 101a. In the example of FIG. 31, display elements 3101 and 3102 for displaying notification information corresponding to the difference between the purchase order information and the invoice information are displayed on the confirmation screen 3100. For example, the buyer user can display notification information 3103 by selecting the display element 3101 on the confirmation screen 3100. In this way, the display control unit 403 can display invoice information (information of the second type of form) 3104 and notification information 3103 corresponding to the invoice information 3104 on the confirmation screen 3100.

[0153] Here, if the buyer user checks the notification information and determines that the invoice information 2902 is valid, the information processing system 1 executes the processes in and after step S2713.

[0154] In step S2713, the buyer user inputs accounting information, payment information, etc., on the confirmation screen 2900, and selects the approval request button 2901. In response, in step S2714, the operation reception unit 413 of the terminal device 101a requests the transaction management system 100 to update the received information.

[0155] In step S2715, the first registration unit 404 of the transaction management system 100 changes the "status" of the information of the invoice to be processed to "waiting for approval" in, for example, the received invoice DB 504a as shown in Fig. 25. In addition, in step S2716, the first registration unit 404 registers the accounting information and payment information obtained from the terminal device 101a in, for example, output information 3200 as shown in Fig. 32. This output information 3200 is used when transmitting information to a core system 3 such as an accounting system, a settlement system, or an order receiving and placing system.

[0156] From this state, for example, in step S2721, the approver uses the terminal device 101b to perform an approval operation on the invoice information registered in the received invoice DB 504a in the "waiting for approval" state. As a result, the terminal device 101b transmits a confirmation request to the transaction management system 100.

[0157] The approval screen on which the approver gives approval may be any screen, for example, a screen in which the "Request Approval" button 2901 on the confirmation screen 2900 as shown in Fig. 29 is changed to an "Approve" button can be used as the approval screen. Also, the timing at which the approver gives approval may be any timing.

[0158] In step S2723, the first registration unit 404 of the transaction management system 100 changes the "status" of the information of the invoice approved by the approver to "confirmed" in, for example, the received invoice DB 504a as shown in FIG.

[0159] Note that the information on the invoice that has been "confirmed" here may be sent by, for example, the information sending unit 406 of the transaction management system 100 to the core system 3 together with the output information 3200 as shown in Fig. 32. As a result, the accounting system or settlement system etc. included in the core system 3 executes the payment process based on the information on the invoice that has been "confirmed."

[0160] By performing the above processes, when the seller changes the amount of the invoice, the buyer can easily confirm the reason for the change in the amount of the invoice by displaying the notification information.

[0161] Therefore, according to this embodiment, in a system that manages transactions in which payment is confirmed by comparing documents issued by the buyer with documents issued by the seller, the workload on the buyer's side can be reduced when the invoice amount is changed.

[0162] In the above embodiment, the order form is an example of a first type of form, and the invoice is an example of a second type of form. For example, the transaction management system 100 may utilize or use in combination various forms used in transactions (e.g., estimates, delivery notes, receipts, etc.).

[0163] <Supplementary Information> Each function of each embodiment described above can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), or a conventional circuit module designed to execute each function described above.

[0164] The devices described in the example are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the trading management system 100 includes a plurality of computing devices, such as a server cluster, configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein.

[0165] Furthermore, each functional component of the transaction management system 100 may be integrated into one server device, or may be distributed across multiple devices. [Explanation of symbols]

[0166] 1. Information Processing Systems 100 Transaction management system (information processing device) 101 Terminal Equipment 102 Terminal Equipment 403 Display control unit 404 First Registration Section 405 Second Registry 501, 501a, 501b Issued Purchase Order DB 502, 502a, 502b Receipt order DB 503, 503a, 503b Invoice DB 504, 504a, 504b Received invoice DB 1500 Invoice creation screen (input screen) 1800, 2000 Notification information registration screen 2900, 3100 Confirmation screen 3104 Invoice Information 3000, 3103 Notification information [Prior art documents] [Patent documents]

[0167] [Patent Document 1] JP 2005-122426 A

Claims

1. a first registration unit that registers information of a first type of form based on first input information from a terminal device used by a first user; a display control unit that displays, on a terminal device used by a second user, an input screen that accepts input of information on a second type of form corresponding to the first type of form based on the information on the first type of form; a second registration unit that registers information of the second type of form based on second input information inputted to the input screen; having When the second input information includes information that does not match information of the first type of form corresponding to the second type of form, the display control unit causes a registration screen for registering notification information related to the mismatched information to be displayed on a terminal device used by the second user. Information processing device.

2. The information processing apparatus according to claim 1 , wherein the second registration unit registers the notification information registered on the registration screen in association with the second type of form.

3. The information processing device according to claim 1 , wherein the display control unit causes the information of the second type of form and the notification information corresponding to the second type of form to be displayed on a terminal device used by the first user.

4. The display control unit is displaying a confirmation screen displaying information on the first type of form and information on the second type of form on a terminal device used by the first user; The information processing apparatus according to claim 3 , wherein, when the notification information corresponding to the second type of form is present, a display element for displaying the notification information is displayed on the confirmation screen.

5. The information processing apparatus according to claim 1 , wherein the notification information includes information indicating a reason why the information on the first type of form and the second input information do not match.

6. The first type of document is a purchase order or a purchase order, The information processing apparatus according to claim 1 , wherein the second type of document is an invoice.

7. 7. The information processing device according to claim 6, wherein the display control unit, when the detailed information of the invoice entered on the input screen does not match the detailed information of the order form or purchase order corresponding to the invoice, causes the registration screen for inputting the notification information indicating the reason for the mismatch to be displayed on a terminal device used by the second user.

8. An information processing device as described in claim 1, which accepts input of the notification information on the registration screen.

9. An information processing system including a terminal device used by a first user and an information processing device capable of communicating with a terminal device used by a second user, and the terminal device used by the second user, The information processing device includes: a first registration unit that registers information of a first type of form based on first input information from a terminal device used by a first user; a display control unit that displays, on a terminal device used by a second user, an input screen that accepts input of information on a second type of form corresponding to the first type of form based on the information on the first type of form; a second registration unit that registers information of the second type of form based on second input information inputted to the input screen; having The terminal device used by the second user is A display unit that displays the input screen, the display control unit, when the second input information includes information that does not match information of the first type of form corresponding to the second type of form, displays a registration screen for registering notification information related to the mismatched information on a terminal device used by the second user; The display unit displays the registration screen. Information processing system.

10. An information processing device capable of communicating with a terminal device used by a first user and a terminal device used by a second user, a first registration process for registering information of a first type of form based on first input information from a terminal device used by a first user; a display control process for displaying, on a terminal device used by a second user, an input screen for accepting input of information of a second type of form corresponding to the first type of form based on information of the first type of form; a second registration process for registering information of the second type of form based on second input information inputted on the input screen; Run When the second input information includes information that does not match information on the first type of form corresponding to the second type of form, the display control process displays a registration screen for registering notification information related to the information that does not match on a terminal device used by the second user. How transactions are managed.

11. An information processing device capable of communicating with a terminal device used by a first user and a terminal device used by a second user, a first registration process for registering information of a first type of form based on first input information from a terminal device used by a first user; a display control process for displaying, on a terminal device used by a second user, an input screen for accepting input of information of a second type of form corresponding to the first type of form based on information of the first type of form; a second registration process for registering information of the second type of form based on second input information inputted on the input screen; Run the command, When the second input information includes information that does not match information on the first type of form corresponding to the second type of form, the display control process displays a registration screen for registering notification information related to the information that does not match on a terminal device used by the second user. program.

Images