Transaction management server, communication system, transaction management method, and program

Abstract

To provide a transaction managing server, a communication system, a transaction managing method, and a program, capable of solving the problem that it requires much time and labor for a purchaser side to add bill-identifying information to remittance data, to a possible extent.SOLUTION: In a communication system in which a seller terminal, a purchaser terminal, a transaction managing server, an account managing server on a purchaser side and an account managing server on a seller side communicate with each other through a communication network such as the Internet, a transaction managing server 3 generates remittance data including bill-identifying information for identifying a bill related to business transaction issued to a purchaser and used in a bill-based remittance from an account of the purchaser to an account of the seller and sends the generated remittance data to the purchaser terminal of the purchaser.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to a transaction management server, a communication system, a transaction management method, and a program. Background Art

[0002] Conventionally, in reconciliation processing, a seller reconciles accounts receivable related to an invoice while collating information such as the remittance amount and remittance date included in remittance information from a purchaser with information such as the billed amount and payment due date described in the invoice. In this case, techniques are used by the seller to check whether the accounts receivable have been collected as billed, whether there is a delay in collection, or the like (see Patent Document 1). Prior Art Documents Patent Documents

[0003] Patent Document 1 Japanese Unexamined Patent Application Publication No. 2008-009873 Summary of the Invention Problems to be Solved by the Invention

[0004] However, on the seller side, in order to facilitate processing such as reconciliation of accounts receivable related to an invoice, the purchaser must perform the work of adding invoice identification information for identifying the invoice to remittance data indicating the remittance amount, remittance date, and the like. Therefore, there arises a problem that it takes time and effort for the purchaser to add the invoice identification information to the remittance data. Means for Solving the Problems

[0005] The invention according to claim 1 is a transaction management server that manages a plurality of invoices relating to commercial transactions between a seller and a buyer, and is characterized by comprising: generation means for generating remittance data which includes invoice identification information that identifies the invoice relating to the commercial transaction issued to the buyer, and which is used for remittance from the buyer's account to the seller's account based on the invoice; and transmission means for transmitting the generated remittance data to the buyer's terminal. [Effects of the Invention]

[0006] As explained above, the present invention has the effect of minimizing the problem of the time and effort required for the purchaser to add invoice identification information to the remittance data. [Brief explanation of the drawing]

[0007] [Figure 1] This diagram shows the relationships between the companies according to this embodiment. [Figure 2] This is a schematic diagram of the communication system of this embodiment. [Figure 3] This is a hardware configuration diagram of the seller terminal, buyer terminal, transaction management server, and account management server in this embodiment. [Figure 4] This is a functional block diagram of the communication system according to this embodiment. [Figure 5] This is a conceptual diagram of the tenant information management table. [Figure 6] This is a conceptual diagram of the transfer source account information management table. [Figure 7] This is a conceptual diagram of the invoice information table. [Figure 8] This is a conceptual diagram of the deposit and withdrawal information management table. [Figure 9] This is a sequence diagram showing the process of sending invoices. [Figure 10] This is a sequence diagram showing the display process for the receipt screen. [Figure 11] This is a flowchart illustrating the process for creating the receipt screen. [Figure 12]FIG. 11 is a diagram showing a reception screen displayed on a purchaser terminal when transfer source account information is not registered. [Figure 13] FIG. 12 is a diagram showing a reception screen displayed on a purchaser terminal when transfer source account information has already been registered. [Figure 14] FIG. 13 is a sequence diagram showing processing for acquiring an invoice image. [Figure 15] FIG. 14 is a sequence diagram showing download request processing for remittance data when a download type ID is T1. [Figure 16] FIG. 15 is a sequence diagram showing download request processing for remittance data when a download type ID is T3. [Figure 17] FIG. 16 is a sequence diagram showing download request processing for remittance data when a download type ID is T2. [Figure 18] FIG. 17 is a diagram showing a new account information registration screen displayed on a purchaser terminal. [Figure 19] FIG. 18 is a diagram showing an account information change screen displayed on a purchaser terminal. [Figure 20] FIG. 19 is a sequence diagram showing download processing for remittance data. [Figure 21] FIG. 20 is a diagram showing an example of remittance data. [Figure 22] FIG. 21 is a sequence diagram showing reconciliation processing. [Figure 23] FIG. 22 is a transition diagram of a deposit / withdrawal information management table. [Figure 24] FIG. 23 is a flowchart showing automatic reconciliation processing. [Figure 25] FIG. 24 is a diagram showing an automatic reconciliation result screen displayed on a seller terminal. [Figure 26] FIG. 25 is a flowchart showing reception screen creation processing in a first modification. [Figure 27] FIG. 26 is a diagram showing a reception screen in a first modification. [Figure 28] FIG. 27 is a diagram showing a new account information registration screen in a first modification. [Figure 29] FIG. 28 is a diagram showing an account information change screen in a first modification. [Figure 30]This diagram shows the offsetting information input screen displayed on the purchaser's terminal. [Figure 31] This is a conceptual diagram of the invoice details information management table. [Figure 32] This is a conceptual diagram of the deposit and withdrawal information management table in Example 1. [Figure 33] This figure shows an example of remittance data in the first modified example. [Figure 34] This flowchart shows the automatic reconciliation process in Example 1. [Figure 35] This figure shows the automatic reconciliation results screen in Modification Example 1. [Figure 36] This diagram shows the invoice information confirmation screen displayed on the seller's terminal. [Figure 37] This figure shows the receipt screen for each trading partner in the modified example 2. [Figure 38] This figure shows an example of remittance data in the second variation. [Figure 39] This flowchart shows the automatic reconciliation process in modified example 2. [Figure 40] This figure shows the offset information input screen in modified example 3. [Figure 41] This figure shows an example of remittance data in the third modified example. [Modes for carrying out the invention]

[0008] [Relationships between companies] Figure 1 will be used to explain the relationships between the companies. Figure 1 is a diagram illustrating the relationships between the companies according to this embodiment.

[0009] As shown in Figure 1, service-using company A is a company that provides goods or services to trading partner company B and receives consideration from trading partner company B. In this case, service-using company A is the creditor and trading partner company B is the debtor.

[0010] Service provider C is a company that, at the request of service user A, provides a service of creating invoices that service user A sends to its business partner B.

[0011] Financial institution D1 is the financial institution that manages the bank account of client company B. Financial institution D2 is the financial institution that manages the bank account of service user company A.

[0012] Here, we will briefly describe the processing in this embodiment. Note that the IDs described later are examples of identification information.

[0013] First, service user company A requests service provider company C to create an invoice and send it to its trading partner (S1). Service provider company C then creates remittance data, including the invoice and invoice ID, and sends it to trading partner company B (S2). This remittance data is used for the invoice-based remittance from trading partner company B's (buyer's) bank account to service user company A's (seller's) bank account. The data contents are shown in Figure 21. In other words, service provider company C creates the remittance data that trading partner company B will use when making the remittance, and furthermore, it includes the invoice ID in the remittance data during its creation.

[0014] Next, client company B sends remittance data, which includes the invoice ID, to financial institution D1 (S3). As a result, financial institution D1 remits the invoiced amount according to the remittance data to financial institution D2, which manages the bank account of service user company A (S4). The invoice ID is also sent at this time.

[0015] Next, after confirming the remittance, financial institution D2 sends remittance information (information such as the remitter, recipient, amount, and date of remittance) including the remittance details and invoice ID to service provider C, and service provider C obtains the remittance information (S5).

[0016] Next, service provider C performs reconciliation processing for the invoice identified by the invoice ID, based on the invoice ID and remittance information included in the remittance information (S6). In this case, even if there are multiple invoices, service provider C can identify the invoice to be reconciled by the invoice ID and confirm whether the billed amount and the remitted amount match using the remittance information. If the invoice IDs match but the billed amount and the remitted amount do not match, service provider C will not perform reconciliation processing for the invoice and will take appropriate action, such as informing trading partner C of the situation.

[0017] [Outline of the communication system] Figure 2 is a schematic diagram of the communication system of this embodiment. Figure 2 shows the terminals or servers of each company in Figure 1.

[0018] Service user company A has a seller terminal 1, such as a PC (personal computer), which is operated by seller A1. Trading partner company B has a buyer terminal 2, such as a PC, which is operated by buyer B1. Service provider company C has a transaction management server 3. Financial institution D1 has an account management server 4a for buyer B1. Financial institution D2 also has an account management server 4b for seller A1. Each server is composed of a computer. Seller terminal 1, buyer terminal 2, transaction management server 3, account management server 4a, and account management server 4b can communicate with each other via a communication network 100 such as the Internet.

[0019] [Hardware configuration of the communication system] Next, using Figure 3, we will explain the hardware configuration of each terminal and server that make up the communication system shown in Figure 1. Since all of them have the same configuration, we will explain the hardware configuration of vendor terminal 1 and omit the explanation of the hardware configuration of each server.

[0020] As shown in Figure 3, the seller terminal 1 is a computer and includes a CPU 101, ROM 102, RAM 103, HD 104, HDD (Hard Disk Drive) controller 105, display 106, external device connection I / F (Interface) 108, network I / F 109, bus line 110, keyboard 111, pointing device 112, DVD-RW (Digital Versatile Disk Rewritable) drive 114, and media I / F 116.

[0021] Of these components, the CPU 101 controls the operation of the entire computer. The ROM 102 stores programs used to drive the CPU 101, such as the IPL. The RAM 103 is used as the work area for the CPU 101. The HD 104 stores various data, such as programs. The HDD controller 105 controls the reading or writing of various data to the HD 104 according to the control of the CPU 101. The display 106 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 108 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I / F 109 is an interface for data communication using the communication network 100. The bus lines 110 are address buses, data buses, etc., for electrically connecting each component, such as the CPU 101 shown in Figure 3.

[0022] The keyboard 111 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 112 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The DVD-RW drive 114 controls the reading or writing of various data to the DVD-RW 113, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may also be DVD-R or Blu-ray Disc (registered trademark), etc. The media I / F 116 controls the reading or writing (storage) of data to the recording medium 115, such as flash memory.

[0023] Furthermore, external device connection interfaces can be used to connect devices such as a microphone (an example of a sound collection device), a speaker (an example of a sound output device), and a camera (an example of an imaging device).

[0024] [Functional Configuration of the Communication System] Next, the functional configurations of the communication system of this embodiment will be described using Figures 3 to 4. Figure 4 is a functional block diagram of the communication system according to this embodiment. Note that the purchaser-side account management server 4a shown in Figure 2 will not appear in the processing described later, so its explanation will be omitted here, but it has the same functions as the account management server 4b.

[0025] <Functional Configuration of the Seller's Terminal> First, the functional configuration of the seller terminal 1 will be explained using Figures 3 and 4. As shown in Figure 4, the seller terminal 1 has a transmitting / receiving unit 11, a receiving unit 12, a display control unit 14, a determination unit 15, and a storage / reading processing unit 19. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 3 operating according to instructions from the CPU 101 that follow a program deployed from the HD 104 onto the RAM 103. The seller terminal 1 also has a storage unit 1000 constructed from the RAM 103 and HD 104 shown in Figure 3.

[0026] (Functional configuration of the seller's terminal) Next, the components of the seller terminal 1 will be described. The transmitting / receiving unit 11 is implemented by commands from the CPU 101 shown in Figure 3, as well as the external device connection I / F 108 and the network I / F 109, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 100.

[0027] The reception unit 12 is mainly implemented by commands from the CPU 101 shown in Figure 3, as well as the keyboard 111 and pointing device 112, and accepts various inputs from the user.

[0028] The display control unit 14 is primarily implemented by instructions from the CPU 101 shown in Figure 3, and displays images by outputting image data to the display 106 or an external display connected to the external device connection I / F 108. The display control unit 14 also has a web browser function.

[0029] The decision unit 15 is mainly implemented by instructions from the CPU 101 shown in Figure 3, and performs various decisions.

[0030] The memory and read processing unit 19 is mainly implemented by instructions from the CPU 101 and the HDD controller 105 shown in Figure 3, and performs processing such as storing various data in the memory unit 1000 and reading various data stored in the memory unit 1000.

[0031] <Functional configuration of the purchaser's device> Next, the functional configuration of the buyer terminal 2 will be explained using Figures 3 and 4. As shown in Figure 4, the buyer terminal 2 has a transmitting / receiving unit 21, a receiving unit 22, a display control unit 24, a determination unit 25, and a storage / reading processing unit 29. The transmitting / receiving unit 21, the receiving unit 22, the display control unit 24, the determination unit 25, and the storage / reading processing unit 29 have the same functions as the transmitting / receiving unit 11, the receiving unit 12, the display control unit 14, the determination unit 15, and the storage / reading processing unit 19 of the seller terminal 1, so their explanation will be omitted. Also, the storage unit 2000 has the same configuration as the storage unit 1000, so its explanation will be omitted.

[0032] <Functional Configuration of the Transaction Management Server> Next, the functional configuration of the transaction management server 3 will be explained using Figures 3 and 4. As shown in Figure 4, the transaction management server 3 has a transmitting / receiving unit 31, a generation unit 34, a determination unit 35, a creation unit 36, and a storage / reading processing unit 39. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 3 operating according to instructions from the CPU 101 that follow a program deployed from the HD 104 onto the RAM 103. The transaction management server 3 also has a storage unit 3000 constructed from the RAM 103 and HD 104 shown in Figure 3.

[0033] (Tenant information management table) Figure 5 is a conceptual diagram showing the tenant information management table. The storage unit 3000 has a tenant information management DB 3001 constructed, which consists of the tenant information management table shown in Figure 5. This table contains information about the tenant's company. Therefore, this table manages the tenant ID, tenant name (company name, trade name, etc.), tenant address (location), and the tenant's bank account information, etc., in association with each other. The account information includes information such as the bank name, branch name, account type, account number, and account holder name.

[0034] (Transfer source account information management table) Figure 6 is a conceptual diagram showing the remittance source account information management table. The memory unit 3000 has a remittance source account information management DB 3002 constructed, which consists of the remittance source account information management table shown in Figure 6. This table contains information about the remittance source account that will transfer the billing amount to each tenant, representing a service-using company. In this table, the remittance source account information (remitter name, bank name, branch name, account type, account number, and information indicating the account holder) is associated and managed for each tenant ID that indicates the recipient of the transfer. Based on this table, future periodic payments are predicted.

[0035] (Invoice Information Management Table) Figure 7 is a conceptual diagram showing the invoice information management table. The memory unit 3000 has an invoice information management DB 3003 constructed, which consists of the invoice information management table shown in Figure 7. This table shows the contents of invoices created by service provider C on behalf of service user A. Therefore, in this table, for each tenant ID, information such as invoice ID, billing ID, billing name, invoice amount, payment due date, invoice image, sending date, receipt status, payment status, and payment date, as well as a URL as the save location for the receipt screen, are associated and managed. The receipt status indicates whether or not the invoice issued by seller A1 to buyer B1 has been received by buyer B1.

[0036] (Deposit and withdrawal information management table) Figure 8 is a conceptual diagram showing the deposit and withdrawal information management table. The memory unit 3000 has a deposit and withdrawal information management DB 3004 constructed, which consists of the deposit and withdrawal information management table shown in Figure 8. This table contains information about deposits and withdrawals to the bank accounts of each service user company at a financial institution. Service provider C can obtain deposit and withdrawal information for service user company A's bank account from financial institution D2, for example, based on information previously registered by service user company A, through a contract with service user company A. Therefore, in this table, for each tenant ID representing a service user company, the following information is associated and managed: transaction date and time, payment amount, payee, deposit amount, deposit source, balance, invoice ID, billing address, billing amount, and reconciliation status.

[0037] (Functional configuration of the transaction management server) Next, we will explain in detail the functional configurations of the transaction management server 3. In addition, when explaining the functional configurations of the transaction management server 3, we will also explain the relationship between each component shown in Figure 3 and the main components necessary to realize each functional configuration of the transaction management server 3.

[0038] The transceiver unit 31 of the transaction management server 3 shown in Figure 4 is implemented by commands from the CPU 101 shown in Figure 3 and the network interface 109, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 100.

[0039] The generation unit 34 is implemented by instructions from the CPU 101 shown in Figure 3, and generates predetermined data (information). The details of the generated data will be described later.

[0040] The decision unit 35 is implemented by instructions from the CPU 101 shown in Figure 3 and performs a predetermined decision. The details of the decision will be described later.

[0041] The creation unit 36 ​​is implemented by instructions from the CPU 101 shown in Figure 3, and performs tasks such as creating the receipt screen and the URL for the receipt screen, which will be described later.

[0042] The memory and read processing unit 39 is implemented by instructions from the CPU 101 and the HDD controller 105 shown in Figure 3, and performs processing such as storing various data in the memory unit 3000 and reading various data stored in the memory unit 3000.

[0043] <Functional Configuration of Account Management Server> Next, the functional configuration of the seller's account management server 4b will be explained using Figures 3 and 4. As shown in Figure 4, the account management server 4b has a transmitting / receiving unit 41, a determination unit 45, a creation unit 46, and a storage / reading processing unit 49. Each of these units is a function or means of functioning, realized by any of the components shown in Figure 3 operating according to instructions from the CPU 101 following a program deployed from the HD 104 onto the RAM 103. The account management server 4b also has a storage unit 4000 constructed from the RAM 103 and HD 104 shown in Figure 3.

[0044] (Deposit and withdrawal information management table) Figure 8 is a conceptual diagram showing the deposit and withdrawal information management table. The memory unit 4000 has a deposit and withdrawal information management DB 4004 constructed, which consists of the deposit and withdrawal information management table shown in Figure 8. This table shows the deposit and withdrawal information for all customers' bank accounts at the financial institution on the seller's side. The data structure of the deposit and withdrawal information management DB 4004 is the same as the data structure of the deposit and withdrawal information management DB 3004 described above, so its explanation is omitted.

[0045] (Functional configuration of the account management server) Next, we will explain in detail the functional configurations of the account management server 4b. In addition, when explaining the functional configurations of the account management server 4b, we will also explain the relationship between each component shown in Figure 3 and the main components necessary to realize each functional configuration of the account management server 4b.

[0046] The transmit / receive unit 41 of the account management server 4b shown in Figure 4 is implemented by instructions from the CPU 101 shown in Figure 3 and the network interface 109, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 100.

[0047] The decision unit 45 is implemented by instructions from the CPU 101 shown in Figure 3 and performs a predetermined decision. The details of the decision will be described later.

[0048] The creation unit 46 is implemented by instructions from the CPU 101 shown in Figure 3, and performs tasks such as creating the screen.

[0049] The memory and read processing unit 49 is implemented by instructions from the CPU 101 and the HDD controller 105 shown in Figure 3, and performs processing such as storing various data in the memory unit 4000 and reading various data stored in the memory unit 4000.

[0050] [Processing or operation of the embodiment] Next, the processing or operation of this embodiment will be described using Figures 9 to 25.

[0051] <Invoice sending process> First, we will explain the invoice sending process using Figure 9. Figure 9 is a sequence diagram showing the invoice sending process.

[0052] On the seller terminal 1, seller A1 operates the seller terminal 1 and inputs the billing details that will form the basis of the invoice, and the reception unit 12 accepts the request for invoice creation (S21). Then, the transmission / reception unit 11 sends a request to the transaction management server 3 for the creation of the invoice and the sending of the URL for the receipt screen (S22). This request includes billing details information that indicates the billing details accepted in step S21. As a result, the transmission / reception unit 31 of the transaction management server 3 receives the request in step S22.

[0053] Next, in the transaction management server 3, the generation unit 34 creates an invoice based on the billing information received in step S22 (S23).

[0054] Furthermore, the generation unit 34 generates an invoice ID for the invoice created in step S23 (S24). The generation unit 34 then writes the generated invoice ID on the invoice. The generation unit 34 may also create the invoice after generating the invoice ID.

[0055] Next, in the transaction management server 3, the storage and reading processing unit 39 registers invoice information in the invoice information management DB 3003, which is information that includes information indicating the billing details of the invoice created in step S23 and the invoice ID created in step S24 (S25).

[0056] Next, in the transaction management server 3, the creation unit 36 ​​creates a receipt screen URL, which is the URL of the receipt screen for receiving the invoice created in step S23 (S26), and the storage / reading processing unit 39 registers the receipt screen URL created in step S26 in the invoice information management DB 3003, associating it with the above invoice information (S27).

[0057] Finally, the sending / receiving unit 31 of the transaction management server 3 sends an email containing the receipt screen URL created in step S26 to the buyer terminal 2. Alternatively, the sending / receiving unit 31 does not have to send the email containing the receipt screen URL directly to the buyer terminal 2. For example, the sending / receiving unit 31 may send the email to a designated email address on the buyer's side, and the buyer terminal 2 may receive the email from the mail server. Note that the method of sending the receipt screen URL is not limited to email. For example, a message containing the receipt screen URL may be sent to the buyer terminal 2 via a messenger application. Furthermore, the creation unit 36 ​​may create a two-dimensional code indicating the receipt screen URL, embed the two-dimensional code in the invoice image, the sending / receiving unit 31 may send the invoice image with the embedded two-dimensional code to a printing device, print the invoice image on recording paper, and mail the printed paper invoice to the buyer.

[0058] <Display process for receipt screen> Next, the display process of the receipt screen will be explained using Figures 10 to 13. Figure 10 is a sequence diagram showing the display process of the receipt screen. Figure 11 is a flowchart showing the creation process of the receipt screen.

[0059] First, on the buyer terminal 2, when buyer B1 operates the buyer terminal 2 to open the link to the receipt screen shown in Figure 12, the reception unit 22 receives the request to open the link (S41). Specifically, the reception unit 22 receives the operation to click the receipt screen URL included in the email sent by the transaction management server 3 to the buyer terminal 2 in step S28 above.

[0060] Next, when the reception unit 22 receives an operation to open the link to the receipt screen (S41), the send / receive unit 21 of the purchaser terminal 2 sends a request for the screen data of the receipt screen to the transaction management server 3 (S42).

[0061] Next, in the transaction management server 3, the creation unit 36 ​​creates the receipt screen in response to the request for screen data for the receipt screen (S43). Here, the process of creating the receipt screen will be explained in detail using Figure 11.

[0062] <Process for creating the receipt screen> As shown in Figure 11, the storage and retrieval processing unit 39 searches the invoice information management DB 3003 (see Figure 7) using the requested receipt screen URL as a search key, and retrieves the corresponding billing name and invoice ID (S201). Next, the storage and retrieval processing unit 39 searches the remittance source account information management DB 3002 (see Figure 6) using the retrieved billing name as a search key, and retrieves the remittance source account information corresponding to the remittance source name that matches the billing name (S202).

[0063] If the source account information is not read (S203:NO), that is, if the account information of buyer B1 as the source account information is not registered, the creation unit 36 ​​creates screen data for the receipt screen that displays the remittance data download instruction area, described later, in pattern 1 (S204). On the other hand, if the source account information is read (S203:YES), that is, if the account information of buyer B1 as the source account information is already registered, the creation unit 36 ​​includes the said source account information and the invoice ID read in step S201 in the screen data for the receipt screen (S205), and creates screen data for the receipt screen that displays the remittance data download instruction area, described later, in pattern 2 (S206). With this, the process of creating the receipt screen is completed.

[0064] Next, the send / receive unit 31 of the transaction management server 3 sends the screen data of the created receipt screen to the buyer terminal 2 (S44).

[0065] Finally, in the buyer terminal 2, the display control unit 24 displays a receipt screen on the display 106 based on the screen data of the receipt screen.

[0066] Figures 12 and 13 show examples of the receipt screen displayed on the purchaser's terminal 2.

[0067] <Receipt Screen> Here, we will explain the receipt screen displayed on the buyer's terminal 2 using Figures 12 and 13. Figure 12 shows the receipt screen displayed on the buyer's terminal when the source bank account information for the transfer is not registered. As shown in Figure 12, the receipt screen includes an invoice preview display field g1, an invoice ID display field g11, an invoice download button b11, a remittance data download button b12, and a receipt button b14.

[0068] Of these, the invoice preview display field g1 shows a preview image of the invoice. The invoice preview image may be a reduced version of the invoice image, or it may be the invoice image itself. Also, if the invoice contains multiple pages, the image of the first page may be displayed as the preview image. The invoice ID display field g11 shows the invoice ID.

[0069] Additionally, the invoice download button b11 is for downloading the invoice image to the buyer's terminal 2. The remittance data download button b12 is for downloading remittance data containing the invoice ID to the buyer's terminal 2 after entering the remitter's bank account information. The receipt button b14 is for notifying the seller that the invoice has been received.

[0070] Figure 13 shows the receipt screen displayed on the buyer's terminal when the source account information for the transfer has been registered. As shown in Figure 13, the receipt screen includes an invoice preview display field g2, an invoice ID display field g21, an invoice download button b21, a first remittance data download button b22, a second remittance data download button b23, and a receipt button b24. The invoice preview display field g2, invoice ID display field g21, invoice download button b21, and receipt button b24 are the same as the invoice preview display field g1, invoice ID display field g11, invoice download button b11, and receipt button b14 shown in Figure 12, so their explanations are omitted.

[0071] The first remittance data download button b22 is for downloading remittance data, including the invoice ID of the invoice, to the buyer terminal 2 without changing the registered source account information. The second remittance data download button b22 is for downloading remittance data, including the invoice ID of the invoice, to the buyer terminal 2 after changing the registered source account information.

[0072] In other words, whether the account information of buyer B1 as the source account information for the transfer is registered or not determines whether the remittance data download button b12 is displayed on the receipt screen, or whether the first remittance data download button b22 and the second remittance data download button b23 are displayed.

[0073] <Process to retrieve invoice image> Next, we will explain the process of acquiring the invoice image using Figure 14. Figure 14 is a sequence diagram showing the process of acquiring the invoice image.

[0074] First, when the buyer terminal 2 receives an operation in which the reception unit 22 clicks the invoice download button b11 or b21 displayed on the receipt screen (S61), the transmission / reception unit 21 sends a data request for the invoice image of the invoice and the invoice ID of the invoice to the transaction management server 3 (S62).

[0075] Next, in the transaction management server 3, the storage and reading processing unit 39 searches the invoice information management DB 3003 using the transmitted invoice ID as a search key to read the location where the invoice image is stored and retrieve the invoice image. Then, the transmitting and receiving unit 21 of the transaction management server 3 transmits the retrieved invoice image to the buyer terminal 2 (S63).

[0076] Next, in the purchaser terminal 2, the storage and reading processing unit 29 stores the invoice image in a predetermined storage location in the storage unit 2000 (S64). The predetermined storage location may be the default storage location or a storage location specified by purchaser B1.

[0077] Finally, in the purchaser terminal 2, the reception unit 22 receives an operation to click one of the remittance data download button b12 displayed on the receipt screen in Figure 12, the first remittance data download button b22, or the second remittance data download button b23 displayed on the receipt screen in Figure 13 (S65). Here, when the reception unit 22 receives an operation to click the remittance data download button b12 displayed on the receipt screen in Figure 12, it identifies "T1" as the download type ID. Also, when the reception unit 22 receives an operation to click the first remittance data download button b22 displayed on the receipt screen in Figure 13, it identifies "T2" as the download type ID. Furthermore, when the reception unit 22 receives an operation to click the second remittance data download button b23 displayed on the receipt screen in Figure 13, it identifies "T3" as the download type ID.

[0078] <Processing of downloading remittance data> Next, the remittance data download process will be explained using Figures 15 to 21. Figure 15 is a sequence diagram showing the remittance data download request process when the download type ID is T1. Figure 16 is a sequence diagram showing the remittance data download request process when the download type ID is T3. Figure 17 is a sequence diagram showing the remittance data download request process when the download type ID is T2. Figure 18 is a diagram showing the new account information registration screen displayed on the buyer's terminal. Figure 19 is a diagram showing the account information change screen displayed on the buyer's terminal. Figure 20 is a sequence diagram showing the remittance data download process. Figure 21 is a diagram showing an example of remittance data.

[0079] When T1 is identified as the download type ID, the display control unit 24 on the purchaser terminal 2 first displays the new account information registration screen on the display 106, as shown in Figure 15 (S111). Figure 18 shows an example of the new account information registration screen displayed on the purchaser terminal 2. This new account information registration screen displays account information items such as bank name, branch name, account type, account number, and account holder name, as well as a download start button and a cancel button. The initial value of each item is "empty". The new account information registration screen may be displayed by transitioning from the receipt screen, or it may be displayed as a pop-up screen above the receipt screen.

[0080] Next, the reception unit 22 accepts the input operation of item values ​​for each item on the new account information registration screen (S112). Specifically, the reception unit 22 accepts the operation by purchaser B1 to select the item values ​​for bank name, branch name, and account type from pull-down lists, and to input the item values ​​for account number and account holder name into text boxes. Figure 18 shows the state after the item values ​​for each item have been entered. Next, the reception unit 22 accepts the operation to click the download button on the new account information registration screen (S113). If the reception unit 22 accepts the operation to click the cancel button on the new account information registration screen, the display control unit 24 displays the receipt screen.

[0081] Next, when the reception unit 22 receives the operation of clicking the download button on the new account information registration screen, the send / receive unit 21 of the purchaser terminal 2 sends a request to download the remittance data, the account information entered via the new account information registration screen, and the invoice ID to the transaction management server 3 (S114). Finally, the storage / reading processing unit 39 of the transaction management server 3 stores the transmitted account information in the remitter account information management DB 3002 (S115). This allows the account information of purchaser B1 to be registered via the new account information registration screen when the account information of purchaser B1 as the remitter account information is not already registered.

[0082] When T3 is identified as the download type ID, the display control unit 24 on the purchaser terminal 2 first displays the account information change screen on the display 106, as shown in Figure 16 (S121). The account information change screen is the same as the new account information registration screen in Figure 18, except for the screen title. The account information change screen also displays the account information of purchaser B1 as the registered source account information for transfers, with the initial values ​​of each item being displayed.

[0083] Next, the reception unit 22 accepts the operation to change the item values ​​of each item on the account information change screen (S122). Specifically, the reception unit 22 accepts the operation by purchaser B1 to change the item values ​​of the registered bank name, branch name, and account type displayed in the pull-down list, and the operation to change the item values ​​of the registered account number and account holder name displayed as initial values ​​in the text box. Figure 19 is a diagram showing an example of the display of the account information change screen after the reception unit 22 has accepted the change operation, as displayed on the purchaser terminal 2.

[0084] Next, the reception unit 22 receives the operation to click the download button on the account information change screen (S123). When the reception unit 22 receives the operation to click the download button on the account information change screen, the send / receive unit 21 of the purchaser terminal 2 sends the request to download the remittance data, the changed account information entered via the account information change screen, and the invoice ID to the transaction management server 3 (S124). Finally, the storage / reading processing unit 39 of the transaction management server 3 stores the transmitted account information in the remittance source account information management DB 3002. This makes it possible to change the registered account information via the account information change screen, even if the account information of purchaser B1 has already been registered as the remittance source account information.

[0085] When T2 is identified as the download type ID, as shown in Figure 17, the receiving unit 22 of the purchaser terminal 2 receives an operation in which the purchaser clicks the first remittance data download button b22 displayed on the receipt screen, and the sending / receiving unit 21 sends the remittance data download request, account information, and invoice ID to the transaction management server 3 (S131). In this case, the account information of purchaser B1 as registered remittance source account information is not changed.

[0086] Next, as a continuation of the processes shown in Figures 15, 16, and 17, as shown in Figure 20, first, in the transaction management server 3, the storage / read processing unit 39 searches the remitter account information management DB 3002 using the remitter name contained in the account information transmitted in step S114, step S124, or step S131 as the search key, and obtains the latest remitter account information corresponding to the remitter name (S141). Alternatively, the account information transmitted in step S114, step S124, or step S131 may be obtained as the latest account information.

[0087] Next, the generation unit 34 generates remittance data based on the invoice ID transmitted in step S114, step S124, or step 131 and the source account information obtained in step S141 (S142). Specifically, the storage and retrieval processing unit 39 uses the invoice ID as a search key to search the invoice information management DB 3003 and obtains invoice information such as the tenant ID, invoice amount, and payment due date corresponding to the invoice ID. The storage and retrieval processing unit 39 also uses the obtained tenant ID as a search key to search the tenant information management DB 3001 and obtains the account information corresponding to the tenant ID as the recipient account information. The generation unit 34 then generates remittance data in which the invoice ID, source account information, recipient account information, invoice amount as the remittance amount, and payment due date as the remittance date are embedded according to a predetermined format.

[0088] Furthermore, the amount of the invoice that buyer B1 has changed via a designated screen may be embedded in the remittance data as the transfer amount, or a date calculated based on a designated rule for the payment due date, such as the date 10 days prior or the last day of the previous month, may be embedded in the remittance data as the transfer date, or a date entered by buyer B1 via a designated screen may be embedded in the remittance data as the transfer date. The information embedded in the remittance data may include one or more of the following: information such as the billing name and delivery date included in the invoice information, information regarding the return of goods or services corresponding to the invoice information, and information indicating that an amount overpaid by buyer B1 to seller A1 in past commercial transactions will be offset by the remittance using the remittance data.

[0089] Figure 21 shows an example of remittance data. As shown in Figure 21, the remittance data includes information such as the sender's account information, the recipient's account information, the transfer amount, the transfer date, and the invoice ID. The remittance data shown in Figure 21 is written in XML (Extensible Markup Language) format, but is not limited to this format. The remittance data may also be written in JSON (JavaScript Object Notation) format, CSV (Comma-Separated Values) format, or text format.

[0090] Next, the transceiver unit 31 of the transaction management server 3 sends the generated remittance data to the buyer terminal 2 (S143).

[0091] Next, in the buyer terminal 2, the storage and reading processing unit 29 stores the remittance data in a predetermined storage location in the storage unit 2000 (S144). The predetermined storage location may be the default storage location or a storage location specified by the buyer B1. Then, when the receiving unit 22 receives the operation of clicking the receive button b14 displayed on the receipt screen (S145), the sending and receiving unit 21 sends the receipt notification and invoice ID to the transaction management server 3 (S146).

[0092] Finally, the memory and read processing unit 39 of the transaction management server 3 searches the invoice information management DB 3003 using the invoice ID as a search key to identify the invoice information corresponding to the invoice ID, and changes the receipt status of the identified invoice information from "not received" to "received" (S147).

[0093] This allows service provider C to create remittance data, including the invoice and invoice ID, and send it to client company B.

[0094] Next, buyer B1 instructs the financial institution D1 to execute the transfer using the downloaded transfer data, following a predetermined procedure. For example, buyer B1 instructs the transfer by uploading the transfer data through a designated screen provided by financial institution D1, such as a corporate banking or internet banking service that manages buyer B's account. Financial institution D1 then transfers the amount specified in the transfer data to financial institution D2, which manages seller A1's account, and also sends information such as the invoice ID included in the transfer data to financial institution D2. As a result, seller A1 can obtain the transfer information, including the invoice ID, from financial institution D2.

[0095] Furthermore, remittances based on remittance data are not limited to being conducted through financial institutions. For example, remittances may be made through services such as online payment services. In this case, for example, service provider C could send a two-dimensional code indicating the remittance data to purchaser B1, and purchaser B1 could make the remittance by having the online payment service application installed on purchaser terminal 2 read the two-dimensional code.

[0096] <Reconciliation Process> Next, the reconciliation process will be explained using Figures 22 to 25. Figure 22 is a sequence diagram showing the reconciliation process. Figure 23 is a transition diagram of the deposit and withdrawal information management table. Figure 24 is a flowchart of the automatic reconciliation process. Figure 25 is a diagram showing the automatic reconciliation results screen displayed on the seller's terminal.

[0097] First, as shown in Figure 22, in the seller terminal 1, the reception unit 12 receives the tenant ID and password input from seller A1, performs a predetermined user authentication process, and then receives an operation to instruct the start of reconciliation. Specifically, the reception unit 12 receives an operation in which seller A1 clicks the start button displayed on a predetermined screen (S161). Then, the transmission / reception unit 11 sends a request to start reconciliation to the transaction management server 3 (S162).

[0098] Next, the transmitting / receiving unit 31 of the transaction management server 3 sends a request for remittance information and a tenant ID to the seller's account management server 4b, which manages the account of seller A1 (S163). Then, the transmitting / receiving unit 41 of the seller's account management server 4b sends the remittance information to seller A1's account, obtained based on the tenant ID, to the transaction management server 3 (S164). This remittance information includes an invoice ID. Here, the seller's account management server 4b may be a server device provided by the financial institution that manages seller A1's account, or it may be a server device provided by a predetermined service that cooperates with the financial institution's system.

[0099] Furthermore, the seller's account management server 4b performs a predetermined authentication process when sending remittance information to seller A1's account to the transaction management server. For example, seller A1 registers the authentication information for seller A1's account with the transaction management server 3 via seller terminal 1, and the transceiver unit 31 of the transaction management server 3 sends the authentication information identified based on the tenant ID, along with the remittance information request, to the seller's account management server 4b. Then, the storage and reading processing unit 49 of the seller's account management server 4b performs an authentication process based on the transmitted authentication information, reads the remittance information corresponding to the authentication information from the remittance information stored in the deposit and withdrawal information management DB 4004, and finally, the transceiver unit 41 sends the read remittance information to the transaction management server 3.

[0100] Next, in the transaction management server 3, the storage and reading processing unit 39 registers the transmitted remittance information in the deposit and withdrawal information management DB 3004, associating it with the tenant ID (S165). Here, the invoice ID included in the remittance information is also registered in the deposit and withdrawal information management DB 3004. Figure 23 shows the difference in the deposit and withdrawal information management DB 3004 before and after the transmitted remittance information is stored in the deposit and withdrawal information management DB 3004. As shown in Figure 23, the transmitted remittance information (remittance information corresponding to remittances where the deposit source is "Ka) B1" and the deposit amounts are 200,000 and 550,000) has been added to the deposit and withdrawal information management DB 3004, associating it with the tenant ID. Note that "Not settled" is registered as the initial value for the settlement status of the added remittance information.

[0101] Next, the transaction management server 3 performs an automatic reconciliation process based on the invoice information and remittance information (S166). Figure 24 is a flowchart showing the details of the automatic reconciliation process.

[0102] As shown in Figure 24, first, the storage and retrieval processing unit 39 retrieves unreconciled deposit information for seller A1 from the deposit and withdrawal information management DB 3004 (S221). Specifically, it retrieves remittance information for seller A1 that is "unreconciled" among the deposit and withdrawal information for seller A1 identified based on seller A1's tenant ID. Here, the storage and retrieval processing unit 39 retrieves deposit and withdrawal information for which the payment amount and payee are "empty" as remittance information.

[0103] Next, a reconciliation process is performed for each acquired payment information (S222). Specifically, the determination unit 35 acquires the invoice ID included in the remittance information (S223). If the invoice ID can be acquired (S224-YES), the storage / reading processing unit 39 uses the invoice ID as a search key to search the invoice information management DB 3003 and acquire the invoice information corresponding to the invoice ID (S225). On the other hand, if the invoice ID cannot be acquired (S224-NO), the storage / reading processing unit 39 changes the "reconciliation status" of the remittance information from "not reconciled" to "incomplete" (S229).

[0104] Next, the determination unit 35 compares the billed amount included in the invoice information with the received amount (amount received) included in the remittance information (S226). If the billed amount and the received amount match (S227-YES), the storage / reading processing unit 39 changes the payment status of the invoice information in the invoice information management DB 3003 from "awaiting payment" to "reconciliation complete" and changes the "reconciliation status" of the remittance information in the deposit / withdrawal information management DB 3004 from "not reconciled" to "reconciliation complete" (S228). On the other hand, if the billed amount and the received amount do not match (S227-NO), the storage / reading processing unit 39 changes the "reconciliation status" of the remittance information from "not reconciled" to "incomplete" (S229).

[0105] In this way, by performing a reconciliation process for each acquired deposit information, the reconciliation process for all acquired deposit information is completed.

[0106] Next, in the transaction management server 3, the creation unit 36 ​​creates screen data for the automatic reconciliation result screen, which shows the result of the automatic reconciliation process, based on the invoice information and remittance information for which the automatic reconciliation process in step S166 was performed, and the transmission / reception unit 31 transmits the created screen data for the automatic reconciliation result screen to the seller terminal 1 (S167). Finally, the display control unit 14 of the seller terminal 1 displays the automatic reconciliation result screen on the display 106 based on the transmitted screen data (S168).

[0107] Figure 25 shows an example of the automatic reconciliation results screen displayed on the seller terminal 1. As shown in Figure 25, the automatic reconciliation results screen includes items such as invoice ID, customer ID, customer name, invoice amount, payment status, and payment date. For example, it shows that the payment status of invoice ID 1054 is "awaiting payment". It also shows that the payment status of invoices IDs 1055 and 1056 is "reconciliation completed".

[0108] In this way, seller A1 can check the collection information for accounts receivable related to each invoice via the automatic reconciliation results screen.

[0109] [Variation 1: Transfer reflecting offsetting information] For various reasons related to the transaction, the amount transferred may differ from the amount stated on the invoice. For example, if some of the delivered goods are returned due to defects, the amount related to the returned goods may be deducted from the invoiced amount before transfer. Also, if it has been agreed that the invoiced party will bear the transfer fees, the transfer fees may be deducted from the invoiced amount before transfer. The following describes some variations of transfers that reflect these offsetting details.

[0110] <Process for creating the receipt screen> Figure 26 is a flowchart showing the process for creating the receipt screen in this modified example. The process for creating the receipt screen in this modified example differs from the process for creating the receipt screen shown in Figure 11 in that steps S203, S204, and S206 are omitted. In step S202, if the source account information is not extracted, in S205, information indicating that the source account information is not registered is included in the screen data of the receipt screen instead of the source account information.

[0111] <Receipt Screen> Figure 27 shows an example of the receipt screen display in this modified example. In the above embodiment, the receipt screen shown in Figure 12 or the receipt screen shown in Figure 13 was displayed depending on whether or not bank transfer account information was registered. However, in this modified example, the receipt screen shown in Figure 27 is displayed in both cases.

[0112] <Processing of downloading remittance data> In this modified example, the receipt screen behaves differently from the receipt screen shown in Figure 12 when the remittance data download button b12 is pressed. When the reception unit 22 receives an operation to click the invoice download button b12 displayed on the receipt screen, the display control unit 24 displays either the new account information registration screen shown in Figure 28 or the account information change screen shown in Figure 29 on the display 106.

[0113] The display control unit 24 displays the account information change screen if the source account information is read, that is, if the screen data of the receipt screen includes the source account information. On the other hand, the display control unit 24 displays the new account information registration screen if the source account information is not read, that is, if the screen data of the receipt screen includes information indicating that the source account information is not registered.

[0114] Figure 28 shows an example of the display of the new account information registration screen in this modified example. The new account information registration screen in this modified example differs from the new account information registration screen shown in Figure 18 in that a "Next" button is displayed instead of a "Download Start" button. When the reception unit 22 receives an operation to click the "Next" button displayed on the new account information registration screen, the display control unit 24 displays the offset information input screen shown in Figure 30 on the display 106.

[0115] Figure 29 shows an example of the display of the account information change screen in this modified example. The account information change screen in this modified example differs from the account information change screen shown in Figure 19 in that a "Next" button is displayed instead of a "Download Start" button. When the reception unit 22 receives an operation to click the "Next" button displayed on the account information change screen, the display control unit 24 displays the offset information input screen shown in Figure 30 on the display 106.

[0116] Figure 30 shows an example of the display of the offset information input screen in this modified example. As shown in Figure 30, the offset information input screen includes checkboxes c31 to c33 for selecting the offset type, input areas a31 to a33 for entering the offset details corresponding to each offset type, a field g31 for displaying the total offset amount, a field g32 for displaying the transfer amount, a cancel button b31, a back button b32, and a download start button b33.

[0117] Of these, input areas a31 to a33 are not displayed when the offset information input screen is first displayed. When checkboxes c31 to c33 are checked, the input area corresponding to that checkbox is displayed. For example, when checkbox a31, which is used to check if the offset type is a return, is checked, input area a31 for entering the return details is displayed.

[0118] In input area a31, where you enter the details of the return, you can enter the items to be returned. The return items can be entered by directly entering the item name and quantity, or a dropdown list can be generated based on the details included in the invoice, and the customer can select from that list. The total amount g33, which will be offset by the returned items, is automatically calculated and displayed in input area a31.

[0119] To include a pull-down list in input area a31, the item details contained in the invoice should be stored in association with the invoice information. Figure 31 is a conceptual diagram showing the invoice item details management table. In this modified example, the storage unit 3000 has an invoice item details management DB 3005 constructed, which consists of the invoice item details management table shown in Figure 31. In this table, the item, quantity, unit, unit price, and amount are managed in association with each invoice ID.

[0120] When the reception unit 22 receives an operation in which the user clicks the download start button b33 on the offsetting information input screen, the send / receive unit 21 of the purchaser terminal 2 sends the request to download the remittance data, the account information entered via the new account information registration screen or the account information change screen, the offsetting information entered via the offsetting information input screen, and the invoice ID to the transaction management server 3.

[0121] Furthermore, when the reception unit 22 receives an operation in which the user clicks the cancel button b31 on the offsetting information input screen, the display control unit 24 displays the receipt screen. Also, when the reception unit 22 receives an operation in which the user clicks the back button b32 on the offsetting information input screen, the display control unit 24 displays the new account information registration screen or the account information change screen that was displayed before the offsetting information input screen was displayed.

[0122] In the transaction management server 3, the storage and retrieval processing unit 39 stores the transmitted account information in the source account information management DB 3002. The storage and retrieval processing unit 39 also stores the transmitted offsetting information in the invoice information management DB 3003.

[0123] Figure 32 is a conceptual diagram showing the invoice information management table in this modified example. The invoice information management table in this modified example differs from the invoice information management table shown in Figure 7 in that it includes the offset amount and the reason for offset.

[0124] Figure 33 shows an example of remittance data in this modified example. As shown in Figure 33, the remittance data in this modified example includes the reason for the amount offset and the amount of the offset. The transfer amount is the amount stated on the invoice minus the amount of the offset.

[0125] <Reconciliation Process> Figure 34 is a flowchart showing the automatic redemption process in this modified example. Compared to the automatic redemption process shown in Figure 24, the automatic redemption process in this modified example differs in that the processing content of step S226 is different, and steps S228, S229, and S231 are added.

[0126] The following explains only the differences from the automatic reconciliation process shown in Figure 24. The determination unit 35 compares the invoice amount, billing address, and tenant company name included in the invoice information with the payment amount, payment source, and payment destination included in the remittance information (S226). If any of the invoice amount, billing address, and tenant company name included in the invoice information and the payment amount, payment source, and payment destination included in the remittance information do not match (S227-NO), the invoice amount included in the invoice information and the payment amount included in the remittance information are compared (S228).

[0127] If the billed amount and the received amount match (S228-YES), the storage / reading processing unit 39 changes the "reconciliation status" of the remittance information from "not reconciled" to "incomplete" (S232). On the other hand, if the billed amount and the received amount do not match (S228-NO), the determination unit 35 determines whether the offset amount included in the invoice information is 0, and whether the sum of the offset amount and the received amount matches the billed amount (S229).

[0128] If the offset amount included in the invoice information is not zero, and the sum of the offset amount and the received amount matches the invoice amount (S229-YES), the storage / reading processing unit 39 changes the "reconciliation status" of the remittance information from "unreconciled" to "offset present, requires confirmation" (S231). On the other hand, if the offset amount included in the invoice information is zero, or the sum of the offset amount and the received amount does not match the invoice amount (S229-NO), the storage / reading processing unit 39 changes the "reconciliation status" of the remittance information from "unreconciled" to "incomplete" (S232).

[0129] Figure 35 shows an example of the display of the automatic reconciliation results screen in this modified example. The automatic reconciliation results screen in this modified example differs from the automatic reconciliation results screen shown in Figure 25 in that it includes additional detail confirmation buttons b41 and b42 corresponding to each invoice for which reconciliation has not been completed.

[0130] When the reception unit 22 receives an operation in which the user clicks the detailed confirmation buttons b41 and b42 on the automatic reconciliation results screen, the display control unit 24 displays the invoice information confirmation screen shown in Figure 36 on the display 106.

[0131] Figure 36 shows an example of the display of the invoice information confirmation screen in this modified example. As shown in Figure 36, the invoice information confirmation screen includes items such as payment date, payment amount, payment source, invoice ID, billing recipient, invoice amount, offset amount, and offset reason. The invoice information confirmation screen also includes a cancel button b51 and a reconciliation complete button b52.

[0132] When the reception unit 22 receives the operation of clicking the reconciliation complete button b52 on the invoice information confirmation screen, the send / receive unit 21 of the purchaser terminal 2 sends the reconciliation request and the invoice ID to the transaction management server 3. In the transaction management server 3, the storage / reading processing unit 39 changes the payment status of the invoice information in the invoice information management DB 3003 from "awaiting payment" to "reconciliation complete," and changes the "reconciliation status" of the remittance information in the deposit / withdrawal information management DB 3004 from "offsetting required confirmation" to "reconciliation complete."

[0133] Furthermore, when the reception unit 22 receives an operation in which the user clicks the cancel button b51 on the invoice information confirmation screen, the display control unit 24 displays the automatic reconciliation results screen.

[0134] [Variation 2: Bank transfer of multiple invoices] When multiple invoices are issued by the same billing source, it is common practice to transfer the total amount of all invoices in a single bank transfer, primarily to reduce transfer fees. The following describes variations of transferring multiple invoices together.

[0135] <Display process for receipt screen> On the buyer terminal 2, buyer B1 operates the buyer terminal 2 to open the link to the receipt screen for each business partner, as shown in Figure 37, and the reception unit 22 accepts the processing to open the link. The links to the receipt screen for each business partner are generated in advance for each business partner and are stored in association with the billing ID in the invoice information management DB 3003, for example. When the sending and receiving unit 31 of the transaction management server 3 sends an email containing the receipt screen URL of the created invoice to the buyer terminal 2, it includes the receipt screen URL for each business partner.

[0136] Next, when the reception unit 22 receives an operation to open the link to the receipt screen for each trading partner, the send / receive unit 21 of the buyer terminal 2 sends a request for screen data for the receipt screen for each trading partner to the transaction management server 3. Subsequently, in response to the request for screen data for the receipt screen for each trading partner, the creation unit 36 ​​of the transaction management server 3 creates the receipt screen for each trading partner.

[0137] <Process for creating the receipt screen> The memory and retrieval processing unit 39 retrieves the corresponding billing ID by searching the invoice information management DB 3003 using the URL of the receipt screen for each requested business partner as the search key. Next, the memory and retrieval processing unit 39 retrieves the invoice information issued by the business partner to the billing partner by searching the invoice information management DB 3003 using the retrieved billing ID as the search key.

[0138] The creation unit 36 ​​creates screen data for the receipt screen for each business partner, including the read invoice information. Subsequently, the transmission / reception unit 31 sends the created receipt screen data to the buyer terminal 2.

[0139] <Receipt screen for each business partner> Figure 37 shows the receipt screen for each business partner in this modified example. As shown in Figure 37, the receipt screen for each business partner includes an invoice list display field g61, checkboxes c61-c62 for selecting invoices, and a remittance data download button b61.

[0140] Of these, the invoice list display field g61 includes items such as invoice ID, invoice amount, payment due date, and mailing date. In addition, each invoice information is associated with and displays detailed information including items, quantity, unit, unit price, and amount. Furthermore, each invoice information includes an invoice download button b62 and a receipt button b63.

[0141] Of these, the remittance data download button b61 is a button for downloading remittance data containing the invoice ID of invoices for which checkboxes c61~c62 are checked to the buyer's terminal 2. The invoice download button b62 is a button for downloading the invoice image of the invoice to the buyer's terminal 2. The receipt button b63 is a button for notifying the seller that the invoice has been received.

[0142] <Processing of downloading remittance data> When the reception unit 22 receives an operation in which the customer clicks the remittance data download button b61 on the receipt screen for each trading partner, the send / receive unit 21 of the purchaser terminal 2 sends the remittance data download request, the account information entered via the new account information registration screen or the account information change screen, and the multiple invoice IDs selected via the receipt screen for each trading partner to the transaction management server 3.

[0143] Figure 38 shows an example of remittance data in this modified example. As shown in Figure 38, the remittance data in this modified example includes multiple invoice details (Invoice 1, Invoice 2, ...). The transfer amount is the sum of the invoice amounts listed on the invoices included in the remittance data.

[0144] <Reconciliation Process> Figure 39 is a flowchart showing the automatic redemption process in this modified example. Compared to the automatic redemption process shown in Figure 24, the automatic redemption process in this modified example differs in that the processing content of step S227 is different, and steps S225, S228, and S229 are added.

[0145] The following explains only the differences from the automatic reconciliation process shown in Figure 24. If the determination unit 35 has acquired multiple invoice IDs in step S223 (S225-YES), the storage and reading processing unit 39 uses each invoice ID as a search key to search the invoice information management DB 3003 and acquires all invoice information corresponding to the acquired invoice IDs (S228).

[0146] Next, the determination unit 35 compares the total billing amount, the billing recipient, and the tenant company name included in the invoice information with the received amount, the source of the payment, and the recipient of the payment included in the remittance information (S229).

[0147] If the total amount billed, the name of the billing party and the tenant company included in the invoice information and the amount received, the source and recipient of the payment included in the remittance information all match (S230-YES), the storage and reading processing unit 39 changes the payment status of the invoice information in the invoice information management DB 3003 from "awaiting payment" to "reconciliation complete" and changes the "reconciliation status" of the remittance information in the deposit and withdrawal information management DB 3004 from "not reconciled" to "reconciliation complete" (S231).

[0148] On the other hand, if the total amount billed, the name of the billing party and tenant company do not match the amount received, the source and recipient of the payment included in the remittance information (S230-NO), the storage and reading processing unit 39 changes the "reconciliation status" of the remittance information from "not reconciled" to "incomplete" (S232).

[0149] [Variation 3: Combination of Variations] By combining Modification 1 with Modification 2, it is also possible to reflect offsetting information in a combined bank transfer of multiple invoices. In this case, the offsetting information input screen is configured to allow input of offsetting information for each invoice.

[0150] Figure 40 shows an example of the offsetting information input screen when Modification 1 and Modification 2 are combined. As shown in Figure 40, the offsetting information input screen in this modification includes tabs t71 to t72 corresponding to each invoice information selected on the receipt screen for each trading partner. The structure of each tab t71 to t72 is the same, and includes checkboxes c31 to c33 for selecting the offsetting type, input areas a31 to a33 for entering the offsetting details corresponding to each offsetting type, and a display field g31 for the total offsetting amount.

[0151] Of these, the total offset amount display field g31 shows the sum of the offset amounts entered in that tab. The transfer amount display field g32 shows the amount obtained by subtracting the sum of the offset amounts from all tabs from the sum of the invoice amounts from all invoice information.

[0152] Figure 41 shows an example of remittance data in this modified example. As shown in Figure 41, the remittance data in this modified example includes multiple invoice information (Invoice 1, Invoice 2, ...). Each invoice information also includes the reason for offsetting the amount and the amount of the offset. Furthermore, the transfer amount is the sum of the invoice amounts listed on the invoices included in the remittance data minus the sum of the offset amounts.

[0153] [Main effects of this embodiment] As described above, according to this embodiment, the transaction management server 3, which manages multiple invoices relating to commercial transactions between the seller and the buyer, generates remittance data (see Figure 21) that includes invoice identification information identifying the invoice relating to the commercial transaction issued to the buyer, and is used for remittance from the buyer's account to the seller's account based on the invoice (see S3), and transmits this generated remittance data to the buyer's terminal (see S143). In this way, by using invoice identification information to identify invoices, it becomes possible to identify the document corresponding to the payment information from the purchaser, thus reducing the effort required for reconciliation.

[0154] 〔supplement〕 Seller terminal 1 is an example of a communication terminal. Seller terminal 1 includes not only PCs, but also smartwatches, game consoles, and video call devices. The presenter terminal is another example of a communication terminal.

[0155] Each component, such as each CPU 101, may be single or multiple.

[0156] Furthermore, each of the functions in the above-described embodiments can be realized by one or more processing circuits. Here, the "processing circuit" in this embodiment includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, and devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), SOCs (System on a chip), GPUs, and conventional circuit modules designed to execute each of the above-described functions.

[0157] Furthermore, the servers 3, 5, and 7 described in the above embodiments represent only one of several computing environments for carrying out the embodiments disclosed herein. For example, the transaction management server 3 may include multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a communication network and shared memory, and to perform the processing disclosed herein. Similarly, the transaction management server 3 may include multiple computing devices configured to communicate with each other.

[0158] Furthermore, the transaction management server 3 can be configured to share the disclosed processing steps in various combinations. For example, processes executed by the transaction management server 3 may be executed by other servers. Similarly, the functions of the transaction management server 3 may be executed by other servers. Also, each element of the transaction management server 3 and the other servers may be combined into a single server or divided among multiple devices.

[0159] Furthermore, other servers, routers, etc., may relay data during communication between the seller terminal 1, the buyer terminal 2, the transaction management server 3, the account management server 4a, and the account management server 4b.

[0160] 〔summary〕 The following is a summary of this embodiment. Note that the statements in parentheses are not intended to limit the scope of the claims, but are merely illustrative examples.

[0161] (1) The transaction management server 3, which manages multiple invoices relating to commercial transactions between the seller and the buyer, generates remittance data (see Figure 21) that includes invoice identification information identifying the invoice relating to the commercial transaction issued to the buyer, and is used for remittances based on the invoice from the buyer's account to the seller's account (see S3), and transmits this generated remittance data to the buyer's terminal (see S2, S143).

[0162] (2) The transaction management server 3 receives remittance information (see one record in Figure 23) that shows the details of the remittance and includes invoice identification information, which has been sent by the account management server that manages the purchaser's account (see S164). Based on the specific invoice indicated by the invoice identification information included in the remittance information and the remittance information, the server performs reconciliation processing for the specific invoice (see S166, S228).

[0163] (3) The transaction management server 3 receives billing information that shows the billing details of the invoice, which has been sent by the seller's terminal (S22), and generates an invoice based on the billing information (S24).

[0164] (4) The transaction management server receives a request from the seller terminal to send an address (e.g., a URL) to the buyer for the buyer to obtain the invoice (S22), and based on this request, sends the address to the buyer (S28), and sends data for a receipt screen to obtain remittance data including invoice identification information to the buyer terminal in response to the buyer's access to the address from the buyer terminal (S41, S42) (S44). [Explanation of Symbols]

[0165] 1. Seller's terminal 2. Purchaser's device 3 Transaction Management Server 4a Account management server 4b Account Management Server 31 Transmitting and Receiving Unit (Example of transmitting means, example of receiving means) 34. Generation Unit (Example of Generation Means) 35. Judgment Unit (An example of a judgment means) 39 Memory and Retrieval Processing Unit 100 Communication Networks 3000 Memory Unit (An example of a memory means)

Claims

1. In a transaction management server that manages multiple invoices related to commercial transactions between sellers and buyers, Receiving means that receive billing information indicating the billing details of the invoice from the seller's terminal and receive offsetting information related to the invoice from the buyer's terminal, A generating means generates remittance data, which includes invoice identification information and offsetting information that identify an invoice relating to the commercial transaction issued to the purchaser, and which is used to remit funds from the purchaser's account to the seller's account based on the invoice, based on the invoice details information and offsetting information received by the receiving means, The system includes a transmission means for transmitting the remittance data generated by the generation means to the purchaser's purchaser terminal, The receiving means receives remittance information from the account management server that manages the purchaser's account, which indicates the details of the remittance and includes the invoice identification information and the offsetting information. The system further includes a reconciliation means that, with respect to a specific invoice among the multiple invoices indicated by the invoice identification information included in the remittance information, identifies the amount to be offset using the offsetting information, and if the identified amount to be offset is not zero, and the sum of the identified amount to be offset and the amount received included in the remittance information matches the invoice amount of the specific invoice, changes the reconciliation status of the remittance information from unreconciled to offsetting, requiring confirmation. A transaction management server characterized by the following features.

2. In the transaction management server described in claim 1, The generation means generates the remittance data including a plurality of invoice identification information and a plurality of offsetting information, The reconciliation means identifies the total amount to be offset using the offsetting information for a plurality of specific invoices indicated by the plurality of invoice identification information contained in the remittance information, and if the identified total amount to be offset is not zero, and the sum of the identified total amount to be offset and the amount received contained in the remittance information matches the total invoice amount for the specific invoice, the reconciliation status of the remittance information is changed from unreconciled to offsetting required confirmation. A transaction management server characterized by the following features.

3. In the transaction management server according to claim 1 or 2, The receiving means receives a request from the seller's terminal of the seller to send to the buyer an address for the buyer to obtain the invoice. The transmission means transmits the address to the purchaser based on the request. The transmission means transmits the data of the receipt screen for obtaining the remittance data, including the invoice identification information, to the purchaser's terminal in response to the purchaser's access to the address from the purchaser's terminal. A transaction management server characterized by the following:

4. The transaction management server according to any one of claims 1 to 3, characterized in that the aforementioned invoice identification information is an invoice ID or an invoice number.

5. A communication system comprising a transaction management server for managing multiple invoices relating to commercial transactions between a seller and a buyer, a buyer terminal of the buyer, and a seller terminal of the seller, The aforementioned transaction management server, The seller's terminal receives billing information indicating the billing details of the invoice. The purchaser's terminal receives offsetting information regarding the invoice, Based on the received billing information and offsetting information, a remittance data is generated which includes invoice identification information and offsetting information that identify the invoice relating to the commercial transaction issued to the purchaser, and which is used for remittance from the purchaser's account to the seller's account based on the invoice. The generated remittance data is transmitted to the purchaser's terminal. The account management server that manages the account of the aforementioned purchaser receives remittance information indicating the details of the remittance, which includes the invoice identification information and the offsetting information. For a specific invoice among the multiple invoices indicated by the invoice identification information included in the remittance information, the amount to be offset is identified using the offsetting information. If the identified amount to be offset is not zero, and the sum of the identified amount to be offset and the amount received included in the remittance information matches the invoice amount of that specific invoice, the reconciliation status of the remittance information is changed from "not reconciled" to "offsetting required, confirmation needed". The aforementioned seller terminal is The aforementioned billing information is transmitted, The aforementioned purchaser's terminal is, The aforementioned offsetting information is transmitted, The remittance data is received, A communication system characterized by the following features.

6. A transaction management method performed by a transaction management server that manages multiple invoices relating to commercial transactions between sellers and buyers, A first receiving step of receiving billing information indicating the billing details of the invoice from the seller's terminal of the seller, A second receiving step of receiving offsetting information relating to the invoice from the purchaser's purchaser terminal, A generation step of generating remittance data that includes invoice identification information and offset information that identify the invoice relating to the commercial transaction issued to the purchaser, based on the received invoice information and offset information, which is used for remittance from the purchaser's account to the seller's account based on the invoice; A transmission step of sending the generated remittance data to the buyer's terminal, A third receiving step of receiving remittance information, which includes the invoice identification information and the offsetting information, from an account management server that manages the account of the aforementioned purchaser, A reconciliation step in which, with respect to a specific invoice among the multiple invoices indicated by the invoice identification information included in the remittance information, the amount to be offset is identified using the offsetting information, and if the identified amount to be offset is not zero, and the sum of the identified amount to be offset and the amount received included in the remittance information matches the invoice amount of the specific invoice, the reconciliation status of the remittance information is changed from unreconciled to offsetting, requiring confirmation. A transaction management method characterized by performing the following actions.

7. A program that causes a computer to execute the transaction management method described in claim 6.

Images