JP7132377B2 - Remittance support system, remittance support method, and remittance support program - Google Patents

Description

The present invention relates to a remittance support system, a remittance support method, and a remittance support program for supporting remittance from overseas.

When receiving a payment instruction addressed to a domestic customer by a remittance message from an overseas bank, the remittance amount is withdrawn from the correspondent account of the remittance bank and deposited in the customer's account. In such an inward remittance, a remittance message created using a format standardized by the International Organization for Standardization is transmitted to the International Interbank Communication System (SWIFT (registered trademark): The Society for Worldwide Interbank Financial Tele-communication). (see, for example, Patent Document 1). In this technology, when the remittance server on the sending side receives information necessary for overseas remittance from a customer, it generates a remittance message based on the necessary items. Then, based on the generated remittance message, the remittance message is transmitted to the remittance server on the receiving side via the SWIFT network. The remittance server on the receiving side decodes the received remittance message and, based on the remittance information contained in the remittance message, executes the process of depositing money into the customer account on the receiving side of the remittee. When the remittance server on the receiving side completes the payment processing, the payment is processed to the data linkage server, which serves as a hub for data linkage between the systems of the financial institutions' bases in each country and region, via an internal network separate from the SWIFT network. Send completion notification. In response to this, the data linkage server transmits the received deposit processing completion notification to the remittance server, which is the sender, via the intrabank network.

JP 2016-122265 A

In the case of a company that has an account with a domestic financial institution, it is possible to transfer money from this account to a recipient in Japan. On the other hand, foreign companies that do not have domestic accounts need to use foreign exchange remittances when making payments to domestic recipients. In this case, the burden on foreign exchange remittance is large.

A remittance support system that solves the above problems includes a passage information storage unit that stores passage identifiers and customer identifiers in association with each other, a bank host system that communicates with overseas financial institution systems, and a control unit that is connected to a user terminal. Then, the control unit receives deposit data including a currency identifier from the overseas financial institution system, and associates the currency identifier included in the payment data with the currency identifier included in the payment data from the user terminal using the currency information storage unit. Specifying a customer identifier, for the bank host system that has received deposit data including the transaction identifier from the overseas financial institution system, in the transaction information storage unit, based on the purpose of remittance corresponding to the deposit data, From the remittance source account corresponding to the passage identifier, the customer identifier is set as the payer name, and a transfer instruction is issued to the recipient account included in the payment data.

According to the present invention, it is possible to support efficient and accurate remittance from foreigners who do not have accounts at domestic financial institutions to domestic residents.

1 is a schematic diagram of a system according to the present embodiment; FIG. Explanatory diagram of a hardware configuration example. FIG. 4 is an explanatory diagram of data used in the present embodiment, where (a) is a passage information storage unit, (b) is a payment information storage unit, and (c) is an explanatory diagram of a deposit information storage unit. Explanatory drawing of the processing procedure of this embodiment. Explanatory drawing of the processing procedure of this embodiment.

An embodiment embodying a remittance support system, a remittance support method, and a remittance support program will be described below with reference to FIGS. 1 to 5. FIG. In this embodiment, it is assumed that a service is provided in which a remittance request is received from an overseas financial institution and the money is deposited into an account held by a recipient in Japan.

As shown in FIG. 1, the remittance support method of this embodiment uses an overseas financial institution system 10, a user terminal 15, a management server 20, and a bank host system 30 which are interconnected via a network.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of the information processing device H10 functioning as the overseas financial institution system 10, the user terminal 15, the management server 20, the bank host system 30, and the like.

The information processing device H10 has 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, such as a mouse or a keyboard. 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 that stores data and various programs for executing various functions of the overseas financial institution system 10, the user terminal 15, the management server 20, and the bank host system 30 (for example, the passing information storage unit 22 described later). , payment information storage unit 23, account information storage unit 32, deposit information storage unit 33). Examples of the storage unit H14 include ROM, RAM, hard disk, and the like.

The processor H15 uses programs and data stored in the storage unit H14 to control each process in the information processing device H10 that functions as the management server 20, the bank host system 30, etc. (for example, the process in the control unit 21, which will be described later). do. Examples of the processor H15 include, for example, a CPU and an MPU. The processor H15 develops 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 programs of the overseas financial institution system 10, the user terminal 15, the management server 20, and the bank host system 30 are started, the processor H15 operates a process for executing each process described later.

The processor H15 is not limited to performing software processing for all the processing that it itself executes. For example, the processor H15 may include a dedicated hardware circuit (for example, an application specific integrated circuit: ASIC) that performs hardware processing for at least part of the processing performed by the processor H15. That is, the processor H15 is composed of (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that execute at least part of various processes, or ( and 3) any combination thereof. A processor includes a CPU and memory, such as RAM and ROM, which stores program code or instructions configured to cause the CPU to perform processes. Memory or computer-readable media includes any available media that can be accessed by a general purpose or special purpose computer.

(Functions of each information processing device)
A foreign financial institution system 10 shown in FIG. 1 is a computer system owned by a foreign financial institution for remittance. This overseas financial institution system 10 is connected to a bank host system 30 via a SWIFT network.

The user terminal 15 is a computer terminal owned by a customer who makes a remittance request. This user terminal 15 is connected to the management server 20 via a network such as the Internet.

The management server 20 is a computer system that supports a remittance service from an overseas remitter to a domestic recipient. This management server 20 includes a control section 21 , a passage information storage section 22 and a payment information storage section 23 .

The control unit 21 functions as a payment management unit 211 and a refund management unit 212 by executing the remittance support program.
The payment management unit 211 receives payment data from the user terminal 15 via the Internet, and executes processing for making a transfer.
The refund management unit 212 executes processing for managing refunds to the overseas financial institution system 10 .

As shown in FIG. 3A, the passage information storage unit 22 records a passage management record 220 for managing accounts that associate deposit data and payment data. This transit management record 220 is recorded when a transit account is set. Information relating to the transaction identifier, customer name, remittance purpose, and refund conditions is recorded in the transaction management record 220 .

In the pass identifier data area, data related to identifiers (bank identifier, head/branch identifier, deposit type identifier, account number) for identifying the account in which funds remitted from overseas payers are temporarily stored are recorded. . In this embodiment, a savings account in the name of the bank is used as the passing account.

In the customer name data area, data relating to the name (customer identifier) for specifying the overseas customer who uses this passing account is recorded.
Data relating to the purpose of remittance using this transit account is recorded in the remittance purpose data area. This remittance purpose records the remittance purpose that requires management in remittance from "overseas".

In the refund condition data area, data relating to conditions for refunding the money to the payer are recorded. The refund conditions include elements for determining whether refund is necessary. As this element, for example, the number of untransferable transactions, the untransferable amount, the timing of refund, the method of calculating the refund amount, and the like can be used.

As shown in FIG. 3B, the payment information storage unit 23 records a payment management record 230 regarding payment data received from the user terminal 15 via the Internet. A payment management record 230 is recorded when payment data is received. The payment management record 230 records data relating to the transaction identifier, recipient account, payment amount, contact information, and remittance result.

In the pass identifier data area, data relating to identifiers for comprehensively specifying remittances from overseas payers are recorded. In this embodiment, the account identifier of the transit account is used.
In the receiver's account data area, data relating to identifiers (bank identifier, head/branch identifier, deposit type identifier, account number) for specifying the receiver's account are recorded.

Data relating to the amount to be credited to the recipient's account is recorded in the payment amount data area.
In the contact data area, data relating to the contact (address) of the payer's user terminal 15 is recorded.

A remittance result data area records a flag for specifying the remittance result for this payment. When the remittance is completed, the date of completion is recorded, and when the remittance cannot be performed due to insufficient balance of the passing account, a balance shortage flag is recorded. Also, if the payee's account could not be identified, a non-transferable flag is recorded.

The bank host system 30 is a computer system of a domestic financial institution that manages accounts of customers (payers and payees) of the financial institution. This financial institution includes not only its own bank but also other banks. This bank host system 30 comprises a control section 31 , an account information storage section 32 and a deposit information storage section 33 .

The control unit 31 functions as an account management unit 311 and a deposit management unit 312 by executing an account processing program.
The account management unit 311 executes processing for managing accounts opened in banks.
The deposit management unit 312 executes processing for transmitting and receiving deposit data and the like from the overseas financial institution system 10 via the SWIFT network.

The account information storage unit 32 records account management information for managing accounts opened in financial institutions. Account identifiers, account holders, balances, and deposit/withdrawal histories are recorded in this account management information.

In the account identifier data area, data relating to identifiers (bank identifier, head/branch identifier, deposit type identifier, account number) for specifying an account opened in a financial institution are recorded. In this embodiment, the accounts opened at financial institutions include transit accounts.
In the account holder data area, data relating to an identifier for specifying the holder of the account (payer or payee) is recorded. In this embodiment, the passing account is in the name of the bank.
Data relating to the balance of this account is recorded in the balance data area.
In the deposit/withdrawal history data area, history information of deposits to and withdrawals from this account is recorded.

As shown in FIG. 3(c), the deposit information storage unit 33 records a deposit management record 330 relating to deposit data received from the overseas financial institution system 10 via the SWIFT network. The deposit management record 330 is recorded when deposit data is received. The deposit management record 330 records data relating to a remittance source account, a remittance destination account, a remittance amount, and a remittance purpose.

In the remittance source account data area, data relating to an identifier for specifying the remittance source account from the overseas financial institution system 10 is recorded.
In the remittance destination account data area, data relating to an identifier for specifying the remittance destination account from the overseas financial institution system 10 is recorded.
In the remittance amount data area, data relating to the amount remitted from the overseas payer is recorded.
Data relating to the purpose of this remittance is recorded in the remittance purpose data area.

(Payment management processing)
Next, payment management processing will be described using FIG. When using a transit account, the bank host system 30 opens a transit account in the name of the bank according to the payer and the purpose of the remittance. Then, the management server 20 generates a passage management record 220 that records the passage identifier, customer name, remittance purpose, and refund conditions, and records it in the passage information storage unit 22 .

First, the control unit 31 of the bank host system 30 executes the payment processing of the transfer price (step S1-1). Specifically, the deposit management unit 312 of the control unit 31 receives deposit data via the SWIFT network. This deposit data includes data on the remittance source account, the remittance destination account, the remittance amount, and the remittance purpose according to the SWIFT format. The deposit data may not include the purpose of remittance. Then, the deposit management unit 312 generates a deposit management record 330 in which information included in the deposit data is recorded, and records it in the deposit information storage unit 33 . Next, the account management unit 311 performs processing for depositing the remittance amount to the remittance destination account. When using this service, the money is deposited into the transit account as the destination account.

Further, the control unit 21 of the management server 20 executes a process of receiving payment data according to the purpose of remittance (step S1-2). Specifically, the payment management unit 211 of the control unit 21 receives payment data via the Internet. This payment data includes data relating to the transit identifier, payee account and payment amount. In the case of multiple payments (eg, thousands) with multiple payees, the payment amount is set for each payee account. Then, the payment management section 211 generates a payment management record 230 recording information included in the payment data, and records it in the payment information storage section 23 . At this stage, the remittance result data area of the payment management record 230 is left blank.

Next, the control unit 21 of the management server 20 repeats the following process for each payment.
Here, the control unit 21 of the management server 20 executes a passing account specifying process (step S1-3). Specifically, the payment management unit 211 of the control unit 21 uses the passage identifier included in the payment management record 230 to identify the passage account.

Next, the control unit 21 of the management server 20 executes balance check processing of the passing account (step S1-4). Specifically, the payment management unit 211 of the control unit 21 acquires the balance of the identified transit account from the bank host system 30 .

Next, the control unit 21 of the management server 20 executes determination processing as to whether or not the balance is sufficient (step S1-5). Specifically, the payment management unit 211 of the control unit 21 compares the balance of the passing account with the payment amount included in the payment management record 230 . If the balance is equal to or greater than the payment amount, it is determined that the balance is sufficient.

If it is determined that the balance is sufficient ("YES" in step S1-5), the control unit 21 of the management server 20 executes processing for creating a transfer message (step S1-6). Specifically, the payment management unit 211 of the control unit 21 acquires the customer name recorded in the passage management record 220 of the passage identifier from the passage information storage unit 22 . Then, the payment management unit 211 generates a transfer message for domestic remittance. In this transfer message, the account identifier of the passing account is set in the sending account column, the customer name is set in the transferor column, the receiver account identifier is set in the receiving account column, and the payment amount is set in the transfer amount column. The payment management unit 211 then transmits the created transfer message to the bank host system 30 . As a result, the bank host system 30 executes remittance processing.

Next, the control unit 21 of the management server 20 executes a transfer result recording process (step S1-7). Specifically, the payment management unit 211 of the control unit 21 acquires the transfer result from the bank host system 30 . This transfer result includes information for specifying whether the transfer to the recipient's account has been completed or not. When transfer completion information is included in the transfer result, the payment management unit 211 records the completion date in the transfer result data area of the payment management record 230 . On the other hand, if transfer impossibility information is included, the payment management unit 211 records a transfer impossibility flag in the remittance result data area of the payment management record 230 .

On the other hand, if it is determined that the balance is not sufficient because the balance is less than the remittance amount ("NO" in step S1-5), the control unit 21 of the management server 20 executes error processing (step S1-8). ). Specifically, the payment management section 211 of the control section 21 records a balance shortage flag in the remittance result data area of the payment management record 230 .
The control unit 21 of the management server 20 repeats the above processing for each payment.

Next, the control unit 21 of the management server 20 executes processing for returning the transfer result data (step S1-9). Specifically, the payment management unit 211 of the control unit 21 acquires the remittance result of the payment management record 230 in which the passage identifier is recorded from the payment information storage unit 23 . Then, the payment management unit 211 generates transfer result data in which the transfer result is recorded in association with the recipient's account identifier. If the payment data includes a plurality of payments to a plurality of recipients, the transfer result data is collectively generated. Then, the payment management unit 211 identifies the address of the payer's user terminal 15 and transmits the transfer result data. It should be noted that the reply of transfer result data is not limited to sending to the address of the payer. For example, transfer result data may be uploaded to a specific server so that it can be downloaded after the receiver's authentication process.

(Refund management processing)
Next, refund management processing will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes payment status identification processing (step S2-1). Specifically, the refund management section 212 of the control section 21 searches the payment information storage section 23 for a payment management record 230 in which no payment has been made. Here, in the payment information storage unit 23, the payment management record 230 in which the transfer impossibility flag is recorded is specified.

Next, the control unit 21 of the management server 20 executes refund necessity determination processing (step S2-2). Specifically, the refund management unit 212 of the control unit 21 acquires refund conditions from the passage information storage unit 22 . Then, the refund management unit 212 identifies elements for determining refund conditions, and acquires status information related to these elements. When the number of untransferable transactions is set as an element, the number of records in the payment management record 230 in which the unpayable flag is recorded is calculated. If the non-transferable amount is set as an element, the total amount of the payment amount in the payment management record 230 in which the non-payable flag is recorded is calculated. If the refund timing is set as an element, it is compared with the current date.

Next, the control unit 21 of the management server 20 executes determination processing as to whether or not refund is necessary (step S2-3). Specifically, the refund management unit 212 of the control unit 21 determines that refund is necessary when the status information satisfies the refund condition.

If it is determined that a refund is necessary ("YES" in step S2-3), the control unit 21 of the management server 20 executes refund processing for the untransferable balance (step S2-4). Specifically, the refund management unit 212 of the control unit 21 calculates the refund amount according to the refund conditions, and transmits a remittance instruction for the balance of the passing account to the bank host system 30 . In this case, the deposit management unit 312 of the control unit 31 transfers the money to the payer's account.

On the other hand, if the status information does not satisfy the refund conditions and it is determined that refund is unnecessary ("NO" in step S2-3), the control unit 21 of the management server 20 performs refund processing for the untransferable balance (step S2-4) is skipped, and the refund management process ends.

According to this embodiment, the following effects can be obtained.
(1) In the present embodiment, the passage information storage unit 22 records a passage management record 220 for managing accounts that associate deposit data and payment data. Information relating to the transaction identifier, customer name, remittance purpose, and refund conditions is recorded in this transaction management record. International payers can use this transit identifier to make payments to domestic payees. Therefore, the payer can save the trouble of holding an account at a domestic financial institution. Furthermore, since a transit account is set for each payer and remittance purpose, different payers and remittance purposes can be distinguished and managed accurately.

(2) In the present embodiment, the control unit 21 of the management server 20 executes a passing account specifying process (step S1-3). The control unit 21 of the management server 20 executes determination processing as to whether or not the balance is sufficient (step S1-5). If it is determined that the balance is sufficient ("YES" in step S1-5), the control unit 21 of the management server 20 executes processing for creating a transfer message (step S1-6). As a result, it is possible to remit funds received from one deposit data to a plurality of recipients using the payment data.

(3) In this embodiment, the payment management unit 211 generates a transfer message for domestic remittance. In this transfer message, the account identifier of the passing account is set in the sending account column, the customer name is set in the transferor column, the receiver account identifier is set in the receiving account column, and the payment amount is set in the transfer amount column. As a result, it is possible to make a transfer under the name of an overseas customer while using a transit account.

(4) In the present embodiment, the control unit 21 of the management server 20 executes transfer result data return processing (step S1-9). This allows the payer to grasp the payment status.

(5) In this embodiment, the control unit 21 of the management server 20 executes a refund necessity determination process (step S2-2). As a result, the refund can be made to the payer according to the refund conditions. For example, if a large account balance is maintained for payments, refunds may be made on a case-by-case basis. In addition, even if the transfer cannot be made due to the failure of the payee's account, the refund can be efficiently made to the payer according to the situation.

This embodiment can be implemented with the following modifications. This embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
- In the above embodiment, an identifier for specifying an account in which funds remitted from an overseas payer are temporarily stored is used as a transit identifier. The transit identifier is not limited to the account identifier of the transit account. For example, the remittance source account may be identified using an identifier that can identify each deposit for each remittance purpose.

- In the above embodiment, a savings account in the name of the bank is used as a passing account, but the name holder and deposit type are not limited to this.
- In the above embodiment, when it is determined that the transfer is impossible ("YES" in step S2-1), the control unit 21 of the management server 20 executes a refund necessity determination process (step S2-2). The refund method is not limited to this. For example, each time a transfer failure occurs, the payer may be asked whether a refund is necessary.

In the above-described embodiment, the passage management record 220 of the passage information storage unit 22 records information about the passage identifier, customer name, remittance purpose, and refund conditions. The information recorded in the passage information storage unit 22 is not limited to these. For example, the purpose of remittance and refund conditions may not be recorded in the passage information storage unit 22 . In this case, the control unit 21 of the management server 20 deposits money into the transit account regardless of the purpose of the remittance. Then, the control unit 21 of the management server 20 acquires the purpose of remittance from the recipient and performs remittance according to the purpose of remittance. As for the refund condition, the money may be refunded when requested by the remitter.
Also, the account balance of the passing account may be used as the refund condition. For example, if the account balance of the passing account is equal to or higher than the reference amount and is maintained for a predetermined period of time, the money may be refunded. In addition, the unpaid payment management record 230 in which the remittance result data area is blank or the balance shortage flag is recorded is specified, and the difference between the total amount of the unpaid payment amount and the account balance is equal to or greater than the reference amount is used as the refund condition. may

In the above-described embodiment, the control unit 21 of the management server 20 executes the process of checking the balance of the passing account (step S1-4) and the process of determining whether the balance is sufficient (step S1-5). Then, when it is determined that the balance is sufficient ("YES" in step S1-5), the control section 21 of the management server 20 executes processing for creating a transfer message (step S1-6). Alternatively, the control unit 21 of the management server 20 may execute the process of creating the transfer message (step S1-6) without performing the process of checking the balance of the passing account. Then, if the balance of the passing account is insufficient, the transfer impossibility information due to the insufficient balance is acquired from the bank host system 30. - 特許庁

DESCRIPTION OF SYMBOLS 10...Overseas financial institution system 15...User terminal 20...Management server 21...Control part 211...Overseas remittance part 212...Payment management part 22...Passing information storage part 23...Payment information storage part 30... Bank host system 31... Control unit 311... Account management unit 312... Payment management unit 32... Account information storage unit 33... Payment information storage unit.

Claims (6)

a passage information storage unit that associates and stores a passage identifier consisting of an account identifier of a remittance source account, which is a deposit account in the name of a financial institution, and a customer identifier;
A remittance support system comprising a bank host system that communicates with an overseas financial institution system, and a control unit connected to a payer's user terminal,
The control unit
receiving from the user terminal, payment data including information on the payment amount for each information for identifying a pass identifier of a deposit account that temporarily stores funds transferred from a payer and a plurality of payee accounts;
identifying a customer identifier associated with a passage identifier included in the payment data using the passage information storage unit;
Using the balance of the remittance account corresponding to the currency identifier to the bank host system that has received the currency deposit data including the currency identifier from the overseas financial institution system, based on the purpose of remittance corresponding to the currency deposit data A remittance support system for generating a plurality of remittance telegrams in which the customer identifier in the passing information storage unit is set as a payer name, and issuing a remittance instruction to each recipient account included in the payment data. The control unit
Comparing the balance of the remittance source account with the payment amount included in the payment data,
2. The remittance support system according to claim 1, wherein when the balance is insufficient for the payment amount, the customer's user terminal associated with the transaction identifier is contacted. a refund condition is recorded in the passage information storage unit in association with the passage identifier;
3. The remittance support system according to claim 1, wherein said control unit executes refund processing based on said refund condition according to a processing result of transfer processing according to said payment data. The refund conditions include information about the balance of the remittance source account,
4. The remittance support system according to claim 3, wherein the control unit specifies the balance of the remittance source account and executes refund processing according to the balance. a passage information storage unit that associates and stores a passage identifier consisting of an account identifier of a remittance source account, which is a deposit account in the name of a financial institution, and a customer identifier;
A method of supporting remittance using a remittance support system comprising a bank host system that communicates with an overseas financial institution system and a control unit connected to a payer's user terminal,
The control unit
receiving from the user terminal, payment data including information on the payment amount for each information for identifying a pass identifier of a deposit account that temporarily stores funds transferred from a payer and a plurality of payee accounts;
identifying a customer identifier associated with a passage identifier included in the payment data using the passage information storage unit;
Based on the purpose of remittance corresponding to the deposit data, the balance of the remittance source account corresponding to the currency identifier is used for the bank host system that has received the deposit data including the currency identifier from the overseas financial institution system. generating a plurality of transfer telegrams in which the customer identifier in the passing information storage unit is set as a payer name, and issuing a transfer instruction to each recipient account included in the payment data. a passage information storage unit that associates and stores a passage identifier consisting of an account identifier of a remittance source account, which is a deposit account in the name of a financial institution, and a customer identifier;
A program for supporting remittance using a remittance support system comprising a bank host system communicating with an overseas financial institution system and a control unit connected to a payer's user terminal,
the control unit,
receiving from the user terminal, payment data including information on the payment amount for each information for identifying a pass identifier of a deposit account that temporarily stores funds transferred from a payer and a plurality of payee accounts;
identifying a customer identifier associated with a passage identifier included in the payment data using the passage information storage unit;
Using the balance of the remittance account corresponding to the currency identifier to the bank host system that has received the currency deposit data including the currency identifier from the overseas financial institution system, based on the purpose of remittance corresponding to the currency deposit data A remittance characterized by generating a plurality of remittance messages in which the customer identifier in the passing information storage unit is set as the name of the payer, and functioning as means for instructing remittance to each recipient account included in the payment data. support program.

Images