Transfer agency system, transfer agency method and transfer agency program

Abstract

To provide a transfer agency system, a transfer agency method and a transfer agency program for enabling a user to simply perform transfer within a software platform.SOLUTION: According to an embodiment, a transfer agency system 1 includes an account transfer request part 213 for requesting a sending bank to perform account transfer of a payment amount from an account of a payer in the sending bank to an account of a transfer agent of the sending bank or an entrusted party of the transfer agent when a payment date or a date based on the payment date arrives, and a transfer request part 214 for requesting an intermediary bank to perform transfer processing of the payment amount from an account of the transfer agent in the intermediary bank or an entrusted party of the transfer agent to an account of a recipient in a receiving bank when notification that the account transfer from the sending bank is completed is received.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a transfer agency system, a transfer agency method, and a transfer agency program, and more particularly to a transfer agency system, a transfer agency method, and a transfer agency program for acting as an agent for users to transfer money on a software platform provided by a SaaS provider. [Background technology]

[0002] In recent years, SaaS providers have been offering software platforms for invoice management systems, accounting systems, accounts payable systems, payroll systems, and more.

[0003] Conventionally, when using a software platform to pay bills, etc., the general method is for corporate users to output billing data (such as Facebook data) from the software platform, log in to their internet banking account, and upload the billing data. This means that payment processing cannot be performed within the software platform, which is time-consuming and inconvenient for users.

[0004] Another possible method is to use the bank's open API (Application Programming Interface). More specifically, the software platform and EB (Electronic Banking) service could be linked via an API (update API) to execute transfer processing directly from the software platform. However, since only a small number of banks support open APIs, it is difficult to use this as a general-purpose transfer method.

[0005] Patent Document 1 discloses a transfer system that aims to reduce fees associated with bank transfers and remittances. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2021-149388 Summary of the Invention [Problem to be solved by the invention]

[0007] The problem to be solved by the present invention is to provide a transfer agent system, a transfer agent method, and a transfer agent program that allow users to easily make transfers within a software platform. [Means for solving the problem]

[0008] The transfer agent system according to the present invention comprises: an account transfer request unit that requests the sending bank to transfer the payment amount from the payer's account at the sending bank to an account of a transfer agent at the sending bank or an account of a party entrusted by the transfer agent at the sending bank when the payment date or a date based on the payment date arrives; and a transfer request unit that, upon receiving notification from the sending bank that the account transfer has been completed, requests the intermediary bank to transfer the payment amount from the account of the transfer agent or the transfer agent's contractor at the intermediary bank to the recipient's account at the receiving bank.

[0009] In addition, in the transfer agent system, Execution of the account transfer may result in immediate debit of the payment amount from the payer's account.

[0010] In addition, in the transfer agent system, The system may also include a registration unit that, upon receiving a payment instruction requesting a transfer and billing information, registers the payment instruction information, including the payer's debit account and the billing information, in a payment instruction database.

[0011] In addition, in the transfer agent system, When the registration unit receives a notification of completion of the account transfer from the sending bank, it may update the transfer status in the payment instruction database from unprocessed to processed.

[0012] In addition, in the transfer agent system, The registration unit may update the transfer status in the payment instruction database from unprocessed to processed when it receives a notification of completion of the transfer process from the intermediary bank.

[0013] In addition, in the transfer agent system, an information acquisition unit that acquires the transfer status registered in the payment instruction database in response to a request from the payer; The payment system may further include a display control unit that displays the transfer status on the payer's terminal.

[0014] In addition, in the transfer agent system, The sending bank may be a bank designated by the payer.

[0015] In addition, in the transfer agent system, After the account transfer, the bank system of the sending bank may perform a transfer process at a specified transfer timing to transfer the payment amount transferred to the account of the transfer agent or the transfer agent's contractor to the account of the transfer agent or the transfer agent's contractor at the intermediary bank.

[0016] In addition, in the transfer agent system, The banking system of the sending bank may transfer the payment amounts relating to multiple invoices with the same payment date all at once to the account of the intermediary bank.

[0017] The transfer agent method according to the present invention comprises: a step in which, when a payment date or a day based on the payment date arrives, an account transfer request unit requests the sending bank to transfer the payment amount from the payer's account at the sending bank to an account of a transfer agent at the sending bank or an account of a party entrusted by the transfer agent; When the transfer request unit receives notification from the sending bank that the account transfer has been completed, it requests the intermediary bank to transfer the payment amount from the account of the transfer agent or the transfer agent's contractor at the intermediary bank to the recipient's account at the receiving bank.

[0018] The transfer agent program according to the present invention is The transfer agent method is executed by a computer. [Effects of the Invention]

[0019] According to the present invention, it is possible to provide a transfer agent system, a transfer agent method, and a transfer agent program that allow users to easily make transfers within a software platform. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a diagram showing a schematic configuration of a transfer agent system according to an embodiment. [Figure 2] FIG. 2 is a functional block diagram of a user terminal according to the embodiment. [Figure 3] FIG. 2 is a functional block diagram of a transfer agent server according to the embodiment. [Figure 4] 1 is an example of a payment instruction database according to an embodiment. [Figure 5] 10 is an example of a flowchart illustrating pre-registration of information according to an embodiment. [Figure 6] FIG. 10 is an example of a sequence diagram illustrating a payment method according to an embodiment. [Figure 7] 7 is an example of a sequence diagram illustrating a payment method according to the embodiment, following FIG. 6. DETAILED DESCRIPTION OF THE INVENTION

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

[0022] <Bank transfer system> With reference to FIG. 1, a transfer agent system 1 according to an embodiment will be described. The transfer agent system 1 is configured to transfer the amount of a payment made by a payer to a bank account of a recipient. In this embodiment, the payer is a buyer and the recipient is a seller. The transfer agent system 1 realizes payments related to invoices (SaaS payments) within an invoice management service provided by a SaaS provider. Note that the payer and recipient are not limited to a buyer and a seller; for example, the payer may be a salary payer or employer, and the recipient may be a worker or employee.

[0023] As shown in Figure 1, the transfer agency system 1 comprises a terminal 10, a transfer agency server 20, a SaaS provider server 30, a sending bank system 40, a relay bank system 50, and a receiving bank system 60.

[0024] The terminal 10 is a terminal of a buyer (hereinafter also referred to as "user"), and may be, for example, a personal computer, a smartphone, a tablet terminal, etc. The user operates the terminal 10 to log in to a software platform provided by the SaaS provider, and view and approve the invoice (confirm the invoice contents), etc.

[0025] The transfer agent server 20 is a server of the transfer agent. As will be described in more detail below, the transfer agent server 20 exchanges information with the SaaS provider server 30, the sending bank system 40, the intermediary bank system 50, etc. in order to perform transfer agency processing. The transfer agent may be a bank. The transfer agent server 20 may also be a server outsourced by the transfer agent. The transfer agent server 20 may also be part of BaaS (Banking as a Service). The transfer agent server 20 may also be API-linked with the SaaS provider server 30, the sending bank system 40, JCN (Japan Card Network), etc.

[0026] The SaaS provider server 30 is a server of the SaaS provider. The SaaS provider server 30 is configured to provide an invoice platform related to the issuance and receipt of invoices.

[0027] The sending bank system 40 includes the accounting system (banking system) of the sending bank where the buyer's debit account is set up. In this embodiment, the sending bank is a bank designated by the buyer within the service provided by the SaaS provider.

[0028] Upon receiving a request for account transfer, etc., the sending bank system 40 performs a process (account transfer) to debit the invoice amount from the buyer's account (hereinafter also referred to as the "withdrawal account"). In this account transfer, the payment amount is transferred from the withdrawal account to the account of the sending bank's transfer agent or an account of a party entrusted by the transfer agent (hereinafter also referred to as the "sending bank agency account").

[0029] Furthermore, the sending bank system 40 performs the transfer process at a predetermined timing, such as after the account transfer or after the daily collection. In this transfer process, the payment amount transferred to the sending bank agency account is transferred to the account of the transfer agency at the intermediary bank or the account of the transfer agency's contractor (hereinafter also referred to as the "intermediary bank agency account").

[0030] The bank system of the sending bank system 40 may transfer the payment amounts relating to multiple invoices with the same payment date into the account of the intermediary bank in one lump sum, thereby reducing transfer fees.

[0031] The intermediary bank system 50 includes an accounting system of an intermediary bank in which an intermediary bank agency account is established. When the intermediary bank system 50 receives a transfer processing request from the transfer agent server 20, it performs a transfer process to transfer the buyer's payment amount from the intermediary bank agency account to the seller's account at the receiving bank. In this embodiment, the intermediary bank agency account is a single account shared by multiple buyers. However, this is not limiting, and an intermediary bank agency account may be established for each buyer.

[0032] The bank system of the intermediary bank system 50 may transfer the payment amounts for multiple invoices with the same payment date to the seller's account in one lump sum. This reduces transfer fees. The intermediary bank may also be the same bank as the sending bank or the receiving bank.

[0033] The receiving bank system 60 includes the accounting system of the receiving bank where the seller's account is established. The receiving bank may be the same bank as the sending bank or the intermediary bank.

[0034] <Device> The details of the terminal 10 used by the user will be described with reference to Figure 2. The user can use the services of the SaaS provider from the terminal 10, and can also select a debit account, approve an invoice, check the payment status (transfer status), etc.

[0035] The terminal 10 includes a processing unit 11, a communication unit 12, a storage unit 13, and a display unit 14.

[0036] The processing unit 11 has an information receiving unit 111 that receives information input by a user, and a display control unit 112 that controls the display unit 14 to display desired information.

[0037] The communication unit 12 is an interface for transmitting and receiving information via wireless or wired communication with the components (such as the SaaS provider server 30) of the transfer agent system 1. Note that there are no particular limitations on the method and standard of communication used by the communication unit 12.

[0038] The storage unit 13 is connected to the processing unit 11 and stores various information used by the processing unit 11 (such as programs executed by the processing unit 11 and data used by the processing unit 11). The storage unit 13 is configured from a semiconductor memory and / or a hard disk drive, etc.

[0039] The display unit 14 is configured, for example, by a liquid crystal display, an organic electroluminescence (EL) display, a CRT (Cathode Ray Tube) display, or the like. The display unit 14 displays various images and information, such as a GUI (Graphical User Interface) that accepts user operations. In this embodiment, the display unit 14 displays the GUI of the SaaS provider's invoice platform. The buyer operates the GUI displayed on the display unit 14 to specify the sending bank (debit account), approve the invoice (confirm the billing details, issue payment instructions), etc.

[0040] <Transfer agent server 20> The details of the transfer agent server 20 will be described with reference to FIG.

[0041] The transfer agent server 20 comprises a processing unit 21, a communication unit 22, and a storage unit 23.

[0042] The processing unit 21 includes an information acquisition unit 211, a registration unit 212, an account transfer request unit 213, a transfer request unit 214, and an information output unit 215. Details of each unit will be described later. In this embodiment, the processing unit 21 is configured by a processor, and by reading and executing programs from the storage unit 23, functions corresponding to each program are realized.

[0043] The functions of the processing unit 21 may be realized by the cooperation of multiple servers that can communicate with each other. For example, the account transfer request unit 213 may be provided on the server of the transfer agent, and the transfer request unit 214 may be provided on the server of a party outsourced by the transfer agent.

[0044] The communication unit 22 is an interface for transmitting and receiving information via wireless or wired communication between the components of the transfer agent system 1 (SaaS provider server 30, sending bank system 40, relay bank system 50, etc.). Note that there are no particular limitations on the method or standard of communication used by the communication unit 22.

[0045] The storage unit 23 is configured with a semiconductor memory and / or a hard disk drive, etc. In this embodiment, each function executed by the processing unit 21 is stored in the storage unit 23 in the form of a program that can be executed by a computer.

[0046] The memory unit 23 stores a customer management database 231, a debit account management database 232, and a payment instruction database 233.

[0047] The customer management database 231 is a database for managing user information. The user information includes the user's identification information (company name, name, identification number, etc.), address, contact information (telephone number, email address, etc.), type of business, and payment date (payment date set by the user, etc.).

[0048] The debit account management database 232 is a database that stores information about the customer's debit account. If the user information includes debit account information, the debit account management database 232 may be omitted.

[0049] The payment instruction database 233 is a database that stores payment instruction information related to the payment of invoices approved by the user. The payment instruction information includes the buyer's debit account and billing information. The billing information includes the billing amount (payment amount) and the transfer account. The billing information may also include the payment due date stated on the invoice.

[0050] Figure 4 shows an example of the payment instruction database 233. In this example, the payment instruction information consists of a header section and a details section. If there are multiple transfer details, the multiple details are linked to one header.

[0051] The header portion of the payment instruction information includes the instruction ID, user name, payment date, debit amount, direct debit status, debit account, transfer status, and number of transfer details. Here, "user name" stores the user's company name. Note that the user name may also be information that can identify the user (such as an identification number). "Payment date" stores the payment date (direct debit date) set by the user. "Debit amount" stores the amount to be debited from the user's account on the payment date (total amount if there are multiple details). "Direct debit status" stores information indicating whether the direct debit process has been completed at the sending bank (unprocessed or processed). "Debit account" stores information about the debit account.

[0052] The "transfer status" stores information (unprocessed or processed) indicating whether the amount associated with the instruction ID (debit amount) has been transferred to the seller's account. In the case of the case with instruction ID 002 in Figure 4, when the relay bank system 50 notifies the transfer agent server 20 that the debit amount of 1.2 million yen has been transferred to the seller's account at the receiving bank (Bank E, Branch e, 9000000), the transfer agent server 20 (registration unit 212) updates the transfer status from "unprocessed" to "processed." Note that in the case of the case with instruction ID 001, since there are multiple details, after all transfer processing for each detail has been executed, the registration unit 212 updates the transfer status in the header section from "unprocessed" to "processed."

[0053] The number of transfer details is stored in "Number of transfer details." For an item with instruction ID 001, there are two transfer details with detail IDs 001 and 002.

[0054] The details section of the payment instruction information includes detailed information for each detail, such as the instruction ID, detail ID, payment amount, transfer account, and transfer status. Here, the "instruction ID" is an ID used to link with the information in the header section, and the "detail ID" is the ID of the transfer detail. The "transfer account" stores information about the seller's account related to each invoice. The "transfer status" stores information (unprocessed or processed) indicating whether the amount related to the detail ID (payment amount) has been transferred to the transfer account.

[0055] Next, each unit of the processing unit 21 of the transfer agent server 20 will be described in detail.

[0056] The information acquisition unit 211 acquires various information from the components (such as the SaaS provider server 30) of the transfer agent system 1. For example, the information acquisition unit 211 acquires user information, debit account information, billing information related to invoices approved by the user, etc. from the SaaS provider server 30. Here, the debit account information includes the bank name, branch name, and account number.

[0057] Furthermore, the information acquisition unit 211 acquires the transfer status (unprocessed or processed) registered in the payment instruction database 233 in response to a request from the terminal 10. The acquired transfer status may be the transfer status in the header section, the transfer status in the statement section, or both. The information acquisition unit 211 then transmits the acquired transfer status to the SaaS provider server 30 via the communication unit 22. The display control unit 112 of the terminal 10 that has received the transfer status displays the transfer status on the display unit 14 of the terminal 10. Note that the information acquisition unit 211 may acquire the direct debit status and the transfer status, and if both have been processed, transmit a message that the transfer processing has been completed.

[0058] The registration unit 212 registers information in various databases in the storage unit 23 and updates the information stored in the databases. For example, the registration unit 212 registers the user information acquired by the information acquisition unit 211 in the customer management database 231. In addition, the registration unit 212 registers the debit account information acquired by the information acquisition unit 211 in the debit account management database 232.

[0059] The registration unit 212 registers the billing information acquired by the information acquisition unit 211 in the payment instruction database 233. In detail, when the registration unit 212 receives a payment instruction from the buyer requesting a transfer agency and the billing information related to the invoice, it registers the buyer's debit account and the payment instruction information including the billing information in the payment instruction database 233.

[0060] When the payment date or a date based on the payment date arrives, the account transfer request unit 213 requests the sending bank to transfer the payment amount (the amount claimed on the invoice) from the buyer's debit account at the sending bank to the sending bank's agent account at the sending bank. The determination of whether the payment date or a date based on the payment date has arrived is made, for example, by the account transfer request unit 213 referring to the payment date of the payment instruction information stored in the payment instruction database 233.

[0061] If the payment date of the payment instruction information falls on a weekend or public holiday, the account transfer request unit 213 may perform the above-mentioned account transfer process on the preceding or following weekday as the payment date. In this way, the account transfer request unit 213 is not limited to requesting an account transfer on the payment date of the payment instruction information, but may also request an account transfer on a day based on the payment date.

[0062] In the example shown in FIG. 4, when the payment date, January 31st, arrives, the account transfer request unit 213 requests the sending bank to transfer the debit amount (3 million yen) for instruction ID 001 from Company A's debit account (Bank A branch a, 1234567) to the sending bank agency account. The account transfer request unit 213 also requests the sending bank to transfer the debit amount (1.2 million yen) for instruction ID 002 from Company B's debit account (Bank B branch b, 7654321) to the sending bank agency account. The account transfer request is made, for example, via a settlement system such as JCN or CAFIS, and the account transfer is processed in real time. In this way, in this embodiment, the payment amount is immediately debited from the buyer's account when the account transfer is executed.

[0063] When the transfer agent server 20 receives a notification from the sending bank system 40 that the account transfer has been completed, the transfer request unit 214 requests the relay bank system 50 to transfer the payment amount (transfer agency) from the relay bank agency account to the seller's account. For example, in the case of an order with instruction ID 002 in FIG. 4, when the transfer request unit 214 receives a notification from the sending bank system 40 that the account transfer has been completed, it requests the relay bank system 50 to transfer the payment amount (1.2 million yen) from the relay bank agency account to the seller's account (Bank E Branch e 9000000). Note that the buyer's name and other identifying information, the invoice number, etc. may be entered in the summary field or the like so that the seller can determine which invoice the transfer is for.

[0064] In addition, when there are multiple transfer details, such as in the case with instruction ID 001, the transfer request unit 214 requests the relay bank system 50 to transfer 2 million yen from the relay bank agency account to the seller's account associated with detail ID 001 (Bank C, Branch C, 0000001), and also requests that it transfer 1 million yen from the relay bank agency account to the seller's account associated with detail ID 002 (Bank D, Branch d, 1000000).

[0065] The information output unit 215 outputs various information to components (such as the SaaS provider server 30) of the transfer agent system 1 via the communication unit 22. For example, the information output unit 215 outputs transfer status information read from the payment instruction database 233 to the SaaS provider server 30, etc.

[0066] <Transfer agency method> An example of the application process flow for a transfer agency service will be described with reference to the flowchart of FIG.

[0067] Step S1: The processing unit 21 (e.g., registration unit 212) of the transfer agent server 20 determines whether the transfer agent server 20 has acquired user information from the SaaS provider server 30. If user information has been acquired (S1: Yes), the process proceeds to step S2. For example, the user information is information (identification information, contact information, payment date, etc.) that the user has entered into the SaaS provider's invoice platform.

[0068] Step S2: The registration unit 212 of the transfer agent server 20 registers the user information acquired in step S1 in the customer management database 231.

[0069] Step S3: The processing unit 21 (e.g., the registration unit 212) of the transfer agent server 20 determines whether the transfer agent server 20 has acquired debit account information from the SaaS provider server 30. If debit account information has been acquired (S3: Yes), the process proceeds to step S4. For example, the debit account information is the account information of the sending bank selected by the user from among multiple banks within the invoice platform.

[0070] Step S4: The registration unit 212 of the transfer agent server 20 registers the debit account information acquired in step S3 in the debit account management database 232. If the debit account management database 232 is not provided, the registration unit 212 may register the debit account information in the customer management database 231.

[0071] After steps S1 to S4 above, the application process for transfer agency service is completed. Note that the above processing flow applies when an account registration function is provided within the software platform. If this function is not provided, for example, the transfer agency sends an account transfer request form to the user, and the user fills in the necessary information such as debit account information on the form and returns it. The transfer agency registers the debit account information entered on the transfer request form in the debit account management database 232.

[0072] Next, an example of payment processing according to the embodiment will be described with reference to the sequence diagram of FIG.

[0073] Step S11: The transfer agent server 20 receives a payment instruction (payment request) from the SaaS provider server 30. The payment instruction is sent to the transfer agent server 20 together with billing information when the user approves the invoice on the software platform. In this step, the information acquisition unit 211 of the transfer agent server 20 acquires the payment instruction and billing information.

[0074] Step S12: The registration unit 212 of the transfer agent server 20 registers the payment instruction information received in step S11 in the payment instruction database 233. In detail, the registration unit 212 registers the billing information (billing amount, transfer destination account) acquired in step S11 and the information stored in the customer management database 231 and the debit account management database 232 (user identification information, payment date, debit account information) in the payment instruction database 233. The latter information is acquired, for example, by searching the customer management database 231 and the debit account management database 232 using the user identification information included in the payment instruction as a key.

[0075] Step S13: The account transfer request unit 213 of the transfer agent server 20 determines whether the payment date related to the payment instruction received in step S11 has arrived. If the payment date has arrived (S13: Yes), proceed to step S14. If the payment date falls on a weekend or public holiday, the account transfer request unit 213 determines whether the weekday before the payment date has arrived.

[0076] Step S14: The account transfer request unit 213 of the transfer agent server 20 sends an account transfer request (a request for account transfer from the buyer's debit account to the sending bank agency account) to the sending bank system 40 via the communication unit 22.

[0077] Step S21: When the sending bank system 40 receives the account transfer request from the transfer agent server 20, it executes the account transfer from the buyer's account to the transfer agent's account. When the account transfer process is completed, the sending bank system 40 sends an account transfer completion notification to the transfer agent server 20.

[0078] Step S15: When the transfer agent server 20 (registration unit 212) receives notification of the completion of the account transfer from the sending bank's sending bank system 40, it updates the account transfer status in the payment instruction database 233 from "unprocessed" to "processed."

[0079] Step S16: The transfer request unit 214 of the transfer agent server 20 sends a transfer request to the relay bank system 50 via the communication unit 22. In detail, the transfer request unit 214 requests the relay bank system 50 to transfer the payment amount from the relay bank agency account to the seller's account.

[0080] Step S31: When the relay bank system 50 receives a transfer request from the transfer agent server 20, it executes the transfer process from the transfer agent's account to the seller's account at the receiving bank. When the transfer process is completed, the relay bank system 50 sends a transfer completion notification to the transfer agent server 20.

[0081] Step S17: When the transfer agent server 20 (registration unit 212) receives a transfer completion notification from the relay bank system 50, it updates the transfer status in the payment instruction database 233 from "unprocessed" to "processed".

[0082] Step S18: The transfer agent server 20 (information output unit 215) transmits a payment completion notice to the SaaS provider server 30.

[0083] Step S22: The sending bank system 40 executes the transfer process from the transfer agent's account to the transfer agent's account of the intermediary bank. The transfer process may be performed collectively for multiple invoices (or multiple users) at a predetermined transfer timing, such as after daily consolidation.

[0084] Note that the above method is merely an example, and various modifications are possible. For example, step S18 may be omitted. Alternatively, after receiving the payment completion notice in step S18, terminal 10 may display a message indicating that the transfer process has been completed.

[0085] As described above, according to this embodiment, users of the invoice platform can complete the transfer process within the invoice platform without having to go through the cumbersome procedures of downloading invoice data, logging in to the EB service, and uploading the invoice data, as in the past. In other words, after the seller uploads the invoice to the invoice platform, the buyer only needs to approve the invoice, and there is no need to log in to the sending bank's system to perform the transfer process. This significantly reduces the user's effort and workload.

[0086] Furthermore, according to this embodiment, the bank where the user's withdrawal account is located is not limited, and the user can make payments using the account of the bank of their choice. This makes it possible to provide a multi-bank B2B payment service. Furthermore, by having the bank act as a transfer agent, the bank can understand the relationship between the seller and the buyer, even in the case of card payments.

[0087] Furthermore, according to this embodiment, users can grasp the transfer status in real time on the invoice platform.

[0088] In the above embodiment, the software platform is an invoice platform, but this is not limited to this. For example, the software platform of the SaaS provider may be a payroll system. In this case, steps S11 and S12 related to payment instructions are unnecessary, and the payment date is the payday.

[0089] Based on the above description, a person skilled in the art may be able to conceive additional effects and various modifications of the present invention, but the aspects of the present invention are not limited to the above-described embodiments. Various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and spirit of the present invention, which is derived from the content defined in the claims and their equivalents.

[0090] At least a portion of the transfer agent system described in the above-described embodiment may be configured as hardware or software. If configured as software, a program that realizes at least a portion of the functions of the transfer agent system may be stored on a recording medium such as a flexible disk or CD-ROM, and may be read and executed by a computer. The recording medium is not limited to removable media such as magnetic disks or optical disks, but may also be fixed recording media such as hard disk drives or memory.

[0091] In addition, a program that realizes at least part of the functions of the transfer agent system may be distributed via communication lines (including wireless communication) such as the Internet. Furthermore, the program may be encrypted, modulated, or compressed and distributed via wired or wireless lines such as the Internet, or stored on a recording medium. [Explanation of symbols]

[0092] 1. Transfer agent system 10 devices 11 Processing section 111 Information Reception Department 112 Display control unit 12 Communications Department 13 Storage section 14 Display section 20 Transfer agent server 21 Processing section 211 Information Acquisition Department 212 Registration Department 213 Account Transfer Request Department 214 Transfer Request Department 215 Information Output Unit 22 Communications Department 23 Memory section 231 Customer Management Database 232 Withdrawal Account Management Database 233 Payment Instruction Database 30 SaaS provider servers 40 Sending Bank System 50 Intermediary Banking System 60 Receiving Banking System

Claims

1. an account transfer request unit that requests the sending bank to transfer the payment amount from the payer's account at the sending bank to an account of a transfer agent at the sending bank or an account of a party entrusted by the transfer agent at the sending bank when the payment date or a date based on the payment date arrives; a transfer request unit that, upon receiving a notification from the sending bank that the account transfer has been completed, requests the intermediary bank to transfer the payment amount from the account of the transfer agent or the account of a party entrusted by the transfer agent at the intermediary bank to the recipient's account at the receiving bank; A transfer agent system equipped with the above.

2. 2. The transfer agent system according to claim 1, wherein the payment amount is immediately debited from the payer's account upon execution of the account transfer.

3. 2. The transfer agent system of claim 1, further comprising a registration unit that, upon receiving a payment instruction and billing information requesting a transfer agent, registers the payment instruction information, including the payer's debit account and the billing information, in a payment instruction database.

4. 4. The transfer agent system according to claim 3, wherein said registration unit updates the transfer status in said payment instruction database from "unprocessed" to "processed" when said registration unit receives a notification of completion of said account transfer from said sending bank.

5. 4. The transfer agent system according to claim 3, wherein said registration unit updates the transfer status in said payment instruction database from "unprocessed" to "processed" when said registration unit receives a notification of completion of said transfer processing from said intermediary bank.

6. an information acquisition unit that acquires the transfer status registered in the payment instruction database in response to a request from the payer; The transfer agent system according to claim 5, further comprising a display control unit that displays the transfer status on the payer's terminal.

7. 2. The transfer agent system according to claim 1, wherein the sending bank is a bank designated by the payer.

8. 2. The transfer agency system according to claim 1, wherein the bank system of the sending bank performs a transfer process in which, after the account transfer, the payment amount transferred to the account of the transfer agency or the account of the transfer agency's contractor is transferred to the account of the transfer agency or the account of the transfer agency's contractor at the intermediary bank at a predetermined transfer timing.

9. 9. The transfer agent system according to claim 8, wherein the bank system of the sending bank transfers payment amounts relating to multiple invoices with the same payment date in one lump sum to the account of the intermediary bank.

10. a step in which, when a payment date or a day based on the payment date arrives, an account transfer request unit requests the sending bank to transfer the payment amount from the payer's account at the sending bank to an account of a transfer agent at the sending bank or an account of a party entrusted by the transfer agent; When the transfer request unit receives a notification from the sending bank that the account transfer has been completed, it requests the intermediary bank to transfer the payment amount from the account of the transfer agent or the account of a party entrusted by the transfer agent at the intermediary bank to the recipient's account at the receiving bank; A transfer agency method that includes the following.

11. A transfer agent program that causes a computer to execute the transfer agent method according to claim 10.

Images