JP2018136611A - Transfer management device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To achieve further efficient automatic payment processing in dealing with incoming transfer error.SOLUTION: A transfer management device comprises: a beneficiary record master which records a beneficiary account and a beneficiary account name as beneficiary account information; a master update unit which, on the basis of a beneficiary account name being modified through operator operation when a payment unacceptability telegram is received from a host device, adds the beneficiary account name before the modification to the beneficiary account information; and an automatic payment unit which, when the payment unacceptability telegram is received, transmits a payment telegram to the host device on the basis of the beneficiary account information of the beneficiary record master if the unit retrieves the beneficiary record master and with it a beneficiary account and a beneficiary account name of the payment unacceptability telegram match the beneficiary account information. The master update unit creates a read-replacement name on the basis of a predetermined read-replacement pattern relative to the beneficiary account name registered in the beneficiary record master and additionally registers the beneficiary account and the read-replacement name in the beneficiary record master.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a transfer management device and a program.

  In recent years, for example, various methods for efficiently comparing information registered in a database of a financial institution with information specified as search information have been proposed. For example, Patent Literature 1 and Patent Literature 2 disclose a technique for expanding a kana name from an input kanji name and searching a database using the kana name.

  Further, in Patent Document 3, if the name of the kana stored in the database of the financial institution does not match the input name of the kana, the input name of the kana is transformed and stored in the database. Techniques for comparison are disclosed.

  Patent Document 4 and Patent Document 5 disclose a technique for comparing and comparing both the name of a kana stored in a database and the name of an input kana according to the same standard.

  Further, Patent Document 6 discloses a technique for automatically performing a cancellation process on and after the next time with respect to a name that has been subjected to a deposit process even if there is a difference in ownership at the time of the transfer cancellation process in a financial institution. .

  Patent Document 7 discloses a technique for correcting a Kana name input according to a predetermined standard and performing a deposit process when the Kana name stored in a database of a financial institution does not match the input Kana name. Is disclosed.

JP-A-6-12456 JP 2008-158655 A JP 2008-192022 A JP 2002-259711 A JP 2006-157374 A JP 2001-306801 A JP-A-2005-107605

  However, in the technologies described in Patent Documents 1 to 5 and Patent Document 7, since the process related to the name of the kana is executed each time, it is difficult to say that the process is efficient, and there is a concern about an increase in the processing load. Further, in the technique described in Patent Document 6, only the name of the person who actually performed the deposit process is effective in the subsequent cancellation process. Is difficult.

  Therefore, the present invention has been made in view of the above problems, and an object of the present invention is to provide a new method capable of realizing more efficient automatic deposit processing in response to an error in a destination transfer. Another object of the present invention is to provide an improved transfer management apparatus and program.

  In order to solve the above problems, according to an aspect of the present invention, there is provided a transfer management device for processing a payee's transfer, wherein the payee account and the payee account name are recorded as payee account information. A master that newly adds a name of a payee account before correction to the payee account information based on the fact that the payee account name is corrected by an operator operation when a non-payable message is received from the master and the host device. An update unit, and an automatic deposit unit that transmits a deposit message using a recipient account name modified based on the operator operation to the host device, and the master update unit is added to the recipient record master For the payee account name, a read name is created based on a predetermined read pattern, and the payee account and the read name are additionally registered in the payee record master, When the non-payable message is received, the unit searches the payee record master, and if the payee account of the non-payable message and the name of the payee account match the payee account information, A transfer management device is provided, wherein the deposit electronic message is transmitted to the host device based on the payee account information of the person record master.

  The transfer management device further includes a personal name database that stores the name and kana name of a personal name, and the master update unit obtains the name of the Chinese character obtained by referring to the host device based on the recipient account. The name may be converted into a kana name by a personal name database, and the kana name may be additionally registered as the replacement name.

  The master update unit may additionally register the related account obtained by referring to the host device based on the payee account and the read name in association with the payee record master.

  In order to solve the above-mentioned problem, according to another aspect of the present invention, a computer is a transfer management device for processing a destination transfer, and a payee account and a payee account name are indicated as payee account information. And when the non-payable message is received from the host device, the name of the recipient account is corrected based on the fact that the name of the recipient account is corrected by an operator operation. A master update unit to be newly added, and an automatic deposit unit that transmits a deposit message using a payee account name modified based on the operator operation to the host device, the master update unit, A replacement name is created based on a predetermined replacement pattern for the name of the payee account added to the payee record master, and the payee account and the read name are stored in the payee record master. When the non-payable message is received, the automatic depositing unit searches the payee record master, and the payee account of the non-payable message and the name of the payee account include the payee account information. A program for functioning as a transfer management device is provided, in which, when they match, the deposit electronic message is transmitted to the host device based on the payee account information of the payee record master. .

  As described above, according to the present invention, it is possible to realize a more efficient automatic depositing process in response to an error in a destination transfer.

It is a sequence diagram for demonstrating the destination error process in the concentration center relevant to this invention. It is a sequence diagram for demonstrating the destination error process in the concentration center relevant to this invention which concerns on the same embodiment. It is a sequence diagram which shows the flow of the to-be-directed error process by the operator system relevant to this invention which concerns on the embodiment. It is a sequence diagram which shows the flow of the directed error process by the system system relevant to this invention which concerns on the same embodiment. It is a figure for demonstrating the outline | summary of embodiment which concerns on this invention. It is an example of a functional block diagram of a transfer management device according to the embodiment. It is a figure for demonstrating the production | generation of the replacement name based on the notation fluctuation pattern by the master update part which concerns on the same embodiment. It is a figure for demonstrating the additional registration of the replacement name based on the organization organization by the master update part which concerns on the embodiment. It is a figure for demonstrating the production | generation of the replacement name based on the reading kana pattern by the master update part which concerns on the same embodiment. It is a figure for demonstrating the additional registration of the replacement name with respect to another account by the master update part which concerns on the embodiment. It is a flowchart which shows the flow of the process judgment of the message | telegram generation | occurrence | production by the transfer management apparatus concerning the embodiment. It is a flowchart which shows the flow of the additional registration of the replacement name by the transfer management apparatus concerning the embodiment. It is a hardware structural example of the transfer management apparatus which concerns on this invention.

  Exemplary embodiments of the present invention will be described below in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.

<1. Embodiment>
<< 1.1. Outline of Embodiment >>
The present invention is based on the fact that the name of the payee account of the transfer that has become non-payable matches the name of the payee account registered in the payee record master in response to the error of the payee transfer at the financial institution. By automatically transmitting the corrected deposit message, the processing efficiency is improved.

  First, the concept of destinations and destinations in financial institutions will be described. Generally, in the financial industry, a bank that performs remittance or transfer requested by a customer to another bank is called a destination bank, and a bank that receives remittance or transfer from the destination bank is called a destination bank. In other words, the error handling of the above-mentioned destination transfer (hereinafter also referred to as destination error processing) means that if the transfer data sent from the destination bank cannot be deposited into the payee's account, the destination bank side A series of processing to be performed. On the other hand, when the transfer data transmitted via various channels becomes non-payable on the destination bank side, error handling performed on the destination bank side is referred to as destination error processing. Conventionally, the above-described destination error processing and destination error processing are generally performed at each branch office.

  On the other hand, in recent years, an attempt has been made to centralize operations such as destination error processing and destination error processing in a centralized center. FIG. 1 is a sequence diagram for explaining destination error processing in a centralized center related to the present invention. FIG. 1 shows a flow of a transfer process performed between the customer 10, the sales office 20, the centralized center, the own bank host 50, and the transfer destination host 65.

  Referring to FIG. 1, first, a destination message is transmitted to the local host 50 through various channels. The destination message is electronic information including a recipient account name, an account number, and the like, and is generated and transmitted based on a transfer operation. For example, the destination message may be transmitted based on a transfer operation performed by the customer 10 using Internet banking (S1101-1), or may be transmitted based on a transfer operation performed by a bank employee at the sales office 20. Good (S1101-2). The destination message may be transmitted based on processing performed by the operator in the centralized center 30 (S1101-3).

  Next, the host host 50 transmits the destination message to the transfer destination host 65 selected based on the received destination message (S1102).

  Here, when the destination message transmitted in step S1102 becomes non-payable at the transfer destination host 65 (S1103), the transfer destination host 65 transmits an inquiry message to the local host 50 based on an operation of the operator or the like. (S1104).

  Next, the local host 50 transmits the inquiry message received in step S1104 to the centralized center 30 (S1105).

  Subsequently, the centralized center 30 confirms the inquiry message received in step S1105 (S1106), and confirms the contents related to the transfer to the customer 10. Here, the above-described content confirmation may be performed, for example, by telephone (S1107-1), or may be performed using a request form using FAX or the like (S1107-2).

  Here, when the content can be confirmed, the centralized center 30 transmits a correction message or a combination message to the local host 50 based on the confirmation content (S1108), and the local host 50 transmits the correction message or the combination message. Is further transmitted to the transfer destination host 65 (S1109).

  As described above, a series of processes (S1106 to S1108: A) performed in the centralized center 30 for the inquiry message transmitted from the transfer destination host 65 based on the transfer that has become impossible to deposit is referred to as a destination error process.

  On the other hand, FIG. 2 is a sequence diagram for explaining a destination error process in the centralized center related to the present invention. FIG. 2 shows a flow of a transfer process performed between the sales office 20, the centralized center, the own bank host 50, and the transfer bank host 75.

  Referring to FIG. 2, first, a destination message generated based on various transfer operations is transmitted from the transfer host 75 to the own host 50 (S1201).

  Here, when the destination message transmitted in step S1201 becomes non-payable in its own host 50 (S1202), the own host 50 transmits a non-depositable message to the centralized center 30 (S1203).

  Subsequently, the centralized center 30 confirms the non-payable message transmitted in step S1203 (S1204), and makes a process determination related to the destination error process (S1205).

  For example, if it is determined in step S1205 that notification or confirmation to the sales office 20 is necessary, the centralized center 30 may transmit a sales office notification to the sales office 20 (S1206).

  For example, if it is determined in step S1205 that the transfer amount needs to be returned, the central center 30 sends a return message to the host host 50 (S1207). The return message is further transmitted to the transfer bank host 75 (S1208).

  Further, for example, if it is determined in step S1205 that the reason for non-payment is an acceptable difference in the name of the recipient account and there is no problem even if the deposit process is performed, the concentration center 30 The depositing electronic message may be transmitted to the owning host 50 (S1209), and the owning host 50 may perform the depositing process based on the depositing message transmitted in step S1209 (S1210).

  As described above, a series of processes (S1204 to S1209: B) performed in the centralized center 30 for a non-payable message transmitted from the banking host 50 based on the transfer that has become non-payable is referred to as a directed error process.

  The outline of the destination error processing and the destination error processing related to the present invention has been described above. In the above description using FIG. 1 and FIG. 2, the case where the destination error processing and the destination error processing are performed centrally in the centralized center has been described. At this time, in a general centralized center, there is a case where a method (hereinafter, also referred to as an operator method) in which an operator makes a process determination related to a destination error process or a destination error process is adopted.

  FIG. 3 is a sequence diagram showing a flow of a destination error process by an operator method related to the present invention. FIG. 3 shows a flow of a series of processes performed among the transfer bank 70, the host bank 50, the transfer management device 40, and the operator 35. Here, the transfer management device 40 may be an information processing device that is installed on the centralized center 30 or the cloud, and electronically processes a part of the business in the centralized center 30. Moreover, the transfer bank 70 in FIG. 3 is a concept indicating the entire destination bank including bank employees, sales offices, centralized centers, hosts, and the like.

  Referring to FIG. 3, first, a destination message is transmitted from the transfer bank 70 to the host host 50 (S1301). Here, when it becomes impossible to deposit money at the own bank host 50 (S1302), the own host host 50 transmits a deposit impossible message to the transfer management device 40 (S1303).

  Next, the operator 35 confirms the non-payable message transmitted to the transfer management device 40 in step S1301 (S1304), and makes an account inquiry to the bank host (S1305). Subsequently, the host 50 transmits an account inquiry result based on the account inquiry performed in step S1305 (S1306). Note that the processing in steps S1305 and S1306 may be performed via an operator terminal (not shown) or the transfer management device 40, for example.

  Next, the operator 35 makes a process determination related to the destination error process based on the account inquiry result acquired in step S1306 and the business rules of each financial institution (S1307).

  At this time, for example, in the process determination in step S1307, if it is determined that the reason for non-payment is an acceptable difference in the name of the recipient account and there is no problem even if the deposit process is performed, the operator 35 proceeds to step S1306. A payment message in which the name of the recipient account is corrected based on the acquired account inquiry result is transmitted to the bank host 50 (S1308). In addition, the host 50 performs a deposit process based on the deposit message received in step S1308 (S1309).

  For example, if it is determined in step S1307 that the transfer amount needs to be returned, the operator 35 creates a return message and transmits it to the host 50 (S1310). In this case, the own host 50 further transmits the return message received in step S1310 to the transfer line 70 (1311).

  For example, if it is determined in step S1307 that the transfer line 70 needs to be inquired, the operator 35 creates an inquiry message and transmits it to the host 50 (S1312). In this case, the own bank host 50 further transmits the inquiry message received in step S1312 to the transfer line 70 (S1313), and receives an answer message created based on the inquiry message from the transfer line 70 (S1314). .

  Subsequently, the own host 50 transmits the reply message received in step S1314 to the transfer management device 40 (S1315), and the operator confirms the above reply message (S1316), and then makes another processing determination (S1316). S1317).

  Heretofore, the flow of the destination error processing by the operator method has been described. As described above, in the operator method, the operator makes all the process determinations related to the target error process, so that the operation is very inefficient and the operator's cost tends to increase. For this reason, in recent years, a system (hereinafter also referred to as a system system) in which a system such as a transfer management device 40 automatically performs processing determination related to a destination error process is becoming widespread.

  FIG. 4 is a sequence diagram showing the flow of the target error processing by the system method related to the present invention. FIG. 4 shows a flow of a series of processes performed among the transfer bank 70, the host bank 50, the transfer management device 40, and the operator 35.

  Referring to FIG. 4, as in the case of the operator method, first, a destination message is transmitted from the transfer bank 70 to the host host 50 (S1401). Here, when it becomes impossible to deposit money in the banking host 50 (S1402), the banking host 50 transmits a banking impossible message to the transfer management device 40 (S1403).

  Next, the transfer management device 40 makes a process determination based on the non-payable message received in step S1403 (S1404).

  At this time, for example, if it is determined in step S1404 that the reason for non-payment matches the predetermined deposit condition, the transfer management device 40 automatically generates a deposit telegram and transmits it to the bank 50 (S1405). ). In addition, the host 50 performs a deposit process based on the deposit message received in step S1405 (S1406).

  For example, if it is determined in step S1404 that the reason for non-payment matches a predetermined return condition, the transfer management device 40 automatically generates a return message and transmits it to the host 50 (S1407). . In this case, the local host 50 further transmits the return message received in step S1407 to the transfer line 70 (1408).

  For example, if it is determined in step S1404 that the reason for non-payment does not match a predetermined deposit condition or a return condition, the transfer management device 40 automatically generates an inquiry message and executes the host 50 (S1409). In this case, the own-host 50 further transmits the inquiry message received in step S1409 to the transfer line 70 (S1410), and receives an answer message created based on the inquiry message from the transfer line 70 (S1411). . Subsequently, the local host 50 transmits the reply message received in step S1411 to the transfer management device 40 (S1412).

  Next, the transfer management device 40 makes a process determination again based on the reply message received in step S1412 (S1413). At this time, if the reply message matches a predetermined condition, the transfer management device 40 may automatically generate a deposit message or a return message and send it to the bank host 50.

  On the other hand, if the response message does not match the predetermined condition, the operator 35 confirms the response message (S1414) and makes a final processing decision (S1415), as in the case of the operator method. .

  As described above, in the targeted error processing by the system method, it is possible to reduce the burden and cost of the operator by systematizing the processing judgment related to the targeted error processing. On the other hand, in the system method, a strict and rational logic is required because the computer makes a determination related to the deposit process.

  The transfer management device 40 according to the present invention has been conceived by paying attention to the above points, and can achieve more accurate process determination in the destination error process. FIG. 5 is a diagram for explaining the outline of the present embodiment.

  FIG. 5 shows data stored in the transfer request form t1 created by the customer and the account master 530 of the bank host 50. At this time, the own host 50 searches the account master 530 for the name of the payee account and the account number included in the destination message generated and transmitted based on the transfer request document t1, and only when matching data exists. Deposit money for the account number.

  On the other hand, as shown in FIG. 5, when the payee account name is different from the data recorded in the account master 530, the bank host 50 transmits a non-payable message to the transfer management device 40. In FIG. 5, the name of the recipient account described in the transfer request form t1 is “K) Nippon Shiyouten”, and the name of the recipient account recorded in the account master 530 is “K) Nippon Shiyouten”. An example is given in some cases. As described above, the majority of the reasons for the inability to deposit, that is, the necessity of the destination error processing, are the differences in the name of the payee account.

  At this time, the transfer management device 40 according to the present embodiment refers to the payee record master 420 based on the non-payable message transmitted from the bank host 50, and the payee account name information corresponding to the payee record master 420 is obtained. If it exists, a deposit message may be automatically generated and transmitted to the host 50.

  The payee account information described above may be information registered by an operator or the like, including a payee account (branch / subject / account number) and a payee account name. If an operator makes a deposit process for a transfer that has become non-payable due to a difference in the name of the payee's account, if the payment process is performed on the grounds that the difference in the name of the payee's account is acceptable, the incorrect receipt included in the non-payable message The person account name is registered in the recipient record master 420. That is, the transfer management device 40 according to the present embodiment can automatically generate and transmit a deposit message when there is a past deposit record related to the name of the payee account included in the deposit impossible message.

  Furthermore, the transfer management device 40 according to the present embodiment creates a replacement name based on a predetermined replacement pattern for the recipient account name registered by the operator, and adds the replacement name to the recipient performance master 420. You may register. According to the above-described function of the transfer management device 40 according to the present embodiment, it is possible to flexibly cope with a difference pattern of similar payee account names, and to realize more efficient destination error processing. It becomes possible. In the following description, the generation of the replacement name by the transfer management device 40 according to the present embodiment will be described in detail.

<< 1.2. Functional configuration example of transfer management device 40 >>
Next, a functional configuration example of the transfer management device 40 according to the present embodiment will be described. FIG. 6 is an example of a functional block diagram of the transfer management device 40 according to the present embodiment. Referring to FIG. 6, the transfer management device 40 according to the present embodiment includes a message generation unit 410, a recipient record master 420, a master update unit 430, a person name DB 440, and a communication unit 450.

(Message generation unit 410)
The message generation unit 410 according to the present embodiment has a function of making a process determination based on a non-payable message transmitted from the own host 50 and generating various messages corresponding to the process determination. The message generation unit 410 may automatically generate, for example, a deposit message, a return message, or an inquiry message, and cause the communication unit 450 to transmit the message.

  At this time, when a non-depositable message is received from the banking host 50, the message generation unit 410 according to the present embodiment searches the recipient record master 420, and receives the non-payable message recipient account and the name of the recipient account. May match the payee account information acquired from the payee record master 420, a payment message may be sent to the bank host 50. More specifically, the message generation unit 410 according to the present embodiment can cause the own bank host 50 to transmit a deposit message generated based on the recipient account information acquired from the recipient record master 420. That is, the message generation unit 410 according to the present embodiment has a function as an automatic depositing unit that performs automatic depositing based on the non-payable message and the recipient account information recorded in the recipient record master 420.

  In addition, the message generation unit 410 according to the present embodiment automatically selects either the return message or the inquiry message when the recipient account and the name of the recipient account of the non-payable message do not exist in the recipient record master 420. May be generated and transmitted to the communication unit 450. At this time, the message generator 410 may automatically generate a return message and send it to the host 50 based on the fact that the destination message that has become non-payable has an instruction such as “no inquiry required”. Further, the message generation unit 410 may automatically generate an inquiry message and send it to the host host 50 when there is no instruction such as “no inquiry” in the destination message.

  Further, the message generation unit 410 according to the present embodiment may operate based on an operator operation. For example, when the payee account information is corrected by an operator operation, the electronic message generation unit 410 according to the present embodiment generates a deposit message based on the corrected payee account information and transmits it to the local host 50. Good.

  According to the above-mentioned function of the message generation unit 410 according to the present embodiment, it is possible to accurately and automatically perform a response to a non-payable message, that is, a process determination in the destination error process, Costs can be reduced.

(Recipient achievement master 420)
The payee record master 420 according to the present embodiment is a database that records a payee account and a payee account name as payee account information. Here, the above-described payee account includes a branch number, account item, and account number of a financial institution.

(Master update unit 430)
The master update unit 430 according to the present embodiment has a function of updating payee account information stored in the payee record master 420. The master update unit 430 may update the payee account information based on an operator operation. For example, the master update unit 430 can register the name of the payee account determined by the operator as an allowable difference and can be deposited in the payee performance master 420. That is, when the master update unit 430 receives a non-payable message from the host 50, the master update unit 430 newly adds the payee account name to the payee account information based on the fact that the payee account name is corrected by an operator operation. You can do it.

  In addition, the master update unit 430 according to the present embodiment creates a replacement name based on a predetermined replacement pattern for the recipient account name added to the recipient performance master 420, and stores the recipient account in the recipient performance master 420. One of the features is to additionally register the replacement name and the name. Here, the above replacement pattern may include, for example, a notation shaking pattern or a reading kana pattern related to a kanji name. In other words, the master update unit 430 according to the present embodiment automatically creates a replacement name based on the notation shaking pattern and the reading kana pattern from the name of the recipient account registered in the recipient result master 420, thereby obtaining the recipient result. The payee account information of the master 420 can be further enhanced. Note that the master update unit 430 may execute the above processing by, for example, a night batch. Details of the functions of the master update unit 430 according to the present embodiment will be described later.

(Personal name DB440)
The personal name DB 440 according to the present embodiment is a database that stores a kanji name of a personal name and one or more kana names corresponding to the kanji name in association with each other. The personal name DB 440 according to the present embodiment may store a kanji name and a kana name related to the institution name in addition to the personal name.

(Communication unit 450)
The communication unit 450 according to the present embodiment has a function of performing information communication with the local host 50 via a network. For example, the communication unit 450 receives a non-payable message from the host host 50 and transmits the deposit message, return message, inquiry message, and the like generated by the message generation unit 410 to the host host 50. Communication unit 450 may perform information communication with an operator terminal (not shown) operated by the operator. The communication unit 450 may receive various information input to the operator terminal and transmit it to each component included in the transfer management device 40. Moreover, the communication part 450 can transmit the result of the process which each structure with which the transfer management apparatus 40 is provided, etc. to an operator terminal.

  The function configuration example of the transfer management device 40 according to the present embodiment has been described above. Note that the above-described configuration described with reference to FIG. 6 is merely an example, and the functional configuration of the transfer management device 40 according to the present embodiment is not limited to the related example. The transfer management device 40 according to the present embodiment can further include a configuration other than that shown in FIG. For example, the transfer management device 40 may further include an input unit that receives an input operation such as an operator, and an output unit that outputs a processing result.

  Moreover, each structure with which the transfer management apparatus 40 which concerns on this embodiment is provided can also be implement | achieved by disperse | distributing with several apparatuses. For example, the recipient record master 420 and the person name DB 440 described above may be provided in a device separate from the transfer management device 40. The transfer management device 40 according to the present embodiment can be flexibly modified according to the operation or specifications of the financial institution.

<< 1.3. Details of creating a replacement name >>
Next, details of creation of a replacement name by the master update unit 430 according to the present embodiment will be described. As described above, the master updating unit 430 according to the present embodiment automatically creates a replacement name based on the notation shaking pattern and the reading kana pattern from the name of the recipient account registered in the recipient performance master 420, and the replacement The name and the payee account can be additionally registered in the payee record master 420 in association with each other.

(Generation of replacement names based on the shaking pattern)
First, generation of the replacement name based on the notation fluctuation pattern by the master update unit 430 will be described in detail. FIG. 7 is a diagram for explaining the generation of the replacement name based on the notation fluctuation pattern by the master update unit 430.

  FIG. 7 shows a transfer request form t2 created by the customer and account master information M1 stored in the account master 530 of the host 50. At this time, the own host 50 generates a non-payable message and sends it to the transfer management device 40 based on the fact that the recipient account name included in the destination message transmitted based on the transfer request form t2 is different from the account master information M1. Send.

  Subsequently, the operator 35 confirms the non-payable message via the operator terminal and makes a process determination. FIG. 7 shows an example in which the operator 35 determines that the deposit can be made because the difference in the name of the payee account is only the difference between the previous stock and the subsequent stock. At this time, the operator 35 inputs the permitted recipient account name “Nippon Shiyouten (K”) to the transfer management device 40 via the operator terminal etc. At this time, the master update unit 430 receives the input recipient. The account name “Nippon Shiyouten (K”) is newly registered in the payee account information M2 of the payee record master 420, and the message generation unit 410 generates a deposit message in which the account name is corrected, and the host 50 May be sent to

  In addition, the master update unit 430 according to the present embodiment generates a replacement name based on the notation fluctuation pattern from the recipient account name “Nippon Shiyouten (K”) registered above, and performs additional registration in the recipient account information M2. In the case of the example shown in Fig. 7, the master updating unit 430 uses the newly registered payee account names "Nippon Shiyo Ten (Ka") and the replacement names "Kabushiki Gaishiya Nitsupon Shiyo Ten" and "Nippon Shiyo Tenkabushiki Shiya". Is created and additional registration is performed.

  As described above, the notation fluctuation pattern according to the present embodiment may include the abbreviation notation of the corporation type. The above abbreviations include abbreviations relating to various corporations, such as limited liability companies, limited partnerships, medical corporations, foundations, and associations, as well as corporations.

  Further, the notation fluctuation pattern according to the present embodiment is not limited to the above abbreviation notation. The notation fluctuation pattern according to the present embodiment may include commonly used name fluctuations such as “Nihon” and “Nippon” shown in FIG.

  Further, the notation fluctuation pattern according to the present embodiment includes the presence / absence of a space, omission of long notes (center and center, etc.) or hiragana notation (center and centera, etc.), alphabetical and numerical hiragana notation (A and A, 7 and Nana).

  According to the function of the master update unit 430 according to the present embodiment, it is possible to create a plurality of similar replacement names on the basis of differences in the recipient account names that the operator 35 determines to be acceptable. It is possible to greatly increase the number of cases in which the message generation unit 410 automatically generates a deposit message at the time of processing the destination error.

  In addition, according to the master update unit 430 according to the present embodiment, as the data determined to be acceptable can be accumulated, a wider variety of replacement names can be automatically registered. It becomes possible to improve.

  In addition, the master update unit 430 according to the present embodiment can also develop the created replacement name in a related account related to the payee account. More specifically, the master update unit 430 according to the present embodiment associates the related account obtained by referring to the host 50 based on the payee account included in the payee account information and the name of the replacement, and recognizes the payee record. Additional registration with the master 420 may be performed. Here, the related account may be acquired based on a recipient organization system related to the recipient account.

  FIG. 8 is a diagram for explaining additional registration of the replacement name based on the organization organization by the master update unit 430 according to the present embodiment. FIG. 8 shows a case where it becomes impossible to deposit money due to a difference in the abbreviation notation of the corporation type as in the example of FIG. On the other hand, in FIG. 8, unlike FIG. 7, the name of the corporation's branch is included in the name of the recipient account.

  At this time, the master updating unit 430 according to the present embodiment acquires a related account based on the recipient's organization organization from the own host 50 based on the recipient account, and receives the replacement name created in the related account in association with the received account. Additional registration can be made in the human achievement master 420. In the example shown in FIG. 8, the master update unit 430 creates a replacement name for the Yokohama branch and the Osaka branch in addition to the Tokyo branch related to the non-payable message, and performs additional registration in the recipient record master 420.

  According to the above function of the master updating unit 430 according to the present embodiment, it is possible to develop a replacement name that is similar to a replacement name created for a recipient account name of a certain organization in a related organization of the organization. Thus, it is possible to realize more efficient targeted error processing.

  In the above, a branch office of a corporation has been described as an example of a related organization. However, the related organization according to the present embodiment may include a sales office, a store, a department, and the like. FIG. 8 shows an example in which the name of the recipient account including the branch office name is specified in the transfer request form t3. However, the master update unit 430 does not include the organization information in the name of the received account. Even so, the above processing can be realized by making an inquiry to the host 50.

(Generating a replacement name based on a reading pattern)
Subsequently, generation of the replacement name based on the reading kana pattern related to the kanji name by the master update unit 430 will be described in detail. The master update unit 430 according to the present embodiment converts the kanji name obtained by referring to the bank host 50 based on the payee account into a kana name by the personal name DB 440, and additionally registers the kana name as a replacement name. Can do. FIG. 9 is a diagram for explaining generation of a replacement name based on a reading kana pattern by the master update unit 430.

  FIG. 9 shows the transfer request form t4 created by the customer and the account master information M1 stored in the account master 530 of the own host 50. At this time, the own host 50 generates a non-payable message and sends it to the transfer management device 40 based on the fact that the recipient account name included in the destination message transmitted based on the transfer request document t4 is different from the account master information M1. Send.

  Subsequently, the operator 35 confirms the non-payable message via the operator terminal and makes a process determination. FIG. 9 shows an example where the operator 35 determines that the deposit can be made because the difference in the name of the payee account is the difference in the reading kana related to the name of the Chinese character. At this time, the operator 35 inputs the permitted payee account name “Joito Kouichi” to the transfer management device 40 via the operator terminal or the like. At this time, the master update unit 430 newly registers the input recipient account name “Jioto Koichi” in the recipient account information M2 of the recipient record master 420, and the message generation unit 410 changes the recipient account name. A corrected deposit message may be generated and transmitted to the host 50.

  In addition, the master update unit 430 according to the present embodiment acquires the name of the recipient's kanji from the account ledger 550 of the bank 50 based on the registered recipient account, and uses the name DB 440 to obtain the name of the recipient. Can be converted to full name. At this time, the kana name acquired by the master update unit 430 may include a plurality of reading patterns.

  For example, in the example shown in FIG. 9, the master update unit 430 acquires a plurality of kana names as replacement names by converting the kanji name “Kouichi Ueto” acquired from the account ledger 550 by the personal name DB 440. Specifically, the master update unit 430 acquires four Kana names “Wet Kouichi”, “Aget Kouichi”, “Wet Hirokaz”, and “Ageto Hirokas” as replacement names, and additionally registers them in the recipient account information M2. Is going.

  As described above, according to the master update unit 430 according to the present embodiment, it is possible to register a kana name converted from a kanji name as a replacement name, and efficiently deal with a target error caused by an incorrect reading name. It becomes possible to do.

  In addition, the master update unit 430 according to the present embodiment can additionally register the converted name in association with another account of the recipient as a replacement name. Here, the above-mentioned separate account may be different from the payee account in which at least one of the branch number, the account subject, and the account number cannot be deposited. The other account according to the present embodiment may include, for example, an account of another branch owned by the recipient.

  FIG. 10 is a diagram for explaining additional registration of a replacement name for another account by the master update unit 430 according to the present embodiment. FIG. 10 shows a case where it becomes impossible to deposit due to a difference in reading characters as in the example of FIG. On the other hand, in the example illustrated in FIG. 10, the master update unit 430 additionally registers the converted name in association with the separate account based on the information of the separate account acquired from the host 50. doing. At this time, the master update unit 430 performs name collation on the account ledger 550 based on information such as the recipient's kanji name, address, date of birth, etc., thereby obtaining information on another account that eliminates the possibility of the same name and the same name. Can be acquired.

  According to the above-described function of the master update unit 430 according to the present embodiment, the replacement name of the name that has been created for a certain recipient account name can be expanded to another account that the recipient has, and more efficiently. Can be realized.

<< 1.4. Flow of operation of transfer management device 40 >>
Next, the operation flow of the transfer management device 40 according to the present embodiment will be described in detail. First, the flow of processing determination for message generation by the transfer management device 40 according to the present embodiment will be described. FIG. 11 is a flowchart showing a flow of processing determination of message generation by the transfer management device 40.

  Referring to FIG. 11, first, the communication unit 450 of the transfer management device 40 receives a non-payable message from the bank host 50 (S2101).

  Next, the message generation unit 410 according to the present embodiment determines whether or not the corresponding recipient account information exists in the recipient record master 420 (S2102). That is, the message generation unit 410 can determine whether or not there is a replacement name corresponding to the name of the payee account that has become non-payable in the payee record master 420.

  Here, when the corresponding replacement name exists in the recipient record master 420 (S2101: Yes), the message generation unit 410 automatically generates a deposit message and transmits it to the host 50 through the communication unit 450. (S2103).

  On the other hand, if the corresponding replacement name does not exist in the recipient record master 420 (S2101: No), then the message generation unit 410 determines whether or not there is an “inquiry unnecessary” instruction for the destination message that has become non-payable. Is determined (S2104).

  Here, when there is an instruction “not required” in the destination message (S2104: Yes), the message generation unit 410 automatically generates a return message and transmits it to the local host 50 via the communication unit 450 (S2105). ).

  On the other hand, if there is no “reference unnecessary” instruction in the destination message (S2104: Yes), the message generation unit 410 automatically generates an inquiry message and transmits it to the host 50 through the communication unit 450 ( S2106).

  The flow of processing determination by the transfer management device 40 according to the present embodiment has been described above. Subsequently, a flow of additional registration of a replacement name by the transfer management device 40 according to the present embodiment will be described in detail. FIG. 12 is a flowchart showing a flow of additional registration of a replacement name by the transfer management device 40.

  Referring to FIG. 12, first, the master update unit 430 newly registers a payee account name in the payee record master 420 based on an operator operation (S2201).

  Subsequently, the master update unit 430 acquires the recipient's kanji name from the bank host 50 based on the recipient account (S2202).

  Further, the master update unit 430 acquires related account information from the bank host 50 based on the payee account (S2203).

  Subsequently, the master update unit 430 creates a replacement name based on the kanji name and the notation fluctuation pattern acquired in step S2202 (S2204).

  Next, the master update unit 430 additionally registers the replacement name created in step S2204 with the corresponding payee account or the related account acquired in step S2203 in the payee record master (S2205).

<2. Hardware configuration example>
Next, a hardware configuration example of the transfer management device 40 according to an embodiment of the present invention will be described. FIG. 13 is a block diagram illustrating a hardware configuration example of the transfer management device 40 according to an embodiment of the present invention. Referring to FIG. 13, the transfer management device 40 includes, for example, a CPU 871, a ROM 872, a RAM 873, a host bus 874, a bridge 875, an external bus 876, an interface 877, an input unit 878, and an output unit 879. A storage unit 880, a drive 881, a connection port 882, and a communication unit 883. Note that the hardware configuration shown here is an example, and some of the components may be omitted. Moreover, you may further include components other than the component shown here.

(CPU 871)
The CPU 871 functions as, for example, an arithmetic processing unit or a control unit, and controls all or part of the operation of each component based on various programs recorded in the ROM 872, RAM 873, storage unit 880, or removable recording medium 901. .

(ROM 872, RAM 873)
The ROM 872 is a means for storing programs read by the CPU 871, data used for calculations, and the like. In the RAM 873, for example, a program read by the CPU 871, various parameters that change as appropriate when the program is executed, and the like are temporarily or permanently stored.

(Host bus 874, bridge 875, external bus 876, interface 877)
The CPU 871, the ROM 872, and the RAM 873 are connected to each other via, for example, a host bus 874 capable of high-speed data transmission. On the other hand, the host bus 874 is connected to an external bus 876 having a relatively low data transmission speed via a bridge 875, for example. The external bus 876 is connected to various components via an interface 877.

(Input unit 878)
For the input unit 878, for example, a mouse, a keyboard, a touch panel, a button, a switch, a microphone, a lever, and the like are used. Furthermore, as the input unit 878, a remote controller (hereinafter referred to as a remote controller) that can transmit a control signal using infrared rays or other radio waves may be used.

(Output unit 879)
The output unit 879 includes acquired information such as a display device (display device) such as a CRT (Cathode Ray Tube), LCD, or organic EL, an audio output device such as a speaker or a headphone, a printer, a mobile phone, or a facsimile. Is a device capable of visually or audibly notifying a user.

(Storage unit 880)
The storage unit 880 is a device for storing various data. As the storage unit 880, for example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, a magneto-optical storage device, or the like is used.

(Drive 881)
The drive 881 is a device that reads information recorded on a removable recording medium 901 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, or writes information to the removable recording medium 901.

(Removable recording medium 901)
The removable recording medium 901 is, for example, a DVD medium, a Blu-ray (registered trademark) medium, an HD DVD medium, or various semiconductor storage media. Of course, the removable recording medium 901 may be, for example, an IC card on which a non-contact IC chip is mounted, an electronic device, or the like.

(Connection port 882)
The connection port 882 is a port for connecting an external connection device 902 such as a USB (Universal Serial Bus) port, an IEEE 1394 port, a SCSI (Small Computer System Interface), an RS-232C port, or an optical audio terminal. is there.

(External connection device 902)
The external connection device 902 is, for example, a printer, a portable music player, a digital camera, a digital video camera, or an IC recorder.

(Communication unit 883)
The communication unit 883 is a communication device for connecting to the network 903. For example, a communication card for wired or wireless LAN, Bluetooth (registered trademark), or WUSB (Wireless USB), a router for optical communication, ADSL (Asymmetric) A digital subscriber line) or a modem for various types of communication. Moreover, you may connect to telephone networks, such as an extension telephone network and a mobile telephone provider network.

<3. Summary>
As described above, the transfer management apparatus 40 according to an embodiment of the present invention can create a replacement name from the name of the payee account determined to be acceptable by the operator and register it in the payee record master 420. . In addition, the transfer management device 40 according to an embodiment of the present invention can automatically generate a deposit electronic message based on the replacement name registered in the recipient record master 420 and transmit it to the bank host 50. According to such a configuration, it is possible to realize a more efficient automatic depositing process in response to an error in a destination transfer.

  The preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field to which the present invention pertains can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that these also belong to the technical scope of the present invention.

  For example, in the above-described embodiment, the description has been made focusing on the target error processing in the financial institution, but the present technical idea can be widely applied to all systems that perform name collation.

  In addition, each step related to the processing of the transfer management device 40 according to the embodiment of the present invention does not necessarily have to be processed in time series in the order described as a flowchart. For example, each step related to the processing of the transfer management device 40 may be processed in an order different from the order described as the flowchart, or may be processed in parallel.

40 Transfer Management Device 410 Message Generation Unit 420 Recipient Performance Master 430 Master Update Unit 440 Person Name DB
450 Communication Department 50 Own Host 530 Account Master 550 Account Ledger

Claims (4)

A transfer management device for processing a destination transfer,
A payee record master that records the payee account and the payee account name as payee account information;
A master update unit for newly adding the name of the payee account before the correction to the payee account information based on the fact that the payee account name is corrected by an operator operation when receiving a non-payable message from the host device; ,
An automatic depositing unit that transmits a deposit telegram using the payee account name modified based on the operator operation to the host device;
With
The master update unit creates a replacement name based on a predetermined replacement pattern for the name of the recipient account added to the recipient performance master, and the recipient account and the replacement name in the recipient performance master. And register
The automatic depositing unit searches the payee record master when receiving the non-payable message, and when the payee account and the name of the payee account of the non-payable message match the payee account information. , Sending the deposit message to the host device based on the recipient account information of the recipient achievement master,
A transfer management device characterized by that. A personal name database that stores the names of kanji and personal names
Further comprising
The master update unit converts a kanji name obtained by referring to the host device based on the payee account into a kana name by the personal name database, and additionally registers the kana name as the replacement name.
The transfer management device according to claim 1. The master update unit associates and registers the related account obtained by referring to the host device based on the payee account and the read name in the payee record master.
The transfer management device according to claim 2. Computer
A transfer management device for processing a destination transfer,
A payee record master that records the payee account and the payee account name as payee account information;
A master update unit for newly adding the name of the payee account before the correction to the payee account information based on the fact that the payee account name is corrected by an operator operation when receiving a non-payable message from the host device; ,
An automatic depositing unit that transmits a deposit telegram using the payee account name modified based on the operator operation to the host device;
With
The master update unit creates a replacement name based on a predetermined replacement pattern for the name of the recipient account added to the recipient performance master, and the recipient account and the replacement name in the recipient performance master. And register
The automatic depositing unit searches the payee record master when receiving the non-payable message, and when the payee account and the name of the payee account of the non-payable message match the payee account information. , Sending the deposit message to the host device based on the recipient account information of the recipient achievement master,
A transfer management device, characterized by
Program to function as.

Images