JP6926178B2 - Forex Remittance System, Forex Remittance Method and Forex Remittance Program - Google Patents

Description

The present invention relates to a foreign exchange remittance system, a foreign exchange remittance method, and a foreign exchange remittance program to support remittances from overseas.

A technique for identifying a payer by an account number to be transferred is being studied (see, for example, Patent Document 1). In this technology, a table search is performed to check whether the transferred account number is a transfer-only account number. If the account number is for transfer only, add the transfer account number and related information to the specified location. Change the transfer account number to a legitimate account number. Normal ledger deposit processing is performed, and processing is performed for legitimate accounts. After that, the deposited company is notified of the transfer by electronic information in the return book and in the EB service. At this time, an account number dedicated to transfer for each payer and related information are given to a predetermined place and notified. In a company that has set up a transfer-only account, the payer can be identified by the account number used for this transfer.

In addition, when receiving a payment instruction addressed to a domestic customer from an overseas bank by remittance telegram, the remittance amount is deducted from the correspondent account of the remittance bank and deposited in the customer account. In such a remittance to be sent, a remittance message prepared using a format standardized by the International Organization for Standardization is received via the International Interbank Communication System (SWIFT: The Society for Worldwide Interbank Financial Tele-communication). (See, for example, Patent Document 2). In this technology, when the remittance server on the destination side receives the information necessary for overseas remittance from the customer, it generates a remittance message based on the necessary items. Then, based on the generated remittance message, it is transmitted to the remittance server on the recipient side via the SWIFT (registered trademark) network. The remittance server on the recipient side decodes the received remittance message and executes the payment process to the customer account on the recipient side of the remittance destination based on the remittance information included in the remittance message.

Japanese Unexamined Patent Publication No. 2000-082101 Japanese Unexamined Patent Publication No. 2016-12265

By using the related account associated with the specific account, the payer can be identified by using the account number. However, when using a related account, it takes time and effort to open a related account.

The foreign exchange remittance system that solves the above problems includes a remittance information storage unit that records remittance information in association with a lower code, and a control unit that acquires a remittance message. Then, the control unit specifies a number corresponding to the number of first digits of the account number from the account number column of the remittance message, identifies the account number and the recipient based on the specified number, and identifies the account. In the number field, the lower code of the second digit number continuously set in the account number is specified, the remittance person information is specified based on the lower code by using the remittance person information storage unit, and the remittance person is specified. A receipt confirmation request including the sender information is transmitted to the recipient system of the above, and the remittance message is deposited in the recipient's account according to the confirmation result of the receipt confirmation request.

According to the present invention, in foreign exchange remittance, the sender can be specified by using the account number of the remittance destination.

The system schematic diagram of 1st Embodiment. The explanatory view of the hardware configuration example of 1st Embodiment. It is explanatory drawing of the data used in 1st Embodiment, (a) is the billing information storage unit, (b) is the remittance person information storage unit, (c) is the explanatory diagram of the arrival information storage unit. The explanatory view of the processing procedure of 1st Embodiment. The explanatory view of the processing procedure of 1st Embodiment. The explanatory view of the processing procedure of 1st Embodiment. The explanatory view of the billing information storage part of the 2nd Embodiment. The explanatory view of the processing procedure of 2nd Embodiment.

(First Embodiment)
Hereinafter, with reference to FIGS. 1 to 6, one embodiment in which the foreign exchange remittance system, the foreign exchange remittance method, and the foreign exchange remittance program are embodied will be described. In this embodiment, it is assumed that a remittance request is received from an overseas financial institution and a service of depositing money into an account held by a domestic recipient is provided.

As shown in FIG. 1, in the foreign exchange remittance method of the present embodiment, a recipient system 10, a management server 20, a remittance person system 30, and an overseas bank system 40, which are interconnected via a network, are used.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of the information processing device H10 that functions as the recipient system 10 to the overseas bank system 40 and the like.

The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage unit H14, and a processor H15. Note that this hardware configuration is an example, and other hardware may be included.

The communication device H11 is an interface that establishes a communication path with another device and executes data transmission / reception, such as a network interface card or a wireless interface.

The input device H12 is a device that receives input from a user or the like, and is, for example, a mouse, a keyboard, or the like. The display device H13 is a display, a touch panel, or the like that displays various information.

The storage unit H14 is a storage device (for example, a billing information storage unit 12, an account information storage unit 22, and a sender, which will be described later) for storing data and various programs for executing various functions of the recipient system 10 and the overseas bank system 40. Information storage unit 23, arrival information storage unit 24). An example of the storage unit H14 is a ROM, a RAM, a hard disk, or the like.

The processor H15 uses the programs and data stored in the storage unit H14 to perform each process (for example, a process in the control unit 21 described later) in the information processing device H10 that functions as the recipient system 10 to the overseas bank system 40 and the like. Control. Examples of the processor H15 include a CPU, an MPU, and the like. The processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processes. For example, when the application program of the payee system 10 to the overseas bank system 40 is started, the processor H15 operates a process for executing each process described later.

The processor H15 is not limited to the one that performs software processing for all the processing executed by itself. For example, the processor H15 may include a dedicated hardware circuit (for example, an integrated circuit for a specific application: ASIC) that performs hardware processing for at least a part of the processing executed by the processor H15. That is, the processor H15 is (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that execute at least a part of various processes, or ( 3) It can be configured as a circuitry including a combination thereof. The processor includes a CPU and a memory such as a RAM and a ROM, and the memory stores a program code or a command configured to cause the CPU to execute a process. Memory or computer-readable medium includes any available medium accessible by a general purpose or dedicated computer.

(Functions of each information processing device)
The recipient system 10 shown in FIG. 1 is a computer system used by the recipient of remittance to make a claim to the sender. The recipient system 10 includes a control unit 11 and a billing information storage unit 12.
The control unit 11 manages the billing to the remittancer. The control unit 11 is connected to the remittance person system 30 via the Internet.

As shown in FIG. 3A, a billing management record 120 for managing billing to the sender is recorded in the billing information storage unit 12. This billing management record 120 is recorded when a bill to the sender is registered. In the billing management record 120, information regarding the invoice number, the business partner name, the billing amount, the billing content, the payment deadline, and the lower code is recorded.

In the invoice number data area, data regarding an identifier for identifying each invoice is recorded.
In the business partner name data area, data regarding an identifier for identifying the business partner name is recorded.

In the billing amount data area, data regarding the billing amount for this business partner is recorded.
Data related to the content of the request is recorded in the request content data area.
Data regarding the payment deadline (date) of this bill is recorded in the payment deadline data area.

In the lower code data area, data related to the lower code assigned to this business partner is recorded. In the present embodiment, the lower code is composed of a number having a second digit with respect to the account number having a first digit.

As shown in FIG. 1, the management server 20 is a computer system of a bank in which an account is opened. The management server 20 includes a control unit 21, an account information storage unit 22, a remittance person information storage unit 23, and an arrival information storage unit 24.

The control unit 21 functions as a communication management unit 211, a guidance management unit 212, a report creation unit 213, and an account management unit 214 by executing the foreign exchange remittance program.
The communication management unit 211 executes a process of receiving a remittance message via the SWIFT network.

The guidance management unit 212 executes an arrival guidance process for notifying the recipient system 10 of the arrival of the remittance telegram.
The report creation unit 213 executes a process of creating a report on the sender in response to the remittance message.
The account management unit 214 executes a process of managing an account opened in a bank.

The account information storage unit 22 records account management information for managing an account opened in a financial institution. In this account management information, an account identifier, an account holder, a balance, and a deposit / withdrawal history are recorded.

In the account identifier data area, data on identifiers (bank identifier, head office identifier, deposit type identifier, account number) for identifying an account opened in a financial institution is recorded.
In the account holder data area, data regarding identifiers and contacts for identifying the holder (payer or beneficiary) of this account is recorded.

Data regarding the balance of this account is recorded in the balance data area.
In the deposit / withdrawal history data area, history information of deposits to / from this account and withdrawals from this account is recorded.

As shown in FIG. 3B, the remittance person information storage unit 23 records the remittance person management record 230 for managing the remittance person. This remittance person management record 230 is recorded when a lower code is assigned to the remittance destination account number. The remittance person management record 230 records information about the remittance destination account number, the lower code, and the remittance person's name.

In the remittance destination account number data area, data regarding an identifier (bank code, head office code, deposit type, account number) for identifying an account managed by the bank is recorded.
In the lower code data area, data regarding an identifier for identifying the sender is recorded.
Data related to the name of the sender is recorded in the sender name data area.

As shown in FIG. 3C, the arrival information storage unit 24 records the arrival management record 240 for managing the remittance telegram acquired via the SWIFT network. This arrival management record 240 is recorded when a remittance message is received. The arrival management record 240 records information on the arrival date and time, bank transaction number, arrival currency, arrival amount, remittance requester name, remittance destination account number, customer identification number, check result, and remittance purpose.

In the arrival date / time data area, data relating to the date and time when the remittance message was received is recorded.
In the bank transaction number data area, data regarding an identifier for identifying this remittance message is recorded.

Data about the currency in which the remittance was made is recorded in the arrival currency data area.
In the arrival amount data area, data regarding the amount of money transferred is recorded.
In the remittance requester name data area, data relating to the name of the remittance requester included in the remittance telegram is recorded.

In the remittance destination account number data area, data regarding an identifier for identifying the remittance destination account is recorded.
In the account identification number data area, data regarding an identifier for identifying the account that holds the beneficiary account is recorded.
In the check result data area, the lower code extracted from the remittance message and the data related to the sender candidate specified based on the lower code are recorded.
Data regarding the purpose of this remittance is recorded in the remittance purpose data area.

The remittance person system 30 shown in FIG. 1 is a computer terminal owned by a customer who makes a remittance request. The remittance system 30 is connected to the recipient system 10 via a network such as the Internet.

The overseas bank system 40 is a computer system owned by an overseas financial institution for remittance. The overseas bank system 40 is connected to the management server 20 via the SWIFT network.

(Processing at the time of billing)
Next, the billing process will be described with reference to FIG.
First, the control unit 11 of the recipient system 10 executes the billing information registration process (step S1-1). Specifically, the recipient inputs billing information to the business partner in the recipient system 10. This billing information includes information on the business partner identification number, the business partner name, the billing amount, the billing content, and the like. In this case, the control unit 11 generates the billing management record 120 and records it in the billing information storage unit 12.

Next, the control unit 11 of the payee system 10 executes the process of designating the invoice deposit account (step S1-2). Specifically, the beneficiary acquires the lower code for specifying the billing address from the remittance person information storage unit 23 of the management server 20 and inputs it into the beneficiary system 10. In this case, the control unit 11 records the allocated lower code in the billing management record 120.

Next, the control unit 11 of the recipient system 10 executes the invoice creation process (step S1-3). Specifically, the control unit 11 creates invoice data based on the billing management record 120 recorded in the billing information storage unit 12. This invoice data includes information about the invoice amount and the remittance destination account. In this case, as the remittance destination account, a number with a lower code added to the recipient's account number is set. Then, the control unit 11 transmits the invoice data to the remittance person system 30 via the Internet. In this case, the remittance person requests the overseas bank system 40 to remit the amount of money according to the invoice amount to the remittance destination account included in the invoice data. If the remittance person can be notified of the remittance destination account, the billing amount, etc., the transmission of the invoice data is not limited to the case of using the Internet. For example, an invoice containing the remittance destination account, the invoice amount, and the like may be mailed.

(Processing at the time of remittance)
Next, the remittance processing will be described with reference to FIG. This process is performed when a remittance message is received from the overseas bank system 40 via the SWIFT network.

First, the control unit 21 of the management server 20 executes the remittance telegram acquisition process (step S2-1). Specifically, the communication management unit 211 of the control unit 21 receives the remittance message from the overseas bank system 40 via the SWIFT network. This remittance message includes fields related to BIC code, currency, remittance amount, remittance requester name, remittance destination account, and message to recipient. In the BIC code field, an identifier for identifying the remittance destination bank, country, and head office is recorded when using the SWIFT network. Any message, such as an invoice number, is recorded in the recipient message field. Then, the communication management unit 211 specifies the current date and time in the system timer and assigns a bank transaction number. Next, the communication management unit 211 generates an arrival management record 240 that records the arrival date and the bank transaction number, and records it in the arrival information storage unit 24. Further, the communication management unit 211 records the information recorded in each field of the currency, the remittance amount, and the remittance requester name included in the remittance message in each data area of the arrival management record 240 from the arrival currency to the remittance requester name.

Next, the control unit 21 of the management server 20 executes the remittance destination account number extraction process (step S2-2). Specifically, the guidance management unit 212 of the control unit 21 specifies a number having the first digit from the beginning in the remittance destination account field of the remittance telegram. This first digit number is, for example, the number of digits used in the head office number and account number of a domestic financial institution used for domestic remittance (here, 10 digits). When using the SWIFT network, the remittance destination bank is specified by the BIC code.

Next, the control unit 21 of the management server 20 executes the recipient identification process using the remittance destination account number (step S2-3). Specifically, the guidance management unit 212 of the control unit 21 identifies the recipient using the account information storage unit 22 based on the head office number and the account number specified in step S2-2.

Next, the control unit 21 of the management server 20 executes the arrival guidance process (step S2-4). Specifically, the guidance management unit 212 of the control unit 21 notifies the recipient system 10 of the specified recipient of the arrival guidance. The destination remittance arrival guide includes the information recorded in the arrival management record 240.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a lower code setting (step S2-5). Specifically, the report creation unit 213 of the control unit 21 confirms whether or not the code is set in the digit field following the first digit number in the remittance destination account field of the remittance telegram. If a code is set in the digit field following the first digit number, it is determined that there is a lower code setting.

When it is determined that the lower code is set (when "YES" in step S2-5), the control unit 21 of the management server 20 executes the lower code extraction process from the account number field (step S2-6). .. Specifically, the report creation unit 213 of the control unit 21 acquires a lower code of the second digit number set following the account number of the first digit number in the remittance destination account field.

Next, the control unit 21 of the management server 20 executes the search process of the remittance person by the lower code (step S2-7). Specifically, the report creation unit 213 of the control unit 21 searches the remittance person information storage unit 23 for the remittance person management record 230 in which the specified remittance destination account number and lower code are recorded.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not the remittance person can be identified (step S2-8). Specifically, when the report creation unit 213 of the control unit 21 can extract the remittance person management record 230 in which the lower code is set for the remittance destination account number from the remittance person information storage unit 23, the remittance is remitted. Judge that a person can be identified.

When it is determined that the remittance person can be identified (when "YES" in step S2-8), the control unit 21 of the management server 20 executes the remittance person candidate identification process which partially matches the lower code (step S2-). 9). Specifically, the report creation unit 213 of the control unit 21 acquires the remittance person name recorded in the remittance person management record 230 as a remittance person candidate by using the lower code of the second digit number. Then, the report creation unit 213 records the specified remittance candidate along with the lower code in the check result data area of the arrival management record 240.

On the other hand, when it is determined that the remittance person cannot be specified (when "NO" in step S2-8), the control unit 21 of the management server 20 performs the remittance person candidate identification process (step S2-9) which partially matches the lower code. ) Is skipped.

Next, the control unit 21 of the management server 20 executes the report creation process (step S2-10). Specifically, the report creation unit 213 of the control unit 21 creates a report including the information recorded in the arrival management record 240. This report includes information on arrival date, arrival currency, arrival amount, potential remittance requester name, beneficiary account, check results, etc.

Next, the control unit 21 of the management server 20 executes the receipt confirmation process (step S2-11). Specifically, the guidance management unit 212 of the control unit 21 transmits a receipt confirmation request including the created report to the recipient system 10. Even when it is determined that the lower code is not set (when "NO" in step S2-5), the receipt confirmation process is executed (step S2-11). In this case, the recipient confirms the remittance content by comparing the billing management record 120 recorded in the billing information storage unit 12 with the report, and clears the bill recorded in the billing information storage unit 12.

(Processing at the time of deposit)
Next, the deposit processing will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes the receipt confirmation completion process (step S3-1). Specifically, when the recipient who received the receipt confirmation request can confirm the remittance contents by the report, the receipt confirmation is input to the recipient system 10. In this case, set the purpose of remittance. Then, the guidance management unit 212 of the control unit 21 acquires the receipt confirmation data from the recipient system 10 and records the remittance purpose in the arrival management record 240.

When the receipt is confirmed, the control unit 21 of the management server 20 executes the payment process to the account (step S3-2). Specifically, the account management unit 214 of the control unit 21 deposits the arrival amount into the recipient account.

Next, the control unit 21 of the management server 20 executes the return processing of the payment result (step S3-3). Specifically, the account management unit 214 of the control unit 21 returns the payment result to the overseas bank system 40 via the SWIFT network.

According to this embodiment, the following effects can be obtained.
(1-1) In the present embodiment, the control unit 11 of the payee system 10 executes the process of designating the invoice deposit destination account (step S1-2). This allows the invoice to specify a destination account that includes a subcode for the sender.

(1-2) In the present embodiment, the control unit 21 of the management server 20 executes the recipient identification process using the remittance destination account number (step S2-3). When it is determined that the lower code is set (when "YES" in step S2-5), the control unit 21 of the management server 20 extracts the lower code from the account number field (step S2-6) and lower code. The remittance person search process (step S2-7) is executed. Thereby, the sender can be identified by using the account number of the remittance destination account included in the remittance message using the SWIFT network.

(1-3) In the present embodiment, when it is determined that the remittance person can be identified (when “YES” in step S2-8), the control unit 21 of the management server 20 partially matches the remittance person candidate with the lower code. (Step S2-9). As a result, even when information other than the lower code for identifying the sender is included, the sender can be identified by using a part of the account number field.

(1-4) In the present embodiment, when it is determined that the remittance person cannot be specified (when “NO” in step S2-8), the control unit 21 of the management server 20 partially matches the remittance person candidate with the lower code. (Step S2-9) is skipped. As a result, even a remittance telegram in which a lower code is not set can be handled in the same manner as a normal remittance telegram.

(1-5) In the present embodiment, the control unit 21 of the management server 20 executes a report creation process (step S2-10). This allows the recipient to identify the sender and clear the claim.

(Second Embodiment)
Next, the second embodiment will be described with reference to FIGS. 7 and 8. In the first embodiment, the billing information storage unit 12 is provided in the recipient system 10 to clear the bill. In the second embodiment, the management server 20 performs a process of clearing the bill. Therefore, the same parts as those in the first embodiment are designated by the same reference numerals, and detailed description thereof will be omitted.

In this case, as shown in FIG. 7, the management server 20 is provided with the billing information storage unit 25.
The billing information storage unit 25 records a billing management record 250 for managing billing to the sender. The billing management record 250 is recorded when billing information is acquired from the payee system 10. The billing management record 250 records information on the payee account number, the invoice number, the business partner name, the billing amount, the billing content, the payment deadline, the subcode, the total remittance amount, and the payment status.

In the beneficiary account number data area, data regarding an identifier for identifying the beneficiary account is recorded.
The same data as the billing management record 120 of the billing information storage unit 12 is recorded in the data area of the business partner identification number, the business partner name, the billing amount, the billing content, and the lower code.

The total remittance data area records data about the total remittance for this request.
In the payment status data area, data regarding a flag for identifying the payment status for this bill is recorded.

(Processing at the time of remittance)
Next, the remittance processing will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes the billing information acquisition process (step S4-1). Specifically, the report creation unit 213 of the control unit 21 acquires the billing information from the recipient system 10 and records it in the billing information storage unit 25. In this case, the payee code of the payee system 10 is recorded in the billing management record 250.

Next, the control unit 21 of the management server 20 executes the remittance telegram acquisition process in the same manner as in step S2-1 (step S4-2). Then, the control unit 21 of the management server 20 executes a remittance destination account number extraction process, a recipient identification process using the remittance destination account number, and an arrival guidance process (processes in steps S2-2 to S2-4). ..

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a lower code setting, as in step S2-5 (step S4-3).
When it is determined that the lower code is set (when "YES" in step S4-3), the control unit 21 of the management server 20 extracts the lower code from the account number field and searches for the remittance by the lower code. (Processing of steps S2-6 to S2-7) is executed.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not the remittance person can be identified (step S4-4), as in step S2-8.
Next, the control unit 21 of the management server 20 executes the remittance candidate identification process that partially matches the lower code, as in step S2-9 (step S4-5).

Next, the control unit 21 of the management server 20 executes a matching process with the billing information (step S4-6). Specifically, the report creation unit 213 of the control unit 21 extracts the billing management record 250 in which the specified remittance candidate is recorded as the business partner name and the payment deadline has not been reached. In this case, the report creation unit 213 compares the billing management record 250 with the remittance telegram. Here, the subcode, amount, client name, and invoice number are compared.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not the remittance amounts match (step S4-7). Specifically, the report creation unit 213 of the control unit 21 compares the remittance amount included in the remittance telegram with the billing amount recorded in the billing management record 250 and calculates the difference.

Here, when the remittance amounts do not match (when "NO" in step S4-7), the control unit 21 of the management server 20 executes the calculation process of the total remittance amount (step S4-8). Specifically, the report creation unit 213 of the control unit 21 extracts the arrival management record 240 in which the same recipient account and the remittance requester are recorded in the arrival information storage unit 24, and totals the remittance amount to obtain the total remittance amount. Calculate and update the total remittance amount of the arrival management record 240. Then, when the total amount of remittance exceeds the billed amount, the report creation unit 213 records the paid flag in the billing management record 250.
If the remittance amounts match (when "YES" in step S4-7), the calculation process of the total remittance amount (step S4-8) is skipped.

Next, the control unit 21 of the management server 20 executes the report creation process (step S4-9). Specifically, the report creation unit 213 of the control unit 21 determines the match / mismatch of the lower code, the difference between the billing amount and the remittance amount, the match / mismatch of the sender's name, and the match / mismatch of the invoice number of the arrival information storage unit 24. Record in the check result data area of the arrival management record 240. Then, the report creation unit 213 creates a report including the check result for the arrival remittance. Further, the report creation unit 213 acquires the total remittance amount associated with the lower code from the billing management record 250 and includes it in the report.
Next, the control unit 21 of the management server 20 executes the receipt confirmation process in the same manner as in steps S2-11 (step S4-10).

According to this embodiment, the following effects can be obtained.
(2-1) In the present embodiment, the control unit 21 of the management server 20 executes the billing information and the matching process (step S4-6). Thereby, the remittance status can be specified by using various information included in the remittance telegram. For example, it is possible to grasp the remittance amount in consideration of the remittance fee. Even if the billing party name and the sender's name are different, the sender can be identified by using other elements included in the remittance message.

(2-2) In the present embodiment, when the remittance amounts do not match (when “NO” in step S4-7), the control unit 21 of the management server 20 executes the calculation process of the total remittance amount (step S4-). 8). Specifically, the report creation unit 213 of the control unit 21 extracts the arrival management record 240 in which the same recipient account and the remittance requester are recorded in the arrival information storage unit 24, and calculates the total remittance amount by totaling the arrival amounts. calculate. In the case of a split remittance in which a part of the invoiced amount is remitted, the amount required for other remittances can be calculated.

This embodiment can be modified and implemented as follows. The present embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
-In the above embodiment, the remittance person information storage unit 23 records the remittance person management record 230 for managing the remittance person. A lower code of the second digit number is recorded in the remittance person management record 230. Here, the number of digits of the lower code may be changed according to the recipient. For example, in the case of a recipient with many business partners, the number of second digits is increased. In this case, the remittance person information storage unit 23 records the number of second digits in association with the remittance destination account number. Then, in step S2-6, the control unit 21 of the management server 20 extracts the lower code by using the second digit number associated with the remittance destination account number in the remittance person information storage unit 23.

-In the above embodiment, a lower code is set according to the sender. A lower code may be set for each remittance purpose. In this case, the remittance person information storage unit 23 records the remittance person's name and the lower code according to the remittance destination account number and the remittance purpose.
-In the above embodiment, the remittance message is received via the SWIFT network. The network used for receiving the remittance message is not limited to the SWIFT network. For example, a foreign exchange yen settlement system that sends remittance instructions between domestic financial institutions may be used.

-In the above embodiment, the remittance person information storage unit 23 is provided in the management server 20. The remittance person information storage unit 23 may be provided in the recipient system 10. In this case, the report creation unit 213 includes the lower code extracted from the remittance destination account field of the remittance telegram in the report and notifies the recipient system 10. Then, in the recipient system 10, the remittance person is specified based on the lower code.

10 ... Recipient system, 11 ... Control unit, 12 ... Billing information storage unit, 20 ... Management server, 21 ... Control unit, 211 ... Communication management department, 212 ... Guidance management department, 213 ... Report creation department, 214 ... Account management Department, 22 ... Account information storage department, 23 ... Sender information storage department, 24 ... Arrival information storage department, 30 ... Sender system, 40 ... Overseas banking system.

Claims (7)

The remittance person information storage unit that records the remittance person information in association with the lower code,
It is a foreign exchange destination remittance system equipped with a control unit that acquires remittance telegrams.
The control unit
From the account number column of the remittance telegram, a number corresponding to the number of first digits of the account number is extracted .
The extracted number is specified as the account number of the recipient's account opened at the financial institution and used for domestic remittance.
In the account number field, specify the lower code of the second digit number that is continuously set for the account number.
Using the remittance person information storage unit, the remittance person information is specified based on the lower code, and the remittance person information is specified.
A receipt confirmation request including the remittance person information is sent to the recipient system of the recipient.
A foreign exchange remittance system, characterized in that the remittance message is deposited in the recipient's account in response to the confirmation result of the receipt confirmation request. The foreign exchange destination remittance system according to claim 1, wherein the lower code is recorded in association with the recipient information in the remittance person information storage unit. The control unit
Obtain billing information including lower code from the recipient system,
The foreign exchange destined remittance system according to claim 1 or 2, wherein a matching result of matching the billing information with a lower code of the remittance message is included in the receipt confirmation request. The foreign exchange destined remittance system according to claim 3, wherein the control unit calculates the difference between the billing amount included in the billing information and the remittance amount of the remittance telegram and includes it in the receipt confirmation request. An arrival information storage unit that records arrival date and time, arrival amount, remittance requester name, check results including lower code, and arrival information regarding the purpose of remittance,
It also has a billing information storage unit that records billing information related to the payee account number, payment deadline, subcode, total remittance, and payment status.
The control unit
In the billing information storage unit, the billing information that is associated with the specified lower code and has not reached the payment deadline is specified.
In the arrival information storage unit, the same recipient account and the arrival information in which the lower code is recorded are extracted, the total amount of the remittance amount by the remittance message including the total amount of arrival amount is calculated, and the total amount of remittance amount of the arrival information is updated.
The foreign exchange destination remittance system according to any one of claims 1 to 3, wherein the receipt confirmation request includes the total amount. The remittance person information storage unit that records the remittance person information in association with the lower code,
It is a method to support foreign exchange remittance by using a foreign exchange remittance system equipped with a control unit that acquires a remittance message.
The control unit
From the account number column of the remittance telegram, a number corresponding to the number of first digits of the account number is extracted .
The extracted number is specified as the account number of the recipient's account opened at the financial institution and used for domestic remittance.
In the account number field, specify the lower code of the second digit number that is continuously set for the account number.
Using the remittance person information storage unit, the remittance person information is specified based on the lower code, and the remittance person information is specified.
A receipt confirmation request including the remittance person information is sent to the recipient system of the recipient.
A method of remittance to a foreign exchange destination, which comprises depositing the remittance telegram into the recipient's account according to the confirmation result of the receipt confirmation request. The remittance person information storage unit that records the remittance person information in association with the lower code,
It is a program that supports foreign exchange remittances by using a foreign exchange remittance system equipped with a control unit that acquires remittance telegrams.
The control unit
From the account number column of the remittance telegram, a number corresponding to the number of first digits of the account number is extracted .
The extracted number is specified as the account number of the recipient's account opened at the financial institution and used for domestic remittance.
In the account number field, specify the lower code of the second digit number that is continuously set for the account number.
Using the remittance person information storage unit, the remittance person information is specified based on the lower code, and the remittance person information is specified.
A receipt confirmation request including the remittance person information is sent to the recipient system of the recipient.
A foreign exchange remittance program, characterized in that the recipient's account functions as a means for depositing the remittance message according to the confirmation result of the receipt confirmation request.

Images