JP5742054B2 - Received remittance receiving system and receiving method - Google Patents

Description

  The present invention relates to a destination remittance receiving system and a receiving method thereof, and more particularly, to a receiving system and a receiving method for receiving a destination remittance based on a request from a customer in a foreign exchange transaction business of a financial institution.

  Conventionally, various processing systems and processing methods have been proposed in order to save labor in foreign remittance (destination remittance) in foreign exchange operations of financial institutions such as settlement of goods and services performed based on requests from customers. For example, Patent Document 1 discloses a transaction in which the settlement amount is not affected by the foreign exchange rate on the transaction execution date among the destination remittance transactions scheduled to be executed on the next business day (the consideration category is “cont” or “ Forex trading apparatus that smoothes the processing load of the system by extracting “NoX” transactions) and performing these processes at night before the remittance execution date.

  Further, in Patent Document 2, in order to avoid inconveniences such as when a cancellation occurs between the conclusion of a contract between a user and a product / service provider and the execution of the contract, a predetermined number is set according to information input by the user. A remittance reservation record that includes transferring a predetermined amount (deposit money) to a predetermined remittance destination on the remittance date is stored in the database, and the predetermined amount is deducted from the withdrawable balance in the user's account balance record, A reservation remittance method is described in which a predetermined amount is transferred to a predetermined remittance destination account according to a remittance reservation record when a predetermined remittance date comes.

  Further, in Patent Document 3, in order to reduce the administrative burden of remittance to be sent, the forex processing server generates destination remittance data with reference to preset transfer conditions and account information of the balance of the transfer source account. The customer inputs the desired rate, sets the details of the exchange request, and when the foreign exchange rate reaches the desired rate, after the exchange contract is concluded, the foreign exchange processing server sends the destination message to the destination financial institution. A transaction processing system and the like are described.

JP 2002-297914 A WO2003 / 083743 Publication JP 2006-92447 A

  In recent years, as the number of overseas transactions increases, the load on the foreign exchange business system of financial institutions tends to increase more and more. The systems and methods described in the above Patent Documents 1 to 3 are all for the purpose of labor saving of the system on the destination remittance side (the remittance side) in the destination remittance abroad, but the destination remittance side ( It is not intended to save labor on the recipient system. However, as described below, the burden of office work is large on the destination remittance side, and it is desired to improve the efficiency of the system.

  FIG. 1 is a diagram showing an outline of a business flow in a conventional remittance receiving system. That is, the recipient first sends a remittance request (invoice, etc.) to the sender by e-mail or the like, and waits for the receipt after receiving a remittance schedule notification from the sender. The remittance sends a remittance request to the sender's bank, and the remittance bank (which may be a different bank than the transacting bank) sends a remittance message describing the remittance based on the remittance request ( It is also called a destination message (see 100 in FIG. 2 for a specific example), and this remittance message is transmitted to the receiving bank head office.

  When the receiving bank's head office (foreign exchange processing host computer) receives the remittance message, it analyzes the contents of the remittance amount information 101, the sender information 102, the recipient information 103, etc. in the remittance message, and receives the receiving bank. Input (mapping) the contents of the remittance message to the corresponding item on the system in order to put it on the internal system. After confirming the contents of each item, register (register) it in the database, confirm the recipient (recipient's account number and recipient's nomination), and then send the remittance message to the branch in the same bank where the customer's account is located. Notify the contents. Upon receiving this notification, the branch of the receiving bank informs the customer who is the recipient of the remittance, receives an instruction regarding payment from the recipient, and contacts the head office of the receiving bank. At the head office of the receiving bank, payment processing is performed only after receiving this instruction.

  As described above, the business at the receiving bank is complicated, and it takes time until the deposit process is executed unless the customer is contacted in a timely manner. In most cases, customers need to contact customers each time they send money. Actual foreign exchange transactions are often made at different times and amounts rather than regular and fixed-destination remittances. In addition, the customer may change the receiving method each time depending on the exchange rate, etc. Therefore, in view of the above-described problems, an object of the present invention is to provide a system that can reduce the processing load and the prompt processing on the receiving side of a remittance of a remittance in a foreign exchange processing operation of a financial institution.

  In order to solve the above problems, the destination remittance receiving system of the present invention provides the following solution.

  Receiving remittance receiving system in the foreign exchange business of a financial institution, wherein a forex processing host computer, a net banking reception computer, and a billing host computer are connected so that data communication is possible, the net banking reception computer is A deposit reservation receiving unit for receiving deposit reservation information corresponding to the destination transfer via the Internet from a customer terminal of the customer receiving the destination transfer, and the foreign exchange processing host computer receives the receipt from the net banking reception computer Receiving deposit reservation information and registering it as reservation data in the deposit reservation DB, a message receiving unit for receiving a remittance message from an overseas remittance system, and analyzing the received remittance message. , Reception record / verification unit that maps to remittance message data for each predetermined item The remittance message data is compared with the reservation data registered in the deposit reservation DB, and the remittance message data determined to match the reservation data by the message matching unit and the message matching unit for matching or mismatching are determined. And a deposit processing unit for transmitting a deposit request for depositing an included remittance amount to a payee account included in the reservation data to the account host computer.

  That is, the destination remittance receiving system (hereinafter referred to as the present system) of the present invention is composed of a plurality of computers, and the network banking acceptance computer receives money from the customer terminal of the customer receiving the destination remittance via the Internet. Receive deposit reservation information corresponding to the destination remittance. The foreign exchange processing host computer receives the deposit reservation information received by the computer for accepting net banking and registers it as reservation data in the deposit reservation DB. On the other hand, the foreign exchange processing host computer analyzes the remittance message received from the overseas remittance system and maps it to the remittance message data for each predetermined item. Then, the remittance message data is compared with the reservation data registered in the deposit reservation DB, and the match (not necessarily a complete match) or mismatch is determined, and the remittance message data determined to match the reservation data is included. A payment request for depositing the amount of money into the payee account included in the reservation data is transmitted to the account host computer that manages the customer's account.

  With this configuration, as in the conventional system described in FIG. 1, the receiving bank head office contacts the branch of the same bank where the customer's account is located, and the contacted branch further contacts the customer. In this case, it is possible to quickly perform the deposit process without the trouble of receiving an instruction from the customer and returning it to the head office.

Further, the present system may be configured to have the following features.
The foreign exchange processing host computer, when the remittance message arrives later than the payment specified date included in the reservation data, transmits a delay notification to the customer terminal according to the customer's specification. And

  With this configuration, the remittance notification is received from the sender, and the recipient has registered the reservation data. However, for some reason, the remittance message is delayed after the designated date of payment (remittance date) notified by the sender. When it arrives, a delay notice can be sent to the customer side for notification. The fact that the remittance was delayed is recorded by this notice and can be used as a reference for future transactions. Of course, the same applies when the remittance message has not arrived.

Further, the present system may be configured to have the following features.
Even if the remittance amount included in the remittance message data is smaller than the remittance amount included in the reservation data, the electronic message matching unit may receive the payment if the difference is within the allowable range designated by the customer. It is made to perform.

  With this configuration, even if the remittance amount is smaller than the notified remittance amount, if the difference is an allowable amount of about the fee, the contents of the remittance message will be used as it is. Since it is turned, it is possible to eliminate in advance the occurrence of unnecessary inquiries from customers.

Further, the present system may be configured to have the following features.
The deposit reservation information includes means for the customer to register the deposit reservation information item separately for a variable item that varies for each transaction and a non-variable item that does not vary for each transaction.

  With this configuration, it is possible to reduce the trouble of inputting the same data (non-variable items) every time a customer makes a payment reservation each time a customer receives a remittance notification.

Further, the present system may be configured to have the following features.
In a case where the customer requests a plurality of senders to receive a certain amount of money to one recipient account when charging for a specific product or service, the deposit reservation registration unit , Adding information (a flag or the like) that can associate the one reservation data with a plurality of remittance message data from the plurality of remittances and storing the information in the deposit reservation DB.

  By configuring in this way, for example, when selling a single product to multiple partners at the same time, and receiving the same payment from the multiple partners in the same currency in a fixed account of the recipient Requires only one reservation data to be created, greatly reducing the trouble of registering the reservation data for each of the plurality of remittance messages.

In the above case, it is desirable to further configure the following features.
The message matching unit determines that the remittance account included in the remittance message data and the reservation data is a virtual remittance account in a case where remittance message data from the plurality of remittances is associated with the one reservation data. In this case, a plurality of remittance message data having the same virtual remittance account is used as a comparison target of the reservation data, and a match or mismatch of remittance accounts is determined.

  With this configuration, when multiple remittances are sent for the same product price as described above, the sender account included in the remittance message is usually different, but the recipient is issued by the system. By telling all the senders the virtual sender's account number, and having the virtual sender's account number entered in the sender's message, the N-to-1 correspondence between the sender's message and the reservation data becomes easier. Processing can be reduced.

  In addition, the present invention is not only a system that is an “invention of things”, but also a plurality of computers (hardware) and computer programs (software) in financial institutions cooperate to execute the following steps. It can also be understood as a “method invention” that exhibits the same operational effects as the system of the above.

  A method of receiving remittance in a foreign exchange business system of a financial institution composed of a plurality of computers connected so as to be able to communicate data, wherein one of the plurality of computers receives the remittance Receiving the deposit reservation information for the destination transfer from the customer terminal of the customer, receiving the received deposit reservation information and registering it as reservation data in the deposit reservation DB; The step of receiving from the remittance system, the step of analyzing the received remittance message and mapping it to remittance message data for each predetermined item, and comparing the remittance message data and the reservation data registered in the deposit reservation DB And determining the match or mismatch, and the determination step matches the reservation data. Then the remittance included in the remittance telegram data determined, and a step of executing the processing for payment to the payee account included in the reservation data, it is characterized.

  ADVANTAGE OF THE INVENTION According to this invention, the system which reduces the quick payment process and office work load of the receiving side of the remittance for the destination in the foreign exchange processing business of a financial institution can be provided.

It is the figure which showed the outline of the business flow in the remittance-destination receiving system currently performed conventionally. It is the figure which showed the specific example of the original text of a remittance message. It is the figure which showed the outline of the business flow in the destination remittance receipt system of this invention. It is the figure which showed the system configuration | structure which is suitable embodiment of the destination remittance receiving system of this invention. It is the figure which showed an example of the deposit reservation information registration screen in suitable embodiment of this invention. It is the figure which showed an example (continuation) of the deposit reservation information registration screen in suitable embodiment of this invention. It is the figure which showed the main processing flow of the forex processing host computer 10 in suitable embodiment of this invention. It is the figure which showed the message matching process flow of the forex processing host computer 10 in suitable embodiment of this invention.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described in detail with reference to the accompanying drawings. Note that the same number is assigned to the same element throughout the description of the embodiment.

  FIG. 3 is a diagram showing an outline of a business flow in the destination remittance receiving system of the present invention. The recipient first sends a remittance request (invoice, etc.) to the sender by e-mail, etc. and receives a remittance schedule notification from the sender, the sender sends the remittance request to the sender's bank, the remittance side The bank generates a remittance message describing the details of remittance based on the remittance request and transmits the remittance message to the receiving bank head office in the same manner as in the conventional system. However, at the time of receiving the remittance schedule notice, the payee reserves that there is a remittance from overseas in the payment reservation DB provided in the payee's bank, so the remittance amount, the sender's account information, And information such as the recipient's account number. The details of this registration will be described later. Paying attention to the fact that the details of remittance are usually decided on the remittance side and the receiving side in the case of destination remittance, the remittance content is registered in the database as reservation data on the receiving side instead of the sending side. Is the feature of this system.

  On the other hand, apart from the deposit reservation, the receiving bank's head office (foreign exchange processing host computer) receives the remittance message from the overseas remittance bank, analyzes the contents of the remittance message, and corresponds to the items in the bank system. To map. Then, verify the contents (for example, check the existence of the account on the recipient's side, check the possibility of fraudulent transactions such as money laundering (fund laundering) for the purpose of remittance, book (register) it in a predetermined database, Search for whether the reservation data is registered in the deposit reservation DB If the reservation data that matches the transaction details of the remittance message in the deposit reservation DB (not necessarily completely matched by the customer's specification) is found, Payment is processed to the customer's payee account specified in the deposit reservation DB without contacting the branch or receiving customer, and of course, the customer will be notified that the payment has been completed. May be.

  By doing so, the receiving bank head office system contacts the branch where the customer's account is located, and the branch office that received the contact further contacts the customer, and receives instructions from the customer each time and returns to the head office. It is possible to perform the deposit process speedily without such trouble. In addition, as will be described later, the customer's designation that is not included in the original remittance message can be registered in the deposit reservation DB. The burden can be reduced.

  FIG. 4 is a diagram showing a system configuration which is a preferred embodiment of the destination remittance receiving system of the present invention. As shown in the figure, a destination remittance receiving system 1 (hereinafter simply referred to as the present system) of the present invention is a forex processing host computer 10, a billing host computer 20, and a net banking acceptance as processing computers constituting a bank system. A computer 30 is communicably connected to each other via an intra-bank network 40 (intranet).

  The foreign exchange processing host computer 10 is a core computer for processing foreign exchange transactions. As a part related to the present invention, the overseas remittance bank computer system 50 is connected with a global dedicated network 60 between financial institutions. If the remittance message is received and the remittance is appropriate, a request for deposit processing to the account of the recipient is made to the account host computer 20.

  The account host computer 20 includes an account transaction information DB, manages transactions in a customer's bank account, receives a request from the foreign exchange processing host computer 10, and executes each deposit / withdrawal transaction.

  The net banking reception computer 30 is a so-called net banking server, and performs authentication from the customer terminal 70 and reception processing (pre-processing) of various requests via the Internet 80. In particular, the embodiment of the present invention includes a deposit reservation accepting unit 31 that receives deposit reservation information (details will be described later) from a customer terminal 70 that is a customer terminal that receives a destination remittance.

  Here, the customer terminal 70 includes not only a terminal possessed by a customer, such as a PC (Personal Computer), a mobile phone or a smartphone, but also a terminal in a bank operated by a bank employee in response to a customer request. These host computers or servers constitute a typical bank online system, and the present invention provides a computer program for executing necessary functions and a database storing various information necessary for processing. Can be implemented by installing these on computers, so existing hardware can be used as is.

  The foreign exchange processing host computer 10 is a computer that is the core of the present invention, and includes an arrival guide information DB 17 and a deposit reservation DB 18 as databases, and as a function unit, a telegram receiving unit 11, a receipt / verification / verification unit 12, A message matching unit 13, a deposit processing unit 14, a deposit reservation registration unit 15, and a deposit reservation DB monitoring unit 16 are configured. Each of the functional units will be described in order below.

  The arrival guidance information DB 17 is a database for receiving and storing remittance messages from overseas bank systems. The deposit reservation DB 18 is a database for a customer who has received a remittance schedule notification from a sender to register the details of the remittance as reservation data in advance. Reservation data to be registered includes the sender's account number, remittance currency, remittance amount, payment designation date (remittance date), purpose of remittance, recipient account number, etc., as well as various conditions specified by the customer (described later) It is.

  The telegram receiving unit 11 plays a role of receiving a remittance telegram from the remittance bank computer system 50 via the dedicated network 60. The receipt / book entry / verification unit 12 plays the role of temporarily storing the received (received) remittance message, verifying the contents of the remittance message, and registering (recording) it in the arrival guide information DB 17 as arrival information. In addition, money laundering is checked here based on the purpose of remittance, information on the sender and recipient, etc.

  The message matching unit 13 compares the contents of the verified remittance message registered in the arrival guidance information DB 17 (hereinafter referred to as remittance message data) with the reservation data registered in the deposit reservation DB 18 and finds matching reservation data. Play a role to detect. At this time, both data do not need to be completely coincident, and may be different as long as a part of the data is within an allowable range as designated by the customer. For example, even if the remittance amount is minus as much as a fee, it is regarded as the message content data that is within the allowable range and matches the reservation data. In addition, the reservation data registered in the deposit reservation DB can be modified until the deposit is completed. For example, the receiver can flexibly respond to sudden requests from customers, such as wanting to change the recipient account at the deposit destination. can do. In this case, although there is a difference between the original remittance message and the reservation data, the reservation data is given priority.

  If there is matching reservation data as a result of the message matching, the deposit processing unit 14 communicates with the account host computer 20 and sends the remittance amount included in the remittance message data (if there is a difference from the reservation data, the remittance message data Plays a role in causing the customer's bank account to be credited (sends a transfer request to the account host computer 20 and receives completion).

  The payment reservation registration unit 15 verifies the customer's payment reservation information received by the network banking reception computer 30 from the customer terminal 70, stores it as reservation data in the payment reservation DB 18, and updates it according to the customer's request. It plays the role of deleting.

  The deposit reservation DB monitoring unit 16 periodically inspects the deposit reservation DB 18 (at least every business day), deletes unnecessary data that has been processed, or remits money for a predetermined period even after the specified payment date. For reservation data that does not receive a message, perform a process such as raising a warning to that effect. The customer who received the warning will perform a process such as prompting the sender, but if the remittance is not executed for a certain period after the warning, the system forcibly deletes the reservation data.

  The above-described functional configuration of the present system is merely an example, and it is needless to say that each computer (server) may be a single unit or a plurality of units. In each computer, one functional unit may be further divided, or a plurality of functional units may be configured as one functional unit. Each functional unit reads a computer program stored in a storage device such as a ROM (Read Only Memory) or a hard disk by a CPU (Central Processing Unit) built in the computer, and the computer program executed by the CPU is Reads and writes necessary data such as tables from a database (DB; Data Base) stored in a storage device or a storage area in memory, and in some cases, related hardware (for example, input / output devices, display devices, communication interfaces) This is realized by controlling the apparatus. In addition, the database (DB) in the embodiment of the present invention may be a commercial database, but it simply means a collection of tables and files, and the internal structure of the database itself does not matter.

  5 and 6 are diagrams showing an example of a deposit reservation information registration screen according to a preferred embodiment of the present invention. A deposit reservation information registration screen 200 (hereinafter referred to as screen 200) in FIG. 5 is used to access the net banking reception computer 30 and to log in in order for a customer to make a reservation for receiving a remittance using this system. It is a screen displayed on the customer terminal 70 after the operation is completed. The registration of this system is subject to having a deposit account in the same bank, but there are restrictions on the range that can be used according to the customer's past transaction performance (for example, updated deletion of reservation data, etc.) ) In some cases, registration may be rejected. This is because the use of this system requires a certain degree of customer confidence.

  On the screen 200, the customer is the sender's account number 201 (remittance account), remittance currency 202 (JPY, USD, EUR, etc.), remittance amount 203 (transaction amount), exchange rate designation 203a, payment designation date 204 (scheduled remittance date) ), Remittance purpose 205, payee account number 206 (reception account), delay notification designation 207, amount minus allowable designation 208, and the like. In particular, the exchange rate designation 203a does not execute the deposit reservation as it is when the exchange rate at the time of receiving a remittance message is equal to or less than the rate designated here, but a method of designation separately (for example, a foreign currency deposit without converting into Japanese yen) Indicates that the deposit will be made. After inputting the above items, the customer requests registration to the system by pressing the registration button 210. In order to cancel the input data, the cancel button 211 is pressed.

  Remittance purpose 205 is referenced for money laundering checks, whether it is trade or not trade (in the case of trade, a report needs to be submitted to the country depending on the amount). The delay notification designation 207 selects “Yes” when it is necessary to notify the customer by e-mail or the like when the payment is not actually performed on the designated payment date. If the delay notification designation 207 is designated as “none”, there will be no notification even if the payment designation date has passed, and even if a remittance message arrives after that, the deposit process will be performed normally. When the date of remittance allows a certain amount of delay with respect to the payment designated date, an allowable time (for example, a time difference arrival time) may be input. An amount minus allowable designation 208 selects whether or not a certain amount of minus (about a fee) is allowed in the amount to be sent. The allowable amount may be explicitly input. If “None” is selected for the amount minus allowable designation 208, it is necessary for the registered reservation data and the remittance message data remittance amount to completely match. Although not shown, the customer can register various designations in addition to the items exemplified here. For example, if a remittance message arrives before the payment specified date, whether or not to notify that, whether or not a plurality of remittance message data can be associated with the reservation data, and the like.

  When transactions are frequently made with the same remittance source, the previous input result may be displayed on the screen 200 except for items that change every time such as the payment designation date 204 when the next input screen is activated. Also, for example, in the case where the same product or service is received in Japanese yen in a single receipt and receipt account, as shown in the figure, the sender account number 201 and the designated payment date 204 are variable items, It may be defined as a non-variable item. For this reason, each item on the screen 200 is provided with a check box 209 that can specify a variable item and a non-variable item. Further, in such a case, in order to reduce the trouble of the customer registering each reservation data for each remittance schedule notification from a large number of senders, the sender account number 201 is set as a virtual sender account number, and payment is made. It is desirable that the designated date 204 can be designated as a certain period (for example, 2011/02/04 to 2011/02/28).

  Using this virtual sender account number, it is possible to correspond to a large number of remittance messages by registering reservation data once. Usually, a virtual account number is mainly used when a sender or receiver makes a transaction without notifying his / her account number to the other party. This is used as a group account number for treating a sender as a group when there are a large number of senders. Since this virtual sender account number is issued in a different format from the account number of a normal bank account, the system can be easily distinguished. In order to indicate that a plurality of remittance message data including the same virtual sender account number can be associated with the reservation data designating a certain virtual sender account number, the stored receipt reservation registering unit 15 stores necessary information ( The flag etc. based on customer designation) is stored in the deposit reservation DB 18.

  Note that the virtual sender account number is used only for electronic message matching, and is not used for withdrawal by linking the real account number to the virtual sender account number on the sender side. The virtual sender account number is provided by preparing a predetermined menu in the system and providing a means for the system to automatically issue a one-time number and present it to the customer. It goes without saying that the customer also tells the sender in advance the issued virtual sender account number.

  By doing in this way, payment reservation information can be registered in a lump when receiving payments from a plurality of partners in a transaction of a specific product or service. In this case, since a plurality of remittance messages correspond to one reservation data in the payment reservation DB 18, this reservation data is held in the payment reservation DB 18 at least during the designated payment designation period. . Further, each time a remittance message arrives, the information of each remittance may be held in the DB.

  The upper part of FIG. 6 is a deposit reservation information registration completion screen 300 that is displayed when the deposit reservation information registration is successfully completed, and displays a registration number (reservation number). The lower part of FIG. 6 is a deposit reservation registration information confirmation screen 400 (hereinafter referred to as a screen 400), which is a screen for confirming, changing, or deleting registered reservation data.

  On the screen 400, a list 401 of registered reservation data is displayed. By default, the displayed order is the order from the oldest registration date, but it is displayed in order from the date of the specified payment date, or from the largest number of transactions by the sender, in order from the largest number of transactions, It may be possible to display the items in descending order. When the customer selects a reservation data row to be operated from the reservation data list 401 and presses the update button 402, a screen similar to the screen 200 shown in FIG. 5 is displayed, and each item can be changed. . Of course, there are items that cannot be changed depending on the time of change and the content of the change. For example, the payment designation date cannot be changed to a past date, or an account number other than the customer name cannot be changed as a receiving account. When canceling reservation data, the corresponding line is selected and the delete button 403 is pressed. In addition, when a plurality of remittance messages correspond to one reservation data, it is desirable that that is included in the reservation data and displayed.

  FIG. 7 is a diagram showing a main processing flow of the foreign exchange processing host computer 10 in a preferred embodiment of the present invention. First, in step S10, the foreign exchange processing host computer 10 receives the remittance message and saves it in the arrival guidance information DB 17 as it is (text and receipt book).

  Next, reception verification is performed on the received electronic message (step S11). In the reception verification, the NG word is not included for the purpose of confirming the recipient's account number, the recipient's name, and the purpose of remittance, or it is used for fraudulent transactions such as money laundering from the sender account number information Whether there is a history is checked automatically or semi-automatically. Anything that cannot be determined by the system is notified to the operator of the system.

  When the reception verification is completed, unprocessed reservation data in the deposit reservation DB is read in step S12. Then, in step S13, it is searched whether there is reservation data that matches the booked remittance message data. Details of the message matching processing procedure are shown in FIG. As a result of the electronic mail matching process, if there is matching reservation data (step S14; Yes), the payment process is performed on the designated account of the recipient included in the reservation data. Specifically, the foreign exchange processing host computer 10 transmits a transfer request to the account host computer 20 so as to transfer the remittance amount specified by the remittance message data to the specified account.

  In step S15, when the deposit process is completed, the process proceeds to step S16, and it is checked whether or not the remittance date is delayed from the designated payment date designated by the reservation data. Here, even if the actual remittance date is after the payment designation date, if the delay is within the allowable range due to the customer designation, it is assumed that the message matching process in step S15 matches, and the payment itself is processed. If there is a delay (step S16; Yes), and if there is a delay notification in the reservation data (step S17; Yes), a message to that effect is issued to the customer specified in advance (step S18). When there is no delay (step S16; No), it returns to the message matching process of step S13 (actually, the process from step S24 of FIG. 8 is continued). The issuance of the delay notification is triggered by the arrival of the remittance message, based on the delay detected by the message matching unit 13, and the receipt reservation DB monitoring unit 16 periodically updates the receipt reservation DB 18. It may be based on a delay detected by inspection.

  Returning to step S14, if there is no matching reservation data as a result of the message matching (step S14; No), the process proceeds to step S19, and the search for unchecked reservation data is continued. When all the reservation data has been checked, the main process ends. For remittance message data that does not match even after checking all reservation data, the deposit process is performed in the same manner as before.

  FIG. 8 is a diagram showing a message matching processing flow of the forex processing host computer 10 in a preferred embodiment of the present invention. FIG. 8 shows the details of the message matching in the previous step S13.

  First, in step S20, the message matching unit 13 of the foreign exchange processing host computer 10 compares the remittance message data with the recipient account of the reservation data to check whether they match. If they match, the process proceeds to step S21. If they do not match, the process proceeds to step S28, where it is determined that the “reserved data does not match” and the process ends. In addition, it may be possible to change the payee account immediately after the remittance message is issued, so the previous payee account and the new payee account are both stored in the reservation receipt DB 18 and the payee accounts do not match. Even if it exists, it may be determined by replacing the new payee account in the reservation data with the old payee account.

  Next, in step S21, it is checked whether or not the sender account numbers match. If they match, the process proceeds to the next step S22, but if they do not match, the process also proceeds to step S28, where it is determined that the “reserved data does not match” and the process ends. As described above, the sender account number may be a virtual sender account number. However, in this case, it should be noted that a plurality of remittance messages correspond to one reservation data.

  Next, in step S22, the message matching unit 13 compares the reservation data payment designation date with the current message processing date, and if the processing date is before the payment designation date, it is the previous remittance specified by the reservation data. Then, the process proceeds to step S28, where it is determined that “reservation data does not match”, and the process is terminated. Therefore, the processing of the message is temporarily suspended and becomes a processing target again at a later date and a designated payment date. However, you may make it accept the remittance before a designated day by customer designation. In that case, the process of step S22 is omitted.

  When the payee and the remittance match the reservation data, the process proceeds to step S23, and the relationship between the designated payment date and the current processing date is checked. If the processing date is later than the designated payment date, a delay is set, but if the delay is within an allowable range due to a time difference due to the customer designation, the process proceeds to step S24. If the delay is not within the allowable range, it is determined in step S28 that the reservation data does not match, and the process returns to the main process. In this case, in the main process, the process is temporarily suspended, and if there is a delay notification designation, the customer is notified accordingly. If there is no delay notification designation, as already described, the process returns to step S24 of the message matching process.

  In step S24, it is checked whether or not there is an amount minus allowable designation by customer designation in the reservation data. If there is a minus amount allowance designation (step S24; Yes), even if the remittance amount does not match the reservation data, if it is within the tolerance range designated by the customer (step S25; Yes), the process proceeds to step S26. “Reserved data match” is determined. If there is no amount minus allowable designation (step S24; No), it is checked in step S27 whether or not the remittance amount completely matches the reservation data. If there is a complete match, “match determination” in step S26 is performed, and if there is no complete match, “mismatch determination” in step S28 is performed.

  In the above flowchart, comparison processing is performed in the order of payee account, sender account, payment designation date and processing date, delay and delay tolerance range, amount minus tolerance designation, but it is not limited to such a comparison order. Absent. For example, if the payment specified date is compared with the processing date in the first step S20, the reservation data before the payment specified date is initially deviated from the subject of the electronic statement check, so it seems that the time required for the subsequent check can be shortened. However, if the number of customer designations that allow payment processing before the designated date of payment increases, this check is also required. Therefore, it is desirable that the above processing order can be changed flexibly depending on the tendency of actual reservation data to match or not match so that an optimum comparison order can be performed.

  As described above, the conventional destination remittance system focused on the remittance side, but rarely focused on the receiving side. Usually, in the case of remittance for foreign destinations, the remittance content is often decided on the remittance side and the receiving side, so in the present invention, it is noted that the remittance content can be registered in the reservation database on the receiving side instead of the transmitting side. Therefore, a new system for labor saving can be constructed. Although the present invention focuses on labor saving in foreign exchange transactions, the present invention can be applied to settlement even for domestic transactions if the remittance content is determined in advance by the sender and recipient. Is possible. For example, a transaction in which customers and contractors can communicate with each other and the amount of money to be sent and transaction information can be determined in advance. Settlement of non-regular, non-fixed amount transactions, and receipt of political contributions with a predetermined amount System etc. can be considered.

  As mentioned above, although this invention was demonstrated using embodiment, it cannot be overemphasized that the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiments. Further, it is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Receivable remittance receiving system 10 Foreign exchange processing host computer 11 Message receiving part 12 Message book and verification part 13 Message matching part 14 Deposit processing part 15 Deposit reservation registration part 16 Deposit reservation DB monitoring part 17 Arrival guidance information DB
18 Payment reservation DB
20 Account host computer 30 Net banking reception computer (net banking server)
31 Cash Reservation Reservation Department 40 Network within bank (intranet)
50 Remittance Bank Computer System 60 Dedicated Network 70 Customer Terminal 80 Internet 100 Remittance Message (Destination Message)
200 Payment reservation information registration screen 300 Payment reservation information registration completion screen 400 Payment reservation registration information confirmation screen

Claims (7)

Receiving remittance receiving system in the foreign exchange business of financial institutions,
The forex processing host computer, the net banking reception computer, and the accounting host computer are connected so that data communication is possible.
The net banking reception computer includes a deposit reservation reception unit that receives deposit reservation information corresponding to a destination transfer via the Internet from a customer terminal of a customer who receives the destination transfer,
The forex processing host computer is:
A deposit reservation registration unit that receives the received deposit reservation information from the computer for accepting net banking and registers it as reservation data in the deposit reservation DB;
A telegram receiver that receives remittance messages from overseas remittance systems;
Analyzing the received remittance message and mapping to remittance message data for each predetermined item;
A message matching unit that compares the remittance message data with the reservation data registered in the deposit reservation DB, and determines a match or mismatch;
Deposit that sends a deposit request for depositing the remittance included in the remittance message data determined to match the reservation data by the message matching unit to the payee account included in the reservation data to the account host computer With a processing unit,
Receivable remittance receiving system characterized by that.   The foreign exchange processing host computer, when the remittance message arrives later than the payment specified date included in the reservation data, transmits a delay notification to the customer terminal according to the customer's specification. The destination remittance receiving system according to claim 1.   Even if the remittance amount included in the remittance message data is smaller than the remittance amount included in the reservation data, the electronic message matching unit may receive the payment if the difference is within the allowable range designated by the customer. The system according to claim 1, wherein the system is executed.   The payment receipt information includes means for allowing the customer to register the receipt reservation information item separately for a change item that changes for each transaction and a non-change item that does not change for each transaction. Item 2. The destination remittance receiving system according to Item 1.   In a case where the customer requests a plurality of senders to receive a certain amount of money to one recipient account when charging for a specific product or service, the deposit reservation registration unit 2. The destination according to claim 1, wherein information for associating one reservation data with a plurality of remittance message data from the plurality of remittors is added and stored in the deposit reservation DB. Remittance receipt system.   The message matching unit determines that the remittance account included in the remittance message data and the reservation data is a virtual remittance account in a case where remittance message data from the plurality of remittances is associated with the one reservation data. 6. The destination of claim 5, wherein a plurality of remittance message data having the same virtual remittance account is set as a comparison target of the reservation data, and a match or mismatch of the remittance account is determined. Remittance receipt system. A method for receiving remittance to a destination in a foreign exchange business system of a financial institution composed of a plurality of computers connected to be able to communicate data,
One of the plurality of computers is
Receiving deposit reservation information corresponding to the destination transfer from the customer terminal of the customer receiving the destination transfer via the Internet;
Receiving the received deposit reservation information and registering it as reservation data in the deposit reservation DB;
Receiving a remittance message from an overseas remittance system;
Analyzing the received remittance message and mapping the remittance message data for each predetermined item;
Comparing the remittance message data and the reservation data registered in the deposit reservation DB, and determining a match or mismatch;
Executing a process for depositing a remittance amount included in the remittance message data determined to match the reservation data by the determining step to a payee account included in the reservation data;
A method for receiving a remittance to a destination.

Images