Information processing method, program, and information processing device

Abstract

To provide an information processing method and the like capable of realizing remittance between bank accounts at a low cost without increasing an operational burden on a remitter.SOLUTION: A computer acquires remittance information relating to remittance processing from a first account at a first financial institution held by a remitter to second accounts at three or more second financial institutions in one file for each designated remittance date, and outputs, to a server of the first financial institution, an instruction to execute processing of remitting a total remittance amount related to the remittance information in the acquired file from the first account at the first financial institution to a third account at the first financial institution held by a funds transfer service provider. The computer divides the remittance information in the file for each second financial institution that is a remittance destination, and, after the remittance processing from the first account at the first financial institution to the third account is completed, outputs, to a server of the second financial institution, an instruction to execute remittance processing from a fourth account at the second financial institution held by the funds transfer service provider to the second account at the second financial institution that is each of the remittance destinations, for each second financial institution that is the remittance destination.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to an information processing method, a program, and an information processing device. [Background technology]

[0002] Financial institutions provide a so-called transfer service, which transfers money from an account at a remitter's financial institution to an account at a recipient's financial institution. When the remitter's financial institution and the recipient's financial institution are different, the transaction is treated as an interbank transfer, which is carried out using a nationwide bank data communication system and therefore incurs high remittance fees. Therefore, Patent Document 1 discloses a system that uses a money transfer agent that has accounts at both the remitter's and recipient's financial institutions to transfer money from the remitter's account to the fund transfer agent's account and from the fund transfer agent's account to the recipient's account using interbank transfer, which incurs low remittance fees, thereby achieving low-cost remittance from the remitter's account to the recipient's account. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-135831 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the system disclosed in Patent Document 1, the remitter needs to input account information of the first account at the first bank held by the remitter, account information of the second account at the second bank held by the recipient, the remittance amount, etc., into a web page for the remittance service. Since the remitter needs to perform such input operations for each remittance transaction, the operational burden is large.

[0005] The present disclosure aims to provide an information processing method etc. that can realize remittance between bank accounts at low cost without increasing the operational burden on the remitter. [Means for solving the problem]

[0006] In an information processing method according to one embodiment of the present disclosure, a computer executes a process of acquiring remittance information relating to a remittance process from a first account of a first financial institution held by a remitter to three or more second accounts of a second financial institution in one file for each specified remittance date, and after acquiring the file, outputting to a server of the first financial institution an instruction to execute a process to remit the total remittance amount related to the remittance information in the file from the first account of the first financial institution to a third account of the first financial institution held by a money transfer service provider, dividing the remittance information in the file for each of the second financial institutions as remittance destinations, and after the remittance process of the total remittance amount from the first account of the first financial institution to the third account of the first financial institution is completed, outputting to a server of each of the second financial institutions as a remittance destination an instruction to execute a remittance process from a fourth account of the second financial institution held by the money transfer service provider to the second account of the second financial institution related to the divided remittance information. Effect of the Invention

[0007] In one aspect of the present disclosure, remittance between bank accounts can be achieved at low cost without increasing the operational burden on the remitter. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an example of the configuration of a remittance system. [Diagram 2] FIG. 2 is an explanatory diagram showing an example of the structure of a remittance request file. [Diagram 3] FIG. 2 is a block diagram showing a configuration example of a server and a remitter terminal. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of a record layout of a DB stored in a server. [Diagram 5] 13 is a flowchart showing an example of a procedure for requesting remittance processing; [Figure 6] 13 is a flowchart showing an example of a procedure for requesting remittance processing; [Figure 7]FIG. 13 is an explanatory diagram showing an example of a screen. [Figure 8] FIG. 13 is an explanatory diagram showing an example of a screen. [Figure 9] FIG. 13 is an explanatory diagram showing an example of a screen. [Figure 10] 1 is a flowchart showing an example of a remittance process procedure from a remitter's bank account to a fund transfer service provider's bank account. [Figure 11] 1 is a flowchart showing an example of a remittance process from a bank account of a funds transfer service provider to a bank account of a recipient. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an information processing method, a program, and an information processing device according to the present disclosure will be described in detail with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) In this embodiment, a remittance system is described which realizes remittance processing (including interbank remittance and same-bank remittance) between financial institutions (hereinafter referred to as banks) via accounts at each bank held by a funds transfer business operator. Figure 1 is an explanatory diagram showing an example of the configuration of a remittance system. The remittance system of this embodiment includes a server 10 managed by the funds transfer business operator, a bank server 50 managed by each bank, a remitter terminal 20 and an approver terminal 30 used by the remitter, and a recipient terminal 40 used by the recipient, and each of these devices is communicatively connected via a network N such as the Internet or a public communication line network.

[0011] The server 10 and the bank server 50 are information processing devices capable of various information processing and sending and receiving information, such as a server computer or a personal computer. The remitter terminal 20, the approver terminal 30, and the recipient terminal 40 are general-purpose information processing devices such as a personal computer, a smartphone, or a tablet terminal. The remitter terminal 20 is a terminal used by a remitter (a person in charge of remittance) who remits money using a remittance service provided by a money transfer service provider, and the approver terminal 30 is a terminal used by an approver (a person in charge of approval) who approves the execution of the remittance process requested by the remitter. The remitter and the recipient may be individuals or corporations. There may be multiple money transfer service providers, and each of them manages its own server 10, but for the sake of simplicity of explanation, the following description will be limited to one money transfer service provider.

[0012] In the remittance system of this embodiment, the server 10 accepts a request to execute a remittance process from the remitter terminal 20, and performs a process of requesting the bank server 50 of each bank to execute a same-bank remittance according to the content of the accepted request. For example, when a remittance request is received from an account of Bank A to an account of Bank B, the server 10 requests the bank server 50 of Bank A to remit from the remitter's account in Bank A to the account of the funds transfer service provider in Bank A, and requests the bank server 50 of Bank B to remit from the account of the funds transfer service provider in Bank B to the recipient's account in Bank B. In this way, the server 10 realizes the requested remittance process between different banks. In this embodiment, the server 10 accepts a request to execute a remittance process by receiving from the remitter terminal 20 a file containing remittance information (remittance request data) related to the remittance process.

[0013] FIG. 2 is an explanatory diagram showing an example of the configuration of a remittance request file. The remittance request file of this embodiment is, for example, a CSV (Comma Separated Values) file, and remittance request data for each remittance process is described in one record. In the example shown in FIG. 2, five remittance request data are associated with IDs 1, 2, 3, 4, and 5, and each includes the bank name of the remittance destination bank (the bank used by the remitter), the branch name, the deposit type, the account number, and the account holder, and the remittance amount (remittance amount) in one record. The remittance request file of this embodiment is prepared for each remittance designated date, and the remittance request file shown in FIG. 2 describes the remittance designated date in addition to the remittance request data. However, this configuration is not limited to this, and for example, the remittance request file may describe only the remittance request data, and the remittance designated date may be input via the remittance service site 12S and transmitted to the server 10. The remittance request file is not limited to a CSV file, and may be a file in the All Banks format (All Banks Association-specified format) used in the nationwide bank data communication system. The server 10 also functions as a web server, and provides a remittance service site 12S (see FIG. 3) via the network N for accepting use of the remittance service. A remitter accesses the server 10 using his / her own remitter terminal 20 and requests use of the remittance service via the remittance service site 12S, and the server 10 accepts the request for use of the remittance process via the remittance service site 12S. The remittance request file in this embodiment may be configured to include one or more remittance request data with one bank as the remittance destination, or may be configured to include multiple remittance request data with multiple banks as the remittance destination, or may be configured to include three or more remittance request data with three or more different banks as the remittance destination.

[0014] Fig. 3 is a block diagram showing an example of the configuration of the server 10 and the remitter terminal 20. The server 10 has a control unit 11, a memory unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, etc., and these units are connected via a bus. The control unit 11 is configured using one or more processors such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or a GPU (Graphics Processing Unit). The control unit 11 executes the program 12P stored in the memory unit 12 as appropriate, thereby carrying out the information processing and control processing that should be carried out by the server 10.

[0015] The storage unit 12 includes a RAM (Random Access Memory), a flash memory, a hard disk, an SSD (Solid State Drive), and the like. The storage unit 12 stores a program 12P (program product) executed by the control unit 11 and various data. The storage unit 12 also temporarily stores data and the like generated when the control unit 11 executes the program 12P. The storage unit 12 also stores a remittance service site 12S for accepting use of the remittance service via the network N. The storage unit 12 further stores a company account DB 12a and a member DB 12b. The storage unit 12 may be composed of multiple storage devices, and a part of the storage unit 12 may be another storage device connected to the server 10, or another storage device with which the server 10 can communicate.

[0016] The communication unit 13 is a communication module for performing processes related to wired or wireless communication, and transmits and receives information to and from other devices via the network N. The input unit 14 accepts operation input by a user, and sends a control signal corresponding to the operation content to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 11. The input unit 14 and the display unit 15 may be a touch panel configured as an integrated unit.

[0017] The reading unit 16 reads information stored in a portable storage medium 10a such as a CD (Compact Disc), a DVD (Digital Versatile Disc), a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, or a Compact Flash (registered trademark). The program 12P and various data stored in the storage unit 12 may be read by the control unit 11 from the portable storage medium 10a via the reading unit 16 and stored in the storage unit 12. The program 12P and various data may be written in the storage unit 12 during the manufacturing stage of the server 10, or may be downloaded by the control unit 11 from another device via the communication unit 13 and stored in the storage unit 12.

[0018] In this embodiment, the server 10 may be a multi-computer consisting of multiple computers, or may be a virtual machine virtually constructed by software in one device. When the server 10 is configured as a server computer, it may be a local server installed in the facility where the server 10 is installed, or may be a cloud server connected to the network N. In the following, the server 10 is described as being one computer. The program 12P may be arranged on a single computer or at one site, or may be distributed across multiple sites and distributed and executed on multiple computers connected to each other via the network N. Furthermore, the input unit 14 and the display unit 15 are not essential for the server 10, and the server 10 may be configured to accept operations through a connected computer, or to output information to be displayed to an external display device.

[0019] The remitter terminal 20 comprises a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, etc., and these units are connected via a bus. The control unit 21, storage unit 22, communication unit 23, input unit 24, and display unit 25 of the remitter terminal 20 each have the same configuration as the control unit 11, storage unit 12, communication unit 13, input unit 14, and display unit 15 of the server 10, so a detailed description of the configuration will be omitted. The storage unit 22 of the remitter terminal 20 stores, in addition to the program 22P (program product) executed by the control unit 21, a web browser 22AP (hereinafter referred to as browser 22AP) for browsing websites published via the network N.

[0020] FIG. 4 is an explanatory diagram showing an example of the record layout of DB12a, 12b stored in the server 10. FIG. 4A shows the company account DB12a, and FIG. 4B shows the member DB12b. The company account DB12a is a database that stores information on accounts held by the fund transfer service provider in each bank. The company account DB12a shown in FIG. 4A includes an ID column, a bank name column, a branch name column, a deposit type column, an account number column, an account name column, a balance column, etc., and stores information on accounts held by the fund transfer service provider in association with an ID assigned to each record. The information on the account includes the bank name, the branch name, the deposit type, the account number, the account name, and the balance. The balance column may store the result each time the server 10 periodically queries each bank server 50 for a balance, or may store the result of the balance each time the server 10 obtains the execution result of a deposit / withdrawal process for each account from each bank server 50. The contents stored in the company's account DB 12a are not limited to the example shown in FIG. 4A, and the deposit and withdrawal history of each account, information on the person in charge of managing each account, etc. may be stored.

[0021] The member DB 12b is a database that stores information on users (remitter requesting remittance processing, hereinafter referred to as remitter) who have registered as members to use the remittance service provided by the funds transfer service provider using the server 10. The member DB 12b shown in FIG. 4B includes a member ID column, a member information column, an account information column, an approver information column, a remittance designated date column, a file name column, a transfer status column, a remittance request data column, etc., and stores information on the remitter and information on the remittance processing requested by the remitter in association with identification information (member ID) uniquely assigned to each remitter. The member information column stores various information on the remitter (individuals and corporations). The member information includes, for example, a password used by the remitter for login processing when using the remittance service site 12S. The account information column stores information on the account held by the remitter (first account at the first financial institution). The account stored in the account information column is, for example, an account set to use the real-time account transfer service provided by each bank, and is preferably an account that allows account transfer (automatic withdrawal) by the funds transfer service provider. The approver information column stores information on the approver who approves the remittance process requested by the remitter (person in charge of remittance process), and stores, for example, the approver's contact information (e.g., email address). The remittance designation date column stores the execution date of the remittance process designated by the remitter. The file name column stores the file name of the remittance request file received by the server 10 from the remitter terminal 20. The remittance request file is stored, for example, in a specified area of ​​the storage unit 12, and the file name column stores information for reading out the remittance request file (e.g., folder name and file name indicating the storage location of the file). The transfer status column stores the execution status of the transfer process in which the total remittance amount (total remittance amount) in the remittance process requested in the remittance request file is credited from the remitter's account to the account of the funds transfer service provider of the same bank. For example, if the transfer process has not been executed, "unprocessed" is stored, and if the transfer process has been executed, "transferred" is stored. If the transfer process fails to be executed, "failed" may be stored. The remittance request data string stores information about the account held by the remittance recipient and the remittance amount.The contents stored in member DB12b are not limited to the example shown in FIG. 4B, and may store information regarding the remittance process, such as the execution status of each remittance process (e.g., waiting to be executed, executed, etc.), information regarding the remittance process, the date and time of receipt of the remittance process, information about the person in charge of receipt, etc.

[0022] The bank server 50 has a similar configuration to the funds transfer service provider's server 10, and therefore a detailed description of the configuration will be omitted. The memory unit of the bank server 50 stores a customer DB in which information on customers who have accounts at the bank that manages the bank server 50 is registered. The bank server 50 is also configured to perform various processes such as funds transfer between accounts at the bank (same-bank remittance) and balance inquiries for each account, in accordance with requests (requests) from the funds transfer service provider's server 10 and the remitter's terminal 20. Furthermore, the bank server 50 may be configured to perform processes related to interbank remittances using the nationwide bank data communication system, in accordance with requests (requests) from the funds transfer service provider's server 10 and the remitter's terminal 20.

[0023] The approver terminal 30 and the recipient terminal 40 have the same configuration as the remitter terminal 20, so a detailed description of their configurations will be omitted. When the server 10 receives a request to execute a remittance process from the remitter terminal 20, it requests the approver (the approver terminal 30) to approve the requested remittance process. At this time, the server 10 may be configured to make the approval request by e-mail, in which case a mailer for sending and receiving e-mails is installed in the server 10 and the approver terminal 30. The server 10 may also be configured to make the approval request via a specified application, in which case a specified application is installed in the approver terminal 30.

[0024] The following describes the process in which a remitter uses the remitter terminal 20 to request the server 10 to execute a remittance process in the remittance system of this embodiment. Figures 5 and 6 are a flowchart showing an example of the remittance process request procedure, and Figures 7 to 9 are explanatory diagrams showing example screens. In Figures 5 and 6, the process performed by the remitter terminal 20 is shown on the left, the process performed by the server 10 in the center, and the process performed by the approver terminal 30 on the right.

[0025] A user (remitter) who wishes to carry out a remittance process using the remittance system of this embodiment accesses the server 10 (remittance service site 12S) using the remitter terminal 20, and makes a request to execute the remittance process via the remittance service site 12S. When the control unit 21 of the remitter terminal 20 receives an instruction to access the remittance service site 12S from the remitter via the input unit 24, it starts the browser 22AP and accesses the remittance service site 12S (S11). Note that if an application program for accessing the remittance service site 12S is stored in the storage unit 22 of the remitter terminal 20, the remitter may access the remittance service site 12S by starting the application program in the remitter terminal 20.

[0026] The control unit 11 of the server 10 transmits a web page in response to the request from the remittance terminal 20, in this case the top screen (top page) of the remittance service site 12S, to the remittance terminal 20 (S12), and the control unit 21 of the remittance terminal 20 receives the top screen transmitted by the server 10 and displays it on the display unit 25 (S13). FIG. 7A shows an example of the top screen, which is a screen for accepting the selection of functions (services) available in the remittance service provided by the server 10. The top screen shown in FIG. 7A has a remittance request data creation button, a remittance request data upload button, requested remittance data button, unsuccessful remittance details button, deposit / withdrawal details button, and various setting buttons. The remittance request data creation button is a button for instructing the execution of a process to create (input) remittance request data via the remittance service site 12S, and the remittance request data upload button is a button for instructing the execution of a process to upload a remittance request file containing remittance request data to the server 10. The Requested Remittance Data button is a button for instructing the display of a list of remittance request data (requested remittance data) for remittance processing that has been requested and is waiting to be executed, and the Unabled Remittance Details button is a button for instructing the display of a list of remittance request data for which the remittance processing has failed. The Deposit / Withdrawal Details button is a button for instructing the display of a list of detailed information (history information) of deposit / withdrawal processing to the remitter's bank account generated by the remittance processing by the funds transfer agent, and the Various Settings button is a button for instructing the execution of setting processing of information that can be set for the remittance service provided by the server 10. The top screen may be configured to be transmitted from the server 10 to the remitter terminal 20 after the remitter logs in to the server 10 (remittance service site 12S) using his / her member ID and password.

[0027] In the flowcharts shown in Fig. 5 and Fig. 6, the processing performed by each device when the remittance request data upload button and the requested remittance data button are operated on the top screen shown in Fig. 7A will be described. When the remittance request data creation button is operated, a screen for inputting the designated remittance date and information on the recipient's bank account is sent from the server 10 to the remitter terminal 20, and the information inputted via the screen is sent from the remitter terminal 20 to the server 10 to request the execution of the remittance process. When the unsuccessful remittance details button is operated, a screen displaying a list of remittance request data for remittance processes that have failed to be executed (unsuccessful remittance processes) is sent from the server 10 to the remitter terminal 20 and displayed on the remitter terminal 20. The list screen of remittance request data for unsuccessful remittance processes is configured to accept corrections to the contents of each remittance request data (e.g., information on the recipient's bank account or remittance amount) and to accept an instruction to execute the remittance process based on the corrected remittance request data. When the Deposit / Withdrawal Details button is operated, a screen displaying a list of details (history information) of deposit / withdrawal transactions for the remitter's bank account registered in the member DB 12b is sent from the server 10 to the remitter terminal 20 and displayed on the remitter terminal 20. When the Various Settings button is operated, a setting screen accepting changes to information that can be changed for the remittance service provided by the server 10 is sent from the server 10 to the remitter terminal 20 and displayed on the remitter terminal 20.

[0028] The control unit 21 of the remittance terminal 20 judges whether or not the remittance request data upload button (shown as the upload button in FIG. 5) has been operated on the top screen (S14), and if it is judged that the button has been operated (S14: YES), it accepts the selection of a remittance request file in which remittance request data is described (S15). Here, the control unit 21 displays a remittance request acceptance screen, for example, as shown in FIG. 7B on the display unit 25, and accepts the selection of a remittance request file via the screen. The screen shown in FIG. 7B has an input field for inputting the remittance designated date, and a file selection button for instructing the execution of a remittance request file selection process. The input field for the remittance designated date may be configured to allow any numerical value to be input, or may have a pull-down menu that allows any one of a number of options to be selected. The input field for the remittance designated date may also be configured to display a calendar from which any date can be selected. When the file selection button is operated, the control unit 21 pops up a selection screen for remittance request files stored in the storage unit 22 or the like, and accepts the selection of any remittance request file via the selection screen. The remittance request file may be a file containing information such as that shown in Fig. 2. Note that, as shown in Fig. 2, when the remittance request file contains a specified remittance date, the control unit 21 may be configured to only accept the selection of a remittance request file via the remittance request reception screen.

[0029] When the OK button is operated on the remittance request reception screen, the control unit 21 transmits the remittance request information, including the remittance designated date and the remittance request file input via the screen, to the server 10 (S16). The control unit 11 of the server 10 receives the remittance request information transmitted by the remitter terminal 20 and stores it in the storage unit 12. The control unit 11 judges whether each of the remittance request data in the received remittance request file is appropriate (S17). For example, the control unit 11 judges whether a bank with the bank name and a branch with the branch name included in the remittance request data exist, whether an account number for the deposit type included in the remittance request data exists at the branch of the bank, whether the account number and the account name included in the remittance request data correspond appropriately, etc. The control unit 11, for example, uses the nationwide bank data communication system to inquire of the bank server 50 of the remittee bank about the above-mentioned information, and judges the appropriateness of the remittance request data.

[0030] The control unit 11 judges whether all remittance request data in the remittance request file is appropriate (S18), and if it judges that at least one remittance request data is inappropriate (S18: NO), it generates an error screen notifying that remittance processing cannot be performed for the remittance request data judged to be inappropriate, and sends it to the remitter terminal 20 (S19). The control unit 21 of the remittance terminal 20 receives the error screen sent by the server 10 and displays it on the display unit 25 (S20). The error screen displays, for example, the remittance request data judged to be inappropriate and the inappropriate parts of the remittance request data. When the error screen is displayed on the remittance terminal 20, the remitter corrects the remittance request data judged to be inappropriate in the remittance request file, and then uploads the remittance request file again.

[0031] When it is determined that all the remittance request data is appropriate (S18: YES), the control unit 11 transmits approval request information to the approver terminal 30 to request approval for the remittance process for which the execution request has been accepted (S21). Here, the control unit 11 reads out the approver information registered in the member DB 12b in association with the remitter who has sent the remittance request file, and transmits the approval request information to the approver terminal 30 based on the approver information. The control unit 11 transmits the approval request information to the approver terminal 30 by using, for example, email or a predetermined application. The control unit of the approver terminal 30 receives the approval request information transmitted by the server 10, and displays an approval request screen on the display unit based on the approval request information (S22). FIG. 8A shows an example of the approval request screen, and the approval request screen displays the remittance designated date and the contents of each remittance process for which the server 10 has accepted the execution request. The approval request screen has an "Approve" button and a "Do not approve" button, and the control unit of the approver terminal 30 accepts the approval or denial (do not approve) of the remittance process by accepting operation of either button (S23), and transmits approval information indicating the accepted approval or denial to the server 10 (S24). Note that, in addition to the configuration of Fig. 8A, the approval request screen may be configured to display information about the remitter's bank account (the account of the bank used by the remitter), and may have input fields for the approver's ID and password that are registered in advance in the server 10 (member DB 12b).

[0032] The control unit 11 of the server 10 receives the approval information sent by the approver terminal 30 and judges whether or not the remittance has been approved by the approver based on the received approval information (S25). If the control unit 11 judges that the remittance has not been approved (S25: NO), it generates an error screen notifying the user that the requested remittance process has not been approved by the approver and sends it to the remitter terminal 20 (S26). The control unit 21 of the remitter terminal 20 receives the error screen sent by the server 10 and displays it on the display unit 25 (S27). If the error screen is displayed on the remitter terminal 20, the remitter should appropriately correct the remittance request data in the remittance request file and then upload the remittance request file again.

[0033] When the control unit 11 determines that the remittance has been approved by the approver (S25: YES), it stores the remittance request data of the approved remittance process, for example, in the member DB 12b (S28). Specifically, the control unit 11 stores the remittance designated date, the file name of the remittance request file, and the remittance request data in the remittance request file in the member DB 12b in association with the member ID of the remitter. As a result, the remittance request data (remittance request file) of the remittance process requested by the remitter and approved by the approver is registered in the member DB 12b. At this time, the control unit 11 stores "unprocessed" as the transfer status of the remittance process in the member DB 12b. After that, the control unit 11 generates a screen notifying the remitter that the remittance process has been accepted and sends it to the remitter terminal 20 (S29). The control unit 21 of the remitter terminal 20 receives the acceptance completion screen sent by the server 10 and displays it on the display unit 25 (S30). FIG. 8B shows an example of a reception completion screen, which displays the designated remittance date, the number of cases, the total remittance amount (total remittance amount), the total fee amount (total fee amount), the transfer amount (total remittance amount and total fee amount), the scheduled transfer date, and the like for the remittance process that has been accepted by the server 10. In the example of FIG. 8B, the scheduled transfer date is the day before the designated remittance date, but is not limited to this. The control unit 21 of the remitter terminal 20 ends the process after displaying the reception completion screen. By the above-mentioned process, the server 10 accepts remittance requests (remittance request files) via the network N, so that there is no time limit for accepting remittance requests from remitter, and remittance requests can be accepted at any time (24 hours a day, 365 days a year). In addition, the server 10 transmits an approval request to the approver terminal 30 using e-mail or the like, so the approver can approve the received approval request at any time, and the burden on the approver is not increased.

[0034] When it is determined in step S14 that the remittance request data upload button has not been operated (S14: NO), the control unit 21 determines whether or not the requested remittance data button (referred to as the requested button in FIG. 6) has been operated on the top screen (S31). When it is determined that the requested remittance data button has not been operated (S31: NO), the control unit 11 ends the process. When it is determined that the requested remittance data button has been operated (S31: YES), the control unit 21 accepts the designated remittance date of the requested remittance data to be displayed (remittance request data of a remittance process waiting for execution because the designated remittance date has not passed) (S32). For example, the control unit 21 displays a designated remittance date selection screen as shown in FIG. 9A on the display unit 25 and accepts the selection of the designated remittance date via the screen. The control unit 21 can display the designated remittance date selection screen by acquiring the designated remittance date of the remittance process (remittance process waiting for execution) requested by the remitter from the server 10. Furthermore, the control unit 21 may be configured to display a calendar and accept any date via the calendar.

[0035] The control unit 21 accepts the selection of a remittance designated date on the remittance designated date selection screen, and when the "Go to details screen" button is operated, it requests the server 10 for requested remittance data (remittance request file) for the selected remittance designated date (S33). The control unit 11 of the server 10 generates a screen displaying a list of the requested requested remittance data (S34) and transmits it to the remitter terminal 20 (S35). The control unit 21 of the remitter terminal 20 receives the list screen of requested remittance data transmitted by the server 10 and displays it on the display unit 25 (S36). FIG. 9B shows an example of the list screen of requested remittance data, which displays a list of remittance request data being requested for the selected remittance designated date. In the example of FIG. 9B, a cancel button and a change button are provided in association with each remittance process for which remittance request data is displayed. The cancel button is a button for issuing an instruction to cancel the corresponding remittance process (cancel instruction), and the change button is a button for issuing an instruction to change the remittance amount in the corresponding remittance process (change instruction).

[0036] The control unit 21 judges whether any of the change buttons has been operated on the screen shown in FIG. 9B (S37), and when it judges that any of the change buttons has been operated (S37: YES), it accepts the change of the remittance amount for the remittance process corresponding to the operated change button (S38). For example, the control unit 21 pops up an input screen for the changed remittance amount and accepts the input of any remittance amount via the input screen. After accepting the input of the changed remittance amount, the control unit 21 requests the server 10 to change the remittance amount for the remittance process corresponding to the operated change button (S39). When a change of the remittance amount is requested, the control unit 11 of the server 10 and the control unit of the approver terminal 30 execute the same processes as steps S21 to S24 (S40 to S43). That is, the control unit 11 of the server 10 transmits approval request information to the approver terminal 30 for the remittance process in which the remittance amount has been changed (S40). The control unit of the approver terminal 30 displays an approval request screen based on the approval request information received from the server 10 (S41), accepts approval or denial of the change in the remittance amount (S42), and transmits approval information indicating the accepted approval or denial to the server 10 (S43).

[0037] The control unit 11 of the server 10 judges whether or not the remittance has been approved by the approver (S44), and if it judges that the remittance has not been approved (S44: NO), it performs the same process as in step S26 (S45), and the control unit 21 of the remitter terminal 20 performs the same process as in step S27 (S46). If the control unit 11 judges that the remittance has been approved (S44: YES), it changes the remittance amount of the approved remittance request data stored in the member DB 12b (S47). Thereafter, the control unit 11 of the server 10 and the control unit 21 of the remitter terminal 20 perform the same processes as in steps S29 to S30 (S48 to S49).

[0038] If it is determined in step S37 that the change button has not been operated (S37: NO), the control unit 21 determines whether any of the delete buttons have been operated (S50), and if it is determined that none of the delete buttons have been operated (S50: NO), the process ends. If it is determined that any of the delete buttons have been operated (S50: YES), the control unit 21 requests the server 10 to delete (cancel) the remittance process corresponding to the operated delete button (S51). If a request is made to delete a remittance process, the control unit 11 of the server 10 deletes the remittance request data of the remittance process requested to be deleted from the remittance request data stored in the member DB 12b (S52), and ends the process.

[0039] Next, a process for transferring (account transfer) the total amount of remittance in the remittance request data in the remittance request file from the remitter's bank account to the bank account of the funds transfer service provider based on the remittance request file uploaded to the server 10 by the above-mentioned process will be described. Figure 10 is a flow chart showing an example of the procedure for transferring money from the remitter's bank account to the bank account of the funds transfer service provider. Figure 10 shows the process performed by the bank server 50 of the bank used by the remitter on the left, the process performed by the server 10 in the center, and the process performed by the remitter terminal 20 on the right.

[0040] The server 10 is configured to perform a process of transferring (account transfer) the amount of the requested remittance process from the remitter's bank account to the account of the funds transfer service provider of the same bank on the day before the designated remittance date or on the designated transfer date designated by the remitter, etc. The server 10 also determines whether there is a remittance process for which the account transfer execution timing has arrived at a predetermined timing, such as once a day at a predetermined time. Therefore, the control unit 11 determines whether the predetermined timing (e.g., a predetermined time) has arrived (S61), and if it determines that the predetermined timing has not arrived (S61: NO), it waits while performing other processes until the timing arrives. If it determines that the predetermined timing has arrived (S61: YES), the control unit 11 reads out from the storage unit 12 the remittance request file for which the account transfer execution timing has arrived (the remittance request file to be account transferred) from which the account transfer execution timing has arrived (S62). Here, the control unit 11 refers to the designated remittance date of each remittance request file stored in the member DB 12b, and judges whether the timing for executing the account transfer (for example, the day before the designated remittance date) has arrived for each remittance request file based on the current date and time and the designated remittance date. When the remitter designates the transfer date, the designated transfer date is stored in the member DB 12b, so the control unit 11 can judge whether the timing for executing the account transfer (designated transfer date) has arrived by referring to the designated transfer date stored in the member DB 12b.

[0041] The control unit 11 of the server 10 executes the process from step S63 onwards for each of the remittance request files that have been read out. The control unit 11 calculates the sum of the remittance amounts (total remittance amount) in the remittance request data included in the remittance request files that have been read out (S63). The control unit 11 then transmits an instruction (remittance request) to the bank server 50 of the bank used by the sender (first financial institution, hereinafter referred to as the remittance bank) to execute a process to remit the calculated total remittance amount from the remittance account (first account of the first financial institution) to the account of the funds transfer service provider of the same bank (third account of the first financial institution) (S64). The remittance process here is preferably an instantaneous account transfer service provided by the remittance bank, but may be any other transfer process as long as it is a remittance process between the same banks (same-bank remittance process). When an instantaneous account transfer service is used, it is possible to instantly execute a remittance process from the remittance account to the account of the funds transfer service provider, and it is possible to instantly determine whether the remittance process (account transfer process) has been successful.

[0042] When the control unit of the remitter's bank server 50 receives an instruction to execute a remittance process from the server 10, it executes the remittance process as instructed (S65). For example, the control unit of the remitter's bank server 50 executes a process related to an instant account transfer service. As a result, the total amount to be remitted in the remittance request file is instantly remitted from the remitter's account at the remitter's bank to the account of the funds transfer service provider at the remitter's bank. The control unit of the remitter's bank server 50 transmits the result of the remittance process to the server 10 (S66). Here, if the remittance process is successful, information indicating the completion of the remittance process is transmitted to the server 10, and if the remittance process fails, information indicating the failure of the remittance process is transmitted to the server 10. The control unit of the bank server 50 notifies the server 10 of the success or failure of the remittance process, for example, by transmitting a withdrawal result message to the server 10.

[0043] The control unit 11 of the server 10 receives the remittance processing result sent by the remittance bank's bank server 50, and updates the transfer status corresponding to the remittance request file read in step S62 in the member DB 12b based on the received remittance processing result (S67). When the control unit 11 receives information indicating the completion of the remittance processing, it stores "Transferred" as the transfer status, and when it receives information indicating the failure of the remittance processing, it stores "Failed" as the transfer status. When it receives information indicating the failure of the remittance processing, the control unit 11 may leave the stored transfer status as "Unprocessed". The control unit 11 judges whether the remittance processing that it has instructed the remittance bank's bank server 50 to execute has been successful (S68), and when it judges that it has failed (S68: NO), it sends a transfer error screen to the remittance terminal 20 to notify that the account transfer from the remitter's account at the remittance bank has failed (S69). The control unit 21 of the remitter terminal 20 receives the transfer error screen sent by the server 10 and displays it on the display unit 25 (S70). When the transfer error screen is displayed on the remitter terminal 20, the remitter checks the balance of his / her account and deposits the shortfall amount.

[0044] When it is determined that the remittance process instructed to be executed by the bank server 50 of the remitter's bank is successful (S68: YES), the control unit 11 skips step S69 and ends the process. The control unit 11 may also send a screen to the remitter terminal 20 to notify that the account transfer from the remitter's account at the remitter's bank has been successful. Through the above-mentioned process, the server 10 can transfer the total remittance amount of the remittance process requested by the remitter from the remitter's account at the remitter's bank to the account of the funds transfer service provider at a specified timing, such as the day before the specified remittance date, for each uploaded remittance request file.

[0045] Next, for remittance processing in which the transfer process from the remitter's account at the remitter's bank to the remitter's bank account at the funds transfer service provider has been completed by the above-mentioned process, the process of remittance (interbank remittance) from the fund transfer service provider's account at the destination bank (the bank used by the recipient, hereafter referred to as the recipient's bank) to the recipient's account based on the remittance request data in the remittance request file will be described. Figure 11 is a flowchart showing an example of the remittance processing procedure from the bank account of the funds transfer service provider to the recipient's bank account. In Figure 11, the left side shows the process performed by the remitter terminal 20, the center shows the process performed by the server 10, and the right side shows the process performed by the bank server 50 of the bank used by the recipient.

[0046] The server 10 is configured to determine whether or not the designated remittance date has arrived (passed) for a remittance process being requested (a remittance process waiting to be executed) at a predetermined time, for example, once a day, and to perform a process of remittance (interbank remittance) from the account of the funds transfer service provider in the same bank as the recipient's bank to the recipient's account for the remittance process for which the designated remittance date has arrived. Therefore, the control unit 11 determines whether or not the timing for performing the remittance process (remittance timing) has arrived (S81), and if it determines that it has not arrived (S81: NO), it waits while performing other processes until it arrives. If it determines that the remittance timing has arrived (S81: YES), the control unit 11 reads from the storage unit 12 a remittance request file (remittance request file to be remitted) for which the transfer process from the remitter's account to the account of the funds transfer service provider has been completed and for which the designated remittance date has arrived (S82). Here, the control unit 11 refers to the remittance date and transfer status of each remittance request file stored in the member DB 12b, and identifies and reads out remittance request files for which the remittance date has arrived and the transfer process has been completed.

[0047] The control unit 11 of the server 10 executes the process from step S83 onwards for each of the remittance request files that have been read out. The control unit 11 divides the remittance request data contained in the remittance request file that has been read out for each recipient bank (remittance destination bank) (S83). When the remittance request file has the configuration shown in Fig. 2, the control unit 11 divides the remittance request data into four: one remittance request data for which the recipient bank is Bank A, one remittance request data for which the recipient bank is Bank B, two remittance request data for which the recipient bank is Bank C, and one remittance request data for which the recipient bank is Bank D. Note that, although one or two remittance request data are included for one bank in the example of Fig. 2, the configuration may also be such that three or more remittance request data are included for one bank.

[0048] The control unit 11 executes the process from step S84 onwards for the remittance request data for each recipient bank split from the remittance request file. Specifically, the control unit 11 identifies the recipient bank (remittee bank, second financial institution) for each split remittance request data (S84), and transmits to the bank server 50 of each recipient bank an instruction to execute a process (remittance request) to transfer the remittance amount indicated in the remittance request data from the fund transfer service provider's account (fourth account of the second financial institution) to the recipient's account (second account of the second financial institution) of the same bank (S85). The remittance process here is preferably an intrabank remittance service provided by each recipient bank, but may be another service as long as it is a remittance process between the same banks.

[0049] When the control unit of the bank server 50 of the recipient bank receives an instruction to execute the remittance process from the server 10, it executes the remittance process that has been instructed to execute (S86). For example, the control unit of the bank server 50 of the recipient bank executes processing related to the same-bank remittance service. As a result, the remittance amount indicated in the remittance request data is remitted from the account of the fund transfer agent of the recipient bank to the account of the recipient of the recipient bank. The control unit of the bank server 50 of the recipient bank transmits the result of the remittance process to the server 10 (S87). Here, if the remittance process is successful, information indicating the completion of the remittance process is transmitted to the server 10, and if the remittance process fails, information indicating the failure of the remittance process is transmitted to the server 10. Note that when the server 10 instructs the bank server 50 of the recipient bank to execute the remittance process, it can specify the remitter (original remitter) who has requested the fund transfer agent to execute the remittance process, rather than the fund transfer agent, as the remitter of the remittance process. Therefore, the bank server 50 of the recipient bank can handle the remittance process from the fund transfer service provider's account to the recipient's account as a remittance process from the original remitter to the recipient. This allows the recipient to know that a remittance process (deposit process) from the original remitter has been carried out when, for example, the recipient uses the recipient bank's balance inquiry service to check the amount of money deposited in his / her account.

[0050] The control unit 11 of the server 10 receives the remittance processing result sent by the bank server 50 of the recipient bank, and stores the execution status (remittance status) of the remittance processing based on each remittance request data divided from the remittance request file in step S83, for example, in the member DB 12b based on the received remittance processing result (S88). For example, the member DB 12b is provided with an execution status column corresponding to each remittance request data, and when the control unit 11 receives information indicating the completion of the remittance processing, it stores "remittance completed" as the remittance status, and when it receives information indicating the failure of the remittance processing, it stores "failure" as the remittance status. The control unit 11 judges whether the remittance processing that it has instructed the bank server 50 of the recipient bank to execute has been successful (S89), and when it judges that it has failed (S89: NO), it sends a remittance error screen to the remitter terminal 20 notifying that the remittance to the recipient's account at the recipient bank has failed (S90). The control unit 21 of the remitter terminal 20 receives the remittance error screen sent by the server 10 and displays it on the display unit 25 (S91). When the remitter terminal 20 displays the remittance error screen, the remitter checks whether the information on the recipient's bank account is correct.

[0051] When it is determined that the remittance process instructed to be executed by the bank server 50 of the recipient bank is successful (S89: YES), the control unit 11 skips step S90 and ends the process. The control unit 11 may send a screen to the remitter terminal 20 notifying that the remittance to the recipient's account in the recipient bank has been successful. Through the above-mentioned process, the server 10 can transfer the remittance amount indicated in the remittance request data from the account of the funds transfer service provider in the recipient bank to the recipient's account at the timing when the designated remittance date arrives for remittance request data for which the execution has been requested by uploading a remittance request file and for which the account transfer from the remitter's account to the account of the funds transfer service provider has been completed.

[0052] In the remittance system of this embodiment, remittance processing from a remitter's bank account to a recipient's bank account can be realized via the accounts of a fund transfer agent that has accounts in the remitter's bank and the recipient's bank. Specifically, remittance processing from the remitter to the recipient is performed by transferring the remittance amount from the remitter's account in the remitter's bank to the fund transfer agent's account, and transferring the same remittance amount from the fund transfer agent's account in the recipient's bank to the recipient's account. When performing interbank remittance, the nationwide bank data communication system is used, so the fee paid to the bank when performing interbank remittance is set higher than the fee paid to the bank when performing same-bank remittance. In this embodiment, interbank remittance, which requires a high fee, is realized by performing same-bank remittance between the bank used by the remitter and the bank used by the recipient, thereby reducing the fee (cost) paid to the bank, and as a result, the fee (cost) that the remitter needs to pay can be reduced. Furthermore, in this embodiment, the remitter can make a number of remittance processing requests (execution instructions) in one remittance request file, thereby reducing the burden on the remitter in processing remittance requests.

[0053] In this embodiment, the remittance process from the remitter's account to the account of the fund transfer service provider of the same bank is performed on a day different from the designated remittance date to the recipient's account (for example, the previous day or the designated transfer date), but is not limited to this. For example, the remittance process may be performed from the remitter's account to the account of the fund transfer service provider of the remitter's bank on the designated remittance date, and then the remittance process from the account of the fund transfer service provider of the recipient's bank to the recipient's account may be performed.

[0054] (Embodiment 2) The following describes a modified example of the remittance system of embodiment 1. Note that the remittance system of this embodiment can be realized using the same devices as those of the remittance system of embodiment 1 shown in Figures 1 and 3, so detailed explanation of the configuration will be omitted.

[0055] In the remittance system of the first embodiment, the server 10 may be configured to transfer (remit) a part or all of the deposited amount from the fund transfer agent's account in this bank (remitter's bank) to the fund transfer agent's account (designated account) in a bank (designated financial institution, hereinafter referred to as the designated bank) designated by the fund transfer agent when the remittance process from the remitter's account in the remitter's bank to the fund transfer agent's account in the same bank is completed. For example, in the process shown in FIG. 10, when it is determined in step S68 that the remittance process from the remitter's account in the remitter's bank to the fund transfer agent's account is successful (S68: YES), the control unit 11 of the server 10 may transmit an instruction (remittance request) to the bank server 50 of the remitter's bank to execute a process to transfer a part or all of the deposited amount from the fund transfer agent's account in the remitter's bank (the third account of the first financial institution) to the account of the designated bank of the fund transfer agent. In this way, when a deposit is made from the remitter's account to the fund transfer agent's account, the funds can be transferred to the fund transfer agent's account in the designated bank and pooled. With such a configuration, it is possible to prevent the balance of each bank's account with the money transfer service provider from increasing. Note that the server 10 may determine whether the balance of the remitter's bank's account with the money transfer service provider is equal to or greater than a predetermined amount, and if it is equal to or greater than the predetermined amount, send an instruction to the remitter's bank server 50 to execute a process to transfer all or part of the deposited amount, or any amount exceeding the predetermined amount, from the remitter's bank's account with the money transfer service provider to the designated bank's account. In this case, it is possible to control the balance of each bank's account with the money transfer service provider so that it does not exceed the predetermined amount.

[0056] In the remittance system of the first embodiment, the server 10 may be configured to determine whether the balance of the account of the fund transfer service provider of each bank falls below a predetermined amount, and when it is determined that the balance falls below the predetermined amount, to transfer (remit) funds from the account of the fund transfer service provider of the designated bank to the account of the fund transfer service provider of the bank whose balance falls below the predetermined amount. For example, the control unit 11 of the server 10 may determine whether the balance of the account of the fund transfer service provider of each bank falls below a predetermined amount periodically, or each time a deposit / withdrawal process is performed for the account of the fund transfer service provider of each bank. Then, when it is determined that the balance of any account falls below the predetermined amount, the control unit 11 may transmit an instruction to the bank server 50 of the designated bank of the fund transfer service provider to execute a process (remittance request) to remit a predetermined amount, or an amount to make the balance equal to or greater than the predetermined amount, from the account of the fund transfer service provider to the account of the fund transfer service provider of the bank whose balance falls below the predetermined amount. With such a configuration, it is possible to prevent the balance of the account of the fund transfer service provider of each bank from falling below the predetermined amount.

[0057] Furthermore, when a remittance process is performed from the remitter's account to the fund transfer service provider's account, the server 10 can be configured to transfer funds from the bank's fund transfer service provider's account to the designated bank's fund transfer service provider's account, and then transfer funds from the designated bank's fund transfer service provider's account to the fund transfer service provider's account of the bank with the lowest balance, depending on the balance of each bank's fund transfer service provider's account. With this configuration, funds remitted by the remitter can be temporarily pooled in the designated bank's fund transfer service provider's account, and then allocated to each bank's fund transfer service provider's account depending on the balance of each account. The designated bank can be, for example, the main bank (main transaction bank) of the fund transfer service provider.

[0058] In the remittance system of the first embodiment described above, the remittance request file uploaded to the server 10 includes remittance request data related to remittance processes having the same remittance designated date, but the present invention is not limited to this configuration. For example, the remittance request file may contain remittance request data related to remittance processes to be executed on each of a plurality of remittance designated dates. In this case, the control unit 11 of the server 10 may divide the remittance request data for each of the uploaded remittance request files for each of the remittance designated dates, and process the divided remittance request data for each of the remittance designated dates as the remittance request file of the first embodiment. For example, before step S17 or before step S28 in the process shown in FIG. 5, the control unit 11 of the server 10 may add a process of dividing the remittance request data in the remittance request file received from the remittance terminal 20 for each of the remittance designated dates. In such a configuration, the remittance request file does not need to be created for each of the remittance designated dates, and the remittance request file may be created in which the remittance request data is described for each of the remittance designated dates, improving operability.

[0059] Even with the above-mentioned configuration, the remittance system of this embodiment can execute the same processes as in embodiment 1, and can obtain the same effects. Furthermore, the modifications described in embodiment 1 above can be applied to this embodiment as well.

[0060] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims.

[0061] The matters described in each of the above-mentioned embodiments can be combined with each other. In addition, the independent claims and dependent claims described in the claims can be combined with each other in any and all combinations regardless of the citation format. Furthermore, the claims use a format in which a claim cites two or more other claims (multiple claim format), but this is not limited to this. A multiple claim (multi-multi claim) that cites at least one multiple claim may also be used. [Explanation of symbols]

[0062] 10 Server 11 Control section 12 Storage section 13. Communications Department 14 Input section 15 Display section 20 Remitter terminal 21 Control section 22 Memory section 23 Communications Department 30 Approver terminal 40 Recipient terminal 50 Bank Server

Claims

1. Acquire remittance information relating to a remittance process from a first account at a first financial institution held by a remitter to three or more second accounts at a second financial institution in one file for each remittance designated date; After acquiring the file, output an instruction to the server of the first financial institution to execute a process of transferring the total remittance amount related to the remittance information in the file from a first account of the first financial institution to a third account of the first financial institution held by the funds transfer service provider; Dividing the remittance information in the file into groups for each of the second financial institutions of the remittance destinations; After the remittance process of the total remittance amount from the first account of the first financial institution to the third account is completed, an instruction to execute a remittance process from a fourth account of the second financial institution held by the funds transfer service provider to a second account of the second financial institution related to the divided remittance information is output to a server of each of the second financial institutions of the remittance destinations. An information processing method in which processing is performed by a computer.

2. After acquiring the file, outputting request information to a terminal of an approver registered in correspondence with the remitter, requesting approval of the remittance process related to the remittance information in the file; When approval information approving the remittance process is obtained from the terminal of the approver, an instruction is output to the server of the first financial institution to execute a process of remittance of the total remittance amount related to the remittance information in the file from the first account of the first financial institution to the third account. The information processing method according to claim 1 , wherein the processing is executed by the computer.

3. outputting a screen displaying a list of remittance information in the file whose remittance designated date has not yet passed; accept, via the screen, a cancellation instruction or an instruction to change the remittance information for the remittance process related to the remittance information being displayed; When an instruction to change the remittance information is received, request information is output to a terminal of an approver registered in correspondence with the remitter of the file, requesting approval of the change process of the remittance information; When approval information approving the change process is obtained from the approver's terminal, the remittance information is changed according to the change instruction.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

4. The file is a CSV (Comma Separated Values) file in which remittance information for each remittance transaction is written in one record for each remittance transaction.

3. The information processing method according to claim 1 or 2.

5. After the remittance process of the total remittance amount from the first account of the first financial institution to the third account is completed, an instruction to execute a remittance process from the third account of the first financial institution to a designated account of a designated financial institution designated by the funds transfer service provider is output to a server of the first financial institution.

3. The information processing method according to claim 1, wherein the processing is executed by the computer.

6. determining whether or not the balances of the fourth accounts held by the money transfer service provider at the three or more second financial institutions are each less than a predetermined amount; If it is determined that the amount is less than the predetermined amount, an instruction to execute a remittance process from the designated account of the designated financial institution to the fourth account of the second financial institution that is determined to be less than the predetermined amount is output to the server of the designated financial institution. The information processing method according to claim 5 , wherein the processing is executed by the computer.

7. Acquire remittance information relating to a remittance process from a first account at a first financial institution held by a remitter to three or more second accounts at a second financial institution in one file for each remittance designated date; After acquiring the file, output an instruction to the server of the first financial institution to execute a process of transferring the total remittance amount related to the remittance information in the file from a first account of the first financial institution to a third account of the first financial institution held by the funds transfer service provider; Dividing the remittance information in the file into groups for each of the second financial institutions of the remittance destinations; After the remittance process of the total remittance amount from the first account of the first financial institution to the third account is completed, an instruction to execute a remittance process from a fourth account of the second financial institution held by the funds transfer service provider to a second account of the second financial institution related to the divided remittance information is output to a server of each of the second financial institutions of the remittance destinations. A program that causes a computer to carry out processing.

8. In an information processing device having a control unit, The control unit is Acquire remittance information relating to a remittance process from a first account at a first financial institution held by a remitter to three or more second accounts at a second financial institution in one file for each remittance designated date; After acquiring the file, output an instruction to the server of the first financial institution to execute a process of transferring the total remittance amount related to the remittance information in the file from a first account of the first financial institution to a third account of the first financial institution held by the funds transfer service provider; Dividing the remittance information in the file into groups for each of the second financial institutions of the remittance destinations; After the remittance process of the total remittance amount from the first account of the first financial institution to the third account is completed, an instruction to execute a remittance process from a fourth account of the second financial institution held by the funds transfer service provider to a second account of the second financial institution related to the divided remittance information is output to a server of each of the second financial institutions of the remittance destinations. Information processing device.

Images