JP2020035133A - Payment determination system, payment determination device, payment determination method, and program - Google Patents

Abstract

To provide a payment determination system, a payment determination device, a payment determination method, and a program capable of further improving the convenience of automatic determination as to the advisability of payment by transfer in which an account holder difference occurs.SOLUTION: In the payment determining system, a management server 22 is provided with: a message receiving unit 250 for acquiring transfer data including at least a recipient's account number and a recipient's name; a recipient account information acquisition unit 254 for acquiring, from the customer master, an account name consisting of a plurality of character strings corresponding to the account number; a payment determination unit 258 for comparing the recipient name with the account name to make a payment determination; an operator confirmation unit 260 for allowing an operator to confirm transfer data whose comparison result is inconsistent; and a determination condition storage processing unit 262 for storing information of the character strings used for matching determination by the operator among the plurality of account name character strings in association with the account number as a determination condition.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a payment determination system, a payment determination device, a payment determination method, and a program.

  In a transfer message at a financial institution, if the name of the recipient included in the transfer message is different from the name of the recipient account of the payee account indicated by the transfer message, the transfer message cannot be deposited due to the difference in the holder. The transfer contents of the transfer message for which payment was not possible are printed, and the operator can read the printed transfer contents according to the business rules and confirm the matching of the parts that should match according to the account attributes to determine whether payment is possible Is done.

  Even in the above-described system for automatically performing the replacement and the determination as to whether or not payment is possible, the replacement is performed in accordance with the replacement method defined in the business rules, and whether or not payment is determined based on the result of the replacement (coincidence or non-coincidence).

  Techniques related to such data match / mismatch determination are disclosed in Patent Documents 1 to 3, for example.

  Patent Literature 1 below discloses a technique in which data including an organization name and an individual name are compared, and a match or a mismatch is determined based on a partial match.

  Further, Patent Literature 2 discloses a technique in which, even if an address or a number is omitted, a street name or a street is matched, and if a building name can be considered to be matched, an address is considered to be matched.

  Patent Document 3 below discloses a technique of a machine translator that accumulates inference knowledge set by an operator.

JP-A-9-231232 JP 2003-173345 A JP-A-6-325083

  However, according to the conventional technology, whether or not payment can be automatically determined when the recipient name included in the transfer message and the recipient account name of the recipient account indicated by the transfer message are different only when all the character strings match. I couldn't.

  Further, in the related art, the determination is performed based on the partial match / mismatch, but none of them considers the improvement of the accuracy of the payment determination.

  Therefore, the present invention has been made in view of the above-described problems, and an object of the present invention is to improve the convenience of automatic determination of whether or not a transfer in which a difference in ownership has occurred has been made possible. It is to provide a payment determination system, a payment determination device, a payment determination method, and a program.

  In order to solve the above-described problems, according to an aspect of the present invention, a transfer data acquisition unit that acquires transfer data including at least a recipient account number and a recipient name, and a plurality of character strings corresponding to the account number. An account information acquisition unit that acquires the account name from the customer master, a payment determination unit that compares the recipient name and the account name to determine the payment, and allows the operator to confirm the transfer data in which the comparison result is inconsistent. A payment unit comprising: a confirmation unit; and a storage processing unit that stores information on a character string used for matching determination by the operator among the plurality of character strings in the account name in association with the account number as a determination condition. A determination system is provided.

  The deposit determination, when the determination condition stored in association with the account number included in the transfer data exists, by referring to the determination condition, determine whether the recipient name and the account name match or mismatch. Is also good.

    The deposit judging unit, based on the judgment condition, includes, among one or more character strings forming the payee name, all character strings that match the character string used for the match judgment by the operator. , It may be determined that the recipient name matches the account name.

  The transfer data may be non-payable electronic message information due to a name mismatch.

  The plurality of character strings forming the account name may be obtained by dividing the account name character string.

  According to another embodiment of the present invention, there is provided a transfer data acquisition unit for acquiring transfer data including at least a receiver's account number and a receiver's name, and a plurality of transfer data corresponding to the account number. An account information acquisition unit that acquires an account name consisting of a character string from a customer master; a payment determination unit that compares the recipient name and the account name to make a payment determination; and an operator that transfers the transfer data having a mismatched result of the comparison. And a storage processing unit that, among the plurality of character strings in the account name, information on the character string used for the match determination by the operator, stores the information in association with the account number as a determination condition. A payment judging device is provided.

  According to another embodiment of the present invention, there is provided a processor for acquiring transfer data including at least an account number and a payee name of a payee, and obtaining a plurality of transfer data corresponding to the account number. Acquiring the account name consisting of a character string from the customer master, comparing the payee name and the account name to make a payment determination, and allowing the operator to confirm the transfer data in which the result of the comparison is inconsistent. And storing the information of the character string used for the matching determination by the operator among the plurality of character strings in the account name in association with the account number as a determination condition. You.

  According to another embodiment of the present invention, there is provided a transfer data acquisition unit for acquiring transfer data including at least a payee's account number and a payee name; An account information acquisition unit that acquires an account name composed of a plurality of character strings from the customer master, a payment determination unit that compares the recipient name and the account name to determine the payment, and a transfer in which the result of the comparison does not match. A confirmation unit that allows an operator to confirm data, and a storage processing unit that stores information of a character string used for matching determination by the operator among a plurality of character strings in the account name in association with the account number as a determination condition. And a program for functioning as a program is provided.

  According to the present invention described above, it is possible to further improve the convenience of automatically determining whether or not a transfer in which a holder difference occurs has been accepted.

FIG. 1 is an explanatory diagram showing a configuration of a financial system according to an embodiment of the present invention. FIG. 3 is an explanatory diagram illustrating a configuration of a management server according to the embodiment of the present invention. It is a figure showing an example of the data composition of recipient master DB by an embodiment of the present invention. FIG. 7 is a diagram illustrating an example of an entry screen for an operator displayed on the client terminal according to the embodiment of the present invention. It is a figure showing an example of a character string comparison screen by an embodiment of the present invention. FIG. 7 is a diagram for explaining a name match determination and storage based on an operator's determination according to the embodiment of the present invention. It is a figure explaining an example (matching judgment) of the payment judgment using judgment mark information by an embodiment of the present invention. It is a figure explaining an example (mismatch determination) of payment judgment using judgment mark information by an embodiment of the present invention. FIG. 8 is a diagram for explaining a name match determination and storage based on an operator's determination according to the embodiment of the present invention. It is a figure explaining an example (matching judgment) of the payment judgment using judgment mark information by an embodiment of the present invention. It is a figure explaining an example (mismatch determination) of payment judgment using judgment mark information by an embodiment of the present invention. 5 is a flowchart illustrating an operation of the management server 22 according to the embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant description is omitted.

  Further, in this specification and the drawings, a plurality of components having substantially the same function and configuration may be distinguished from each other by adding different alphabets after the same reference numeral. However, unless it is necessary to particularly distinguish each of a plurality of components having substantially the same functional configuration, only the same reference numeral is given to each of the plurality of components.

<1. Overview of Financial System>
FIG. 1 is an explanatory diagram showing a configuration of a financial system according to an embodiment of the present invention. As shown in FIG. 1, the financial system according to the embodiment of the present invention includes a transfer management system 20 and a host bank 30.

(Transfer management system)
The transfer management system 20 includes a management server 22 and a client terminal 23. The management server 22 accumulates and processes the received various messages such as the inquiry message, the correction message, and the non-depositable message. The client terminal 23 is an information processing device that creates various messages according to an operation by an operator.

(Own host)
The own bank host 30 is a host computer of the own bank, and when operating as a destination side, transmits a transfer message to another transfer system (not shown) of the transfer destination via a dedicated network. On the other hand, when operating as the destination side, the own bank host 30 deposits funds into the designated account according to the transfer message received from the other bank system. That is, the owning host 30 can operate as both the destination side and the destination side. Note that FIG. 1 illustrates a case where the owning host 30 receives a transfer message from the transfer destination store 40 via the dedicated network 12 and operates as the destination side. The transfer destination store 40 may be included in the other bank system.

(Operation overview)
The self-host host 30 considers the difference between the recipient name and the receiver account name corresponding to the account number included in the transfer message transmitted from the transfer destination store 40 when there is a difference between the receiver name and the receiver account name corresponding to the account number included in the transfer message. The non-depositable telegram is transmitted to the management server 22 of the transfer management system 20.

  In the transfer, it is necessary that the name of the payee and the name of the payee account match, but even if they do not match, the transfer by the operator and the account attributes (salary income If necessary items (first and last name, corporate name, representative name, etc.) according to the person, corporation, personal store, etc. match, payment can be made.

  Accordingly, the management server 22 distributes the non-depositable telegram to the client terminal 23, and in the client terminal 23, the operator reads the telegram in accordance with the business rules or confirms necessary items according to the account attribute, and transmits the received account to the recipient account. A deposit judgment is performed. When it is determined that payment is possible, the management server 22 creates a payment message for the payee account and transmits the message to the host 30.

  Conventionally, such confirmation of necessary items according to the account attribute determined by the operator has been performed every time a non-depositable electronic message to the payee account is generated.

  The embodiment of the present invention is an invention created with a focus on the above circumstances, and the management server 22 according to the embodiment of the present invention stores the information of the judgment by the operator, and stores the information in the recipient account next and subsequent times. It is possible to further improve the convenience of the automatic determination of whether or not the transfer in which the transfer between the holders has occurred can be made.

<2. Configuration of Management Server>
FIG. 2 is an explanatory diagram showing the configuration of the management server 22 according to the embodiment of the present invention. As shown in FIG. 2, the management server 22 according to the embodiment of the present invention includes a message receiving unit 250, a non-depositable message DB 252 (database), a recipient account information acquisition unit 254, a recipient master (customer master) DB 256, and a deposit It has a determination unit 258, an operator confirmation unit 260, a determination condition storage processing unit 262, a message editing unit 264, and a message transmission unit 266. These message receiving unit 250, non-depositable message DB 252, recipient account information acquiring unit 254, recipient master DB 256, deposit judging unit 258, operator confirming unit 260, judgment condition storage processing unit 262, message editing unit 264, and message transmitting unit Functions such as 266 can be realized by cooperation between hardware and software such as a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), and a communication device.

  The telegram receiving unit 250 receives the non-depositable telegram from the self-run host 30 and stores it in the non-depositable telegram DB 252. The recipient account information acquisition unit 254 retrieves one non-depositable telegram from the non-depositable telegram DB 252 and, if the non-depositable reason set in the non-depositable telegram is different from the recipient account name, stores the store name, subject, account number, and the like. The account master information of the recipient is retrieved from the recipient master DB 256 using the key.

  Here, FIG. 3 shows an example of the data configuration of the recipient master DB according to the present embodiment. As shown in FIG. 3, the recipient master DB 256 includes, as account master information of the recipient, recipient account information (store name, account), recipient name information, and match determination target mark information according to the present embodiment described later. Is held. The matching judgment mark information is obtained by dividing a character string in the name of the recipient by one or more character strings obtained by dividing the character string by a predetermined delimiter (for example, space, period, comma, colon, semicolon, parenthesis opening, parenthesis closing, etc.). Each of the pieces of information is information (initial value “0”, and “1” when the operator uses the determination) indicating whether or not the operator has used for the determination of the name match. In the present embodiment, the information of the character string used by the operator to determine the name match can be stored in the recipient master DB 256 by the determination condition storage processing unit 262 described later.

  The payment determination unit 258 performs a processing of determining whether payment is possible based on the acquired account master information of the payee. More specifically, when the name match determination by the operator is already recorded as the determination mark information, the payment determination unit 258 determines whether the required character string in the recipient name of the transfer message matches. It is possible to automatically determine whether or not payment can be made based on the determination (name match determination by name comparison). In the present embodiment, the determination of the name match based on the determination of the operator is recorded as the determination mark information (match determination condition), and is thus used for the automatic determination of the name match of the same name account in the next and subsequent times. This makes it possible to improve the convenience of the deposit determination system.

  On the other hand, if the name match has not yet been determined by the operator's determination and the determination mark information has not been recorded, the operator confirmation unit 260 distributes a non-depositable message to the client terminal 23.

Here, FIG. 4 shows an example of an entry screen for the operator displayed on the client terminal 23. The entry screen 231 of FIG. 4 displays non-depositable telegram information, host inquiry results (ledger inquiry, inquiry results) of the recipient account, answer / request matching entry, and the like. The ledger inquiry screen shows the account attributes (salary earner, corporation, personal store, etc.) of the payee account, and the inquiry result screen shows the reason why payment cannot be made. The screen example shown in FIG. 4 is an example, and the screen configuration according to the present embodiment is not limited to this.

  If the reason for the inability to deposit is the recipient account name difference, the operator selects the "confirm recipient name" button 235 on the screen to display a screen for character string comparison under the name. FIG. 5 shows an example of a character string comparison screen according to the present embodiment.

  As shown in FIG. 5, the character string comparison screen 238 displays a character string obtained by dividing the recipient name of the non-depositable message (“the recipient name of the transfer message”) by a delimiter, and divides the name of the recipient account by the delimiter. Includes the display of the changed character string. Note that the screen example shown in FIG. 5 is an example, and the screen configuration according to the present embodiment is not limited to this.

  The operator refers to the account attribute indicated in the host inquiry result of the recipient account, and, based on the account attribute and business rules, the items to be confirmed (corporate name, representative, first name, last name, etc.) are the character string of the recipient name in the transfer message. And that they match.

  In the business rules, items to be confirmed in the name match determination according to the account attributes are defined, and it is assumed that the operator has grasped the business rules. In addition, the information of the office regulations may be displayed on an entry screen or a character string comparison screen as needed, or may be displayed in response to an operation of an operator.

  As an example of the business rules, for example, if the account attribute is “corporate”, “corporate name” only needs to match, and if “corporate personality” matches, the position is ignored (ie, (Either of the previous share or the previous share). Therefore, for example, if the name of the president and the person in charge is described in addition to the `` corporate name '' and `` corporate name '' in the recipient name of the transfer message, and the names of the If the character strings of "corporate name" and "corporate personality" match the name of the payee account, it is determined that payment is possible.

  If all the items to be confirmed match, the operator checks the judgment mark of the corresponding character string in the name of the payee account, and selects the “register” button. In addition, the operator selects a process of “payment” as an entry result on the entry screen 231 and registers it in the management server 22.

  On the other hand, if there are items that do not match, the operator selects the “return” button on the character string comparison screen 238, and performs “query” or “return” as an entry result on the entry screen 231. A selection is made and registered in the management server 22.

  The determination condition storage processing unit 262 performs a process of storing information of the determination by the operator in the recipient master DB 256. Specifically, the determination condition storage processing unit 262 stores the information of the character string used for the account name match determination by the operator, that is, the character string whose check mark is checked on the character string comparison screen 238 shown in FIG. (Match determination target mark information) is stored in the recipient master DB 256 as a name match determination condition of the account name.

  The message editing unit 264 edits the message in accordance with the result of the determination by the deposit determination unit 258 or the result of the operator confirmation (entry result) by the operator confirmation unit 260, and transmits the message to the host bank 30 by the message transmission unit 266. Specifically, the message editing unit 264 edits the received message when the determination result or the entry result is “payment”, and edits the inquiry message or the replacement message when “inquiry” or “return”.

<3. Specific example>
As described above, the management server 22 according to the present embodiment records the information of the account name match determination based on the operator's determination, and uses the information for the automatic determination of the same account name in the next and subsequent times. It is possible to further improve the convenience of the automatic determination of whether or not the transfer can be paid.

  A description will be given of the recording of the information of the account name match determination based on the determination of the operator and the use of the account name in the automatic determination of the account name from the next time onward, together with specific business rules.

(When the account attribute is "Individual store")
First, a case where the account attribute of the recipient's account is “individual store” will be described with reference to FIGS.

  FIG. 6 is a diagram for explaining the name match determination and storage based on the operator's determination according to the present embodiment. As shown in the upper part of FIG. 6, for example, when the recipient name of the transfer message is “Nara Shikao” and the recipient account name is “Narashoten Nara Shikao”, a non-depositable telegram due to the name mismatch is transmitted from the host 30. You.

  As a result of querying the account, it was found that the account attribute was "individual store", and the operator determined that the representative name matches in accordance with the business rule "in the case of a private store, if the representative matches, payment is possible." It is determined whether or not. Specifically, as shown in the middle part of FIG. 6, when the character strings of the representative names “Nara” and “Shikao” respectively match, the operator determines that the names match and registers “payment”.

  At this time, the operator inputs in the client terminal 23 which character string was used to determine a match (registration of a determination mark). The management server 22 records the judgment information input by the operator in the recipient master DB 256 as account name information. Specifically, as shown in the lower part of FIG. 6, the initial value “0” is set for each account name character string separated by a delimiter, but the value of the character string used for determination by the operator is , "1". Here, of the account holder character strings “Narashoten”, “Nara”, and “Shikao”, the value of the determination mark of “Nara” and “Shikao” is “1”.

  Subsequently, a case where the determination information of the operator thus registered is used at the next determination of the account will be described with reference to FIGS.

  FIG. 7 is a view for explaining an example (match determination) of the payment determination using the determination mark information according to the present embodiment. As shown in the upper part of FIG. 7, for example, when the recipient name of the transfer message is “Nara Shikao”, the deposit determination unit 258 determines only the character string with the determination mark (“Nara” “Shikao”) in the name of the recipient account. ") Is compared with the recipient name (" Nara "or" Shikao ") of the transfer message. In this case, since all the compared character strings match, the payment determination unit 258 determines “payment” as shown in the lower part of FIG.

  On the other hand, as shown in the upper part of FIG. 8, for example, when the recipient name of the transfer message is “Narashoten”, the deposit determination unit 258 determines only the character string with the determination mark (“Nara” "Shikao") is compared with the recipient name ("Narashoten") of the transfer message. In this case, since the compared character strings do not match, the deposit determination unit 258 determines “inquiry” or “return” as shown in the lower part of FIG.

(When the account attribute is "corporate")
Next, a case where the account attribute of the recipient's account is “corporate” will be described with reference to FIGS. 9 to 11.

  FIG. 9 is a diagram for explaining the name match determination and storage based on the operator's determination according to the present embodiment. As shown in the upper part of FIG. 9, for example, when the recipient name of the transfer message is “(ka) Nihon Shiyouji Aigiyoubu Tanaka” and the recipient account name is “Nihon Shiyouji (Kadaihiyo Yamada Tarou)”, the transfer from the host 30 due to the name mismatch. An impossible message is sent.

  As a result of querying the account, it was found that the account attribute was "corporate." Therefore, the operator stipulated that the business rule "In the case of a corporation, payment is possible if the corporate name matches, and the position is ignored if the corporate personality is the same. (The same for the subsequent shares and the previous shares) ", it is determined whether the required items (corporate name, legal personality) are the same. Specifically, as shown in the middle part of FIG. 9, when the character strings of the representative names “ka” and “Japanese syrup” respectively match, the operator determines that the names match and registers “payment”.

  At this time, the operator inputs in the client terminal 23 which character string was used to determine a match (registration of a determination mark). The management server 22 records the judgment information input by the operator in the recipient master DB 256 as account name information. Specifically, as shown in the lower part of FIG. 9, an initial value “0” is set for each account name character string separated by a delimiter, but the value of the character string used for determination by the operator is , "1". Here, among the account holder character strings “Nihon Shiyouji” “Ka”, “Daihyo”, “Yamada” and “Taro”, the value of the judgment mark of “Nihon Shiyouji” and “Ka” is “1”.

  Subsequently, a case where the determination information of the operator thus registered is used at the next determination of the account will be described with reference to FIGS.

  FIG. 10 is a diagram illustrating an example (match determination) of a payment determination using the determination mark information according to the present embodiment. As shown in the upper part of FIG. 10, for example, when the recipient name of the transfer message is “Nihon Shiyouji (ka)”, the deposit determination unit 258 determines only the character string with the determination mark in the receiver account name (“Nihon Shiyouji” “ ) Is compared with the recipient name of the remittance message (“Nippon Shinyoji” “K”). In this case, since all of the compared character strings match, the depositing determination unit 258 determines, as shown in the lower part of FIG. The determination of “payment” is performed.

  On the other hand, as shown in the upper part of FIG. 11, for example, when the recipient name of the transfer message is “Nihon Shiyouji Daihyo Yamada Taro”, the deposit determination unit 258 determines only the character string with the determination mark in the name of the recipient account (“ Compare the name of the recipient of the remittance message (“Nippon Shiyouji” and “Kai”) with the recipient of the transfer message (“Nihon Shiyouji”, “Daihyo”, “Yamada” and “Taro”). In this case, since the compared character strings do not match (there is no “ka” indicating the corporate personality), the payment determination unit 258 determines “inquiry” or “return” as shown in the lower part of FIG.

<4. Operation Processing>
The configuration of the management server 22 according to the embodiment of the present invention has been described above. Subsequently, the operation of the management server 22 according to the embodiment of the present invention will be summarized with reference to FIG.

  FIG. 12 is a flowchart showing the operation of the management server 22 according to the embodiment of the present invention. As shown in FIG. 12, first, the message receiving unit 250 receives, from the own bank host 30, a deposit-impossible message that has become unreceivable due to a name difference (S103).

  Next, the telegram receiving unit 250 stores the non-depositable telegram in the non-depositable telegram DB 252 (S106).

  Next, the recipient account information acquisition unit 254 acquires one non-depositable telegram from the non-depositable telegram DB 252 (S109), and if the reason for the non-depositable is a difference in the name of the recipient account (S112 / Yes), the account of the recipient is acquired. Master information is retrieved from the recipient master DB 256 (S115).

  Next, when the account master information of the recipient is registered (S118 / Yes), the payment determination unit 258 performs a payment determination (S121). Specifically, the payment determination unit 258 refers to the determination mark included in the account master information and performs a match determination of the account name as the payment determination.

  When the payment determination unit 258 determines that there is a mismatch (no payment) (S124 / No), or when the account master information of the recipient (more specifically, the determination mark) has not been registered yet (S118 / No), the operator confirmation unit 260 distributes the non-depositable telegram to the client terminal 23 (S127).

  In addition, even when the reason for the non-payment is not the difference in the name of the payee account (S112 / No), the non-payable message is delivered to the client terminal 23 (S127). The reason why the payment cannot be made except for the difference in the name of the payee account includes, for example, "no payee account number". “No payee account number” may occur, for example, due to merging and abolition of the store on the payee side, and it is also assumed that the payment is determined by the operator with reference to the merging and abolition information of the store.

  Next, the result of the payment determination based on the operator's determination made at the client terminal 23 is acquired, and if the result is a match determination (S130 / match), the determination condition storage processing unit 262 stores the information of the character string used for the operator determination. The (determination condition) is recorded in the recipient master DB 256 (S133).

  Then, when the operator determines that there is a match, the telegram editing unit 264 edits the received telegram (S136), and the telegram transmitting unit 266 transmits the received telegram to the host bank 30 (S139).

  Also, when it is judged by the deposit judging unit 258 that they match (possible to deposit) (S124 / Yes), the incoming telegram is edited by the telegram editing unit 264 (S136), and the telegram is transmitted to the host 30 by the telegram transmitting unit 266. It is transmitted (S139).

  On the other hand, when the payment determination result determined by the operator is a mismatch determination (S130 / mismatch), the replacement or inquiry message is edited by the message editing unit 264 (S142), and the replacement or inquiry message is transmitted by the message transmission unit 266. (S145). The distribution or inquiry message can be transmitted to the transfer destination shop 40 via the host bank 30.

<5. Effect>
According to the embodiment of the present invention described above, various effects can be obtained.

  In the case of automatic determination of name match, it is necessary to interpret the meaning of the character string by a program in order to determine the items to be checked in the receiver's account name based on the account attribute, which is difficult. However, the management server 22 according to the embodiment of the present invention stores the character string used for the determination by the operator in the unit of the recipient account (by adding the determination mark), so that the transfer to the recipient account from the next time onward can be performed. Can check necessary items in consideration of account attributes based on business rules, and make a payment determination by applying a determination rule. This makes it possible to further improve the convenience of the automatic determination of whether or not the transfer in which the ownership difference occurs has been accepted.

<6. Supplement>
Although the preferred embodiments of the present invention have been described in detail with reference to the accompanying drawings, the present invention is not limited to such examples. It is obvious that those skilled in the art to which the present invention pertains can conceive various changes or modifications within the scope of the technical idea described in the claims. It is understood that these also belong to the technical scope of the present invention.

  For example, each step in the processing of the information processing system in this specification does not necessarily need to be processed in chronological order in the order described in the flowchart. For example, each step in the processing of the information processing system may be processed in an order different from the order described in the flowchart, or may be processed in parallel.

  Further, a computer program for causing hardware such as a CPU, a ROM, and a RAM built in the management server 22 to exhibit the same functions as those of the components of the management server 22 described above can also be created. Also, a storage medium storing the computer program is provided.

DESCRIPTION OF SYMBOLS 12 Dedicated network 20 Transfer management system 22 Management server 23 Client terminal 30 Own host 40 Transfer destination store 231 Entry screen 238 Character string comparison screen 250 Message receiving unit 252 Non-receivable message DB
254 Recipient account information acquisition unit 256 Recipient master DB
258 Deposit judgment unit 260 Operator confirmation unit 262 Judgment condition storage processing unit 264 Message editing unit 266 Message transmission unit

Claims (8)

A transfer data obtaining unit for obtaining transfer data including at least the payee's account number and the payee name;
An account information acquisition unit that acquires an account name consisting of a plurality of character strings corresponding to the account number from the customer master,
A payment determination unit that compares the receiver's name and the account name and determines payment,
A confirmation unit that allows the operator to confirm the transfer data in which the result of the comparison is inconsistent,
A plurality of character strings in the account name, a storage processing unit that stores information on character strings used for matching determination by the operator as a determination condition in association with the account number;
A payment determination system comprising: The deposit judgment is,
2. The method according to claim 1, wherein when the determination condition stored in association with the account number included in the transfer data exists, the determination unit refers to the determination condition and determines whether the recipient name matches the account name. Payment judgment system. The deposit determination unit,
Based on the determination condition, when one or more character strings forming the recipient name include all character strings that match the character string used for the match determination by the operator, the recipient name is 3. The payment determination system according to claim 2, wherein the system determines that the account name matches the account name.   The deposit determination system according to any one of claims 1 to 3, wherein the transfer data is non-receivable electronic message information due to a name mismatch.   The payment judging system according to claim 1, wherein the plurality of character strings forming the account name are obtained by dividing the account name character string. A transfer data obtaining unit for obtaining transfer data including at least the payee's account number and the payee name;
An account information acquisition unit that acquires an account name consisting of a plurality of character strings corresponding to the account number from the customer master,
A payment determination unit that compares the receiver's name and the account name and determines payment,
A confirmation unit that allows the operator to confirm the transfer data in which the result of the comparison is inconsistent,
A plurality of character strings in the account name, a storage processing unit that stores information on the character strings used for the match determination by the operator as a determination condition in association with the account number;
A payment judging device comprising: The processor
Obtaining transfer data including at least the payee's account number and payee name;
Acquiring the account name consisting of a plurality of character strings corresponding to the account number from the customer master,
Comparing the payee name and the account name to make a payment determination;
Causing the operator to confirm the transfer data in which the result of the comparison is inconsistent,
Among the plurality of character strings in the account name, information on the character string used for the match determination by the operator is stored in association with the account number as a determination condition,
And a deposit determination method. Computer
A transfer data obtaining unit for obtaining transfer data including at least the payee's account number and the payee name;
An account information acquisition unit that acquires an account name consisting of a plurality of character strings corresponding to the account number from the customer master,
A payment determination unit that compares the receiver's name and the account name and determines payment,
A confirmation unit that allows the operator to confirm the transfer data in which the result of the comparison is inconsistent,
A plurality of character strings in the account name, a storage processing unit that stores information on the character strings used for the match determination by the operator as a determination condition in association with the account number;
Program to function as

Images