JP4304161B2 - Transfer request processing method and transfer request processing program - Google Patents

Description

  The present invention relates to a system and method for processing a transfer request from a customer in a financial institution.

  In the transfer service of a financial institution, when making a transfer by a transfer request from a customer, if there is an error in the account number, recipient name, etc. in the transfer request, transfer to the specified transfer account Can not. In the event that transfer is not possible in a transfer where the bank account is another bank, an inquiry message is sent from the transfer financial institution (destination financial institution) to the transfer source financial institution (destination financial institution). . Conventionally, the transfer source financial institution that received the inquiry message has notified the transfer requester that the transfer is not possible by telephone or other means, and received an instruction from the requester to correct the transfer request or reorganize it. Execute the corresponding process.

On the other hand, a system for simplifying the procedure when transfer to a transfer request becomes impossible is also disclosed (see, for example, Patent Document 1). In the system described in Patent Document 1, regarding a transfer request from a subject of an automatic refund service, a refund process to a designated account is uniformly performed when the transfer is impossible. This eliminates the need for complicated processing such as making an inquiry to the transfer requestor each time a transfer is impossible, and correcting or reassembling based on a reply instruction from the transfer requester.
JP 2003-271824 A (page 4-6)

  However, when the transfer is impossible, the transfer requester often desires not only refund but also correction of the transfer destination. For this reason, the response (inquiry message management, contact processing, etc.) when receiving an inquiry message from another bank is complicated. The technology of Patent Document 1 simplifies the procedure for performing automatic refunds when transfer is not possible, and for efficiently performing the transfer procedure by correcting the transfer destination when transfer is not possible. It is not a thing.

  In addition, when performing transfer all at once like general transfer, a plurality of transfer failures may occur at one time. In this case, it is troublesome for the transfer requester to receive and respond to the request each time. Moreover, even if a transfer failure notification is received, it may be difficult for the transfer requester to promptly correct the correct bank account.

  The present invention has been made to solve the above-mentioned problems, and its purpose is to provide a transfer request response processing method and a transfer for efficiently performing a procedure when receiving a non-transferable inquiry message from a destination financial institution. It is to provide a request handling processing program.

The present invention includes a request category data storage means that records the request category and the correspondence category in association with each other, a correction history data storage means that records in association the impossible transfer destination account information and the correction transfer destination account information for each user, Standby reference time data storage means for recording data related to standby reference time for accumulating the inability to transfer for each user, time measuring means, and non-transfer notification reference number data storage for recording data relating to the non-transfer notice reference number for each user Means, a counter, and a management computer for handling a transfer request that cannot be transferred, and when the management computer receives a transfer impossible notification for the transfer request, it is included in the transfer request Based on the requested category, a corresponding category is identified using the requested category data storage means, and the received transaction is identified based on the corresponding category. The transfer destination of the transfer request for the impossible notification is searched using the correction history data storage unit, and the transfer destination that cannot be transferred for the user of the transfer request is recorded in the correction history data storage unit as the transfer destination account information. If it is, it obtains the corrected transfer destination account information corresponding to the non transfer destination account information, to create a confirmation request statement that displays this, for the user on this transfer impossible notice, time using the clock means While starting the measurement, during the waiting reference time for the user in this non-transfer notice, a confirmation request text based on the non-transfer notice received for this user is accumulated, and for each user identifier using the counter The number of transfers that cannot be transferred is counted, and the number of transfers that cannot be transferred exceeds the number of transfers that cannot be transferred within the waiting reference time, or When, it transmits the accumulated confirmed request sentence to the user, when receiving the check result from the user, and records the correction history on the basis of the confirmation result to the correction history data storage means.

  According to this, the correction transfer destination account information corresponding to the impossible transfer destination account information can be acquired based on the correction history, and the confirmation request text displaying the correction transfer destination account information can be created and provided to the user. For this reason, the user can instruct | indicate correction destination account information by confirming the correction transfer destination account information displayed on the confirmation request text, and notifying a confirmation result. In response to this instruction, the management computer can efficiently correct the transfer destination and perform the transfer process. Therefore, when a transfer request becomes impossible, it is possible to efficiently receive a transfer destination instruction from the user and perform a transfer process to the corrected transfer destination. On the other hand, when the transfer request becomes impossible, the user can efficiently instruct correction of the transfer destination using the confirmation request text displaying the corrected transfer destination account information.

  Further, according to the present invention, the management computer further receives a transfer impossible notification by further using standby reference time data storage means and time measuring means for recording data relating to a standby reference time for storing transfer impossible for each user. In this case, for the user regarding the non-transfer notice, time measurement is started using the time measuring means, and the non-transfer can be received for the user during the waiting reference time for the user in the non-transfer notice. The confirmation request text based on the notification is accumulated, and the accumulated confirmation request text is transmitted to the user after the waiting reference time has elapsed.

According to this, it is possible to collectively transmit confirmation request texts regarding the inability to transfer accumulated during the standby reference time for each user.
Further, according to the present invention, when the management computer receives a transfer impossible notification, further using a transfer impossible notification reference number data storage means and a counter for recording data related to the transfer impossible notification reference number for each user. , Further counting the number of transfer impossible for each user identifier using the counter, and when the transfer impossible number exceeds the transfer impossible notification reference number within the waiting reference time, a confirmation request sentence about the accumulated transfer impossible To the user to reset the counter.

  According to this, for each user, if the number of transfer impossible accumulated during the standby reference time exceeds the transfer impossible notification reference number, a confirmation request text is sent even if the standby reference time has not been reached. Can be sent together.

  Further, according to the present invention, the confirmation request message transmitted to the user includes a display code for specifying the transfer request, and the management computer includes a confirmation result in the confirmation request statement by the user. When the confirmation result message that has been entered is received, the display request included in the confirmation result message is read to identify the transfer request, and the correction history of the impossible bank account information related thereto is recorded in the correction history data storage means To do.

According to this, with respect to the confirmation result message in which the confirmation result is entered by the user, it is possible to efficiently specify the transfer request and record the correction history using the display code.
Further, according to the present invention, the management computer further receives a recombination message by further using a user account designation data storage unit that records the user identifier and the account identifier of the designated account of the user in association with each other. In this case, the transfer requester is specified based on the reorganization message, the transfer requester's specified account is specified using the user account specifying data storage means, and the transfer requester's specified account is stored in the transfer requester's specified account. Deposit the reversal amount based on the recombination message.

  According to this, by automatically depositing in the designated account of the transfer requester based on the return message, it is possible to efficiently refund the customer in the case of return.

  According to the present invention, it is possible to efficiently perform a procedure in the case of receiving a non-transferable inquiry message from a destination financial institution.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. The present embodiment will be described as a transfer request handling processing method and a transfer request handling processing program for efficiently performing a procedure when transfer to a transfer request addressed to another bank becomes impossible. In this embodiment, a case where a transfer request is made from an account of a financial institution A (destination financial institution) with a customer (transfer requester) as a user to an account of another financial institution B (destination financial institution) is described. To do.

  As shown in FIG. 1, a host computer (destination host computer 20) of a financial institution A (destination financial institution) and a host computer (destination host computer 60) of a financial institution B (destination financial institution) are all silver. They are connected to each other via a network system 70 such as a data communication system.

  The destination host computer 20 is connected to a recording data input device 41, an automated teller machine (ATM) 42, a data input terminal 43, and a scanner device 44 via a network in the financial institution A.

  The recording data input device 41 is an input device for inputting data recorded on a recording medium such as a magnetic tape (MT). Using this recording data input device 41, data recorded on a recording medium such as a magnetic tape submitted by a customer is input. A customer who makes a large amount of money transfer requests, such as a corporate customer, inputs data relating to the money transfer request on the customer side, records it on a recording medium such as a magnetic tape, and submits it to the financial institution A.

  The automatic teller machine 42 is installed in a store of the financial institution A or the like. When making a transfer request using the automatic teller machine 42, the customer goes to the store of the financial institution A and performs a transfer operation with the automatic teller machine 42.

  The data input terminal 43 and the scanner device 44 are installed in a store or data center of the financial institution A. The data input terminal 43 is a computer terminal used by a person in charge at a store of the financial institution A or an operator of the data center. This data input terminal 43 is used when a person in charge at a store or an operator of a data center makes an input based on a transfer request document submitted by a transfer requester. Then, the person in charge at the store or the operator of the data center uses the scanner device 44 to read the image data of the transfer request form. This image data is transferred to the destination host computer 20 and recorded in the image recognition data storage unit 37.

  The destination host computer 20 is further connected to an operator terminal 51. The operator terminal 51 is a computer terminal used by an operator of the financial institution A. The operator terminal 51 is used when the operator confirms the inquiry form. The operator uses the telephone terminal 52 provided in the financial institution A to make a telephone contact with the transfer requester for the transfer request inquiry form in which a telephone number other than the mobile phone number is registered as the client contact information. The telephone terminal 52 is connected to the customer telephone terminal 81 via the public line network 90. The customer telephone terminal 81 is a fixed telephone terminal used by a customer who is a transfer requester.

The destination host computer 20 is further connected to a customer mobile phone terminal 82 via a public line network 90 (including a public telephone network and a mobile phone network). The customer mobile phone terminal 82 is a mobile phone terminal used by a customer who is a transfer requester. The destination host computer 20 is connected to the customer facsimile machine 83 via the public network 90. The customer facsimile machine 83 is a facsimile machine used by a customer who is a transfer requester.

The destination host computer 20 includes a management computer 21.
The management computer 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing to be described later. By executing the program for this purpose, the management computer 21 functions as a correspondence classification specifying unit, a transfer destination search unit, a confirmation request unit, a confirmation result registration unit, and the like.

  When the correspondence classification specifying unit receives a transfer impossible notification (inquiry message) for the transfer request, the correspondence classification identification unit uses the transmission classification data storage unit 31 to identify the correspondence classification based on the transmission classification included in the inquiry message.

Based on the correspondence classification, the transfer destination search means searches for the transfer destination included in the received transfer request that cannot be transferred, using the correction history data storage unit 34.
When the account information of the bank account that cannot be transferred is recorded in the correction history data storage unit 34 as the bank account that cannot be transferred, the confirmation requesting unit acquires the account information of the bank account corresponding to this bank transfer, Create a confirmation request text (inquiry form) to be displayed and send it to the user.

When the confirmation result registration unit receives the confirmation result (answer document) from the user, the confirmation result registration unit records the modification history in the modification history data storage unit 34 based on the reply document.
The management computer 21 includes a transmission category data storage unit 31 as a request category data storage unit, a customer data storage unit 32 as a user account designation data storage unit, a transfer request data storage unit 33, and a correction history as a correction history data storage unit. The data storage unit 34, the inquiry form data storage unit 35, the transmission condition data storage unit 36, and the image recognition data storage unit 37 are connected.

  As shown in FIG. 2, the transmission classification data storage unit 31 stores transmission classification data 310 relating to the transmission classification corresponding to the transmission location of the transfer request, the transfer medium that has received the transfer request, and the like. The transmission category data 310 is recorded when a corresponding category is determined for the transmission category. The transmission category data 310 includes data related to the transmission category and the correspondence category.

  Data for specifying a transmission category is recorded in the transmission category data area. Specifically, codes for specifying “MT / FD”, “data transmission”, “ATM”, “sales office transmission (manual key)”, “data entry (manual key)”, etc. as this transmission category Is provided.

  In the corresponding category data area, data relating to the corresponding category for this outgoing category is recorded. This correspondence category is a category for determining whether or not it is necessary to record a correction history relating to a transfer destination and whether or not a facsimile transmission of an inquiry form to a customer is necessary. In this embodiment, it is assumed that a correction history is recorded when an inquiry form is transmitted to a customer. Therefore, when “ATM” or the like is the transmission category, “No correction history recording is necessary” is recorded, and “Other than that, correction history recording is necessary” is recorded.

As shown in FIG. 3, customer data 320 is recorded in the customer data storage unit 32 for customers (customer companies, etc.) who have made a customer registration regarding the transfer request to the financial institution A. The customer data 320 is recorded based on registration information when customer registration is performed for such a customer. In the present embodiment, a customer identifier is assigned and customer data 320 is registered for a customer who makes a transfer request to a plurality of transfer destinations at once. The customer uses this customer identifier when making a transfer request. Customer data 320 includes customer identifier, customer name, customer address,
It includes data relating to telephone numbers, facsimile numbers and account identifiers.

In the customer identifier data area, data relating to an identifier for specifying a customer (customer company or the like) who performed customer registration related to the transfer request is recorded.
Data relating to the name or name of the customer is recorded in the customer name data area.

Data relating to the customer's address is recorded in the customer address data area.
In the telephone number data area, data relating to the customer's telephone number is recorded.
In the facsimile number data area, data relating to the customer's facsimile number is recorded.

  Data relating to the account identifier of the customer is recorded in the account identifier data area. In the present embodiment, the account identifier is composed of data relating to a financial institution name, a branch, a deposit type, and an account number.

  As shown in FIG. 4, transfer request data 330 is recorded in the transfer request data storage unit 33 for each transfer request. The transfer request data 330 is recorded based on the input data when a transfer request is received from the transfer requester. The transfer request data 330 includes data relating to a transmission number, a request date, a client name, a client customer identifier, a client contact address, a transfer type, a transfer amount, a bank account identifier, and a payee name.

  Data relating to the transmission number is recorded in the transmission number data area. This transmission number is assigned when a transfer request message is created based on the transfer request data 330, and is recorded when the transfer request message is created. In the present embodiment, the transmission number is composed of a code assigned in a specific code system for each transmission category, with a serial number assigned to one or more alphabets, numbers or katakana assigned corresponding to the transmission category. The

In the request date data area, data related to the request date of the transfer request is recorded.
In the client name data area, data relating to the client name of the transfer request is recorded.
Data on the client identifier of the client is recorded in the client customer identifier data area.

In the client contact data area, data relating to the telephone number of the client contact is recorded.
In the transfer type data area, data related to the transfer type is recorded. In the present embodiment, codes for specifying “MT / FD”, “data transmission”, “ATM”, “sales office transmission (manual key)”, “data entry (manual key)”, and the like as the transfer type are included. To be recorded. This transfer type corresponds to the transmission category of the transmission category data 310.

Data relating to the transfer amount is recorded in the transfer amount data area.
Data relating to an identifier for specifying a transfer destination account is recorded in the transfer account identifier data area. In the present embodiment, the transfer destination account identifier is composed of a financial institution name, a branch, a deposit type, and an account number for the transfer destination account.

Data related to the name or name of the recipient is recorded in the recipient name data area.
As shown in FIG. 5, the correction history data storage unit 34 stores correction history data for each correction of transfer destination account information (account identifier and payee name) based on a reply to the inquiry form returned from the customer regarding the generated transfer failure. 340 is recorded. The correction history data 340 is recorded when a reply to the inquiry form is returned from the customer regarding the transfer failure that has occurred. The correction history data 340 includes data relating to a customer identifier, an impossible transfer destination, and a correction transfer destination.

Data relating to the customer identifier is recorded in the customer identifier data area.
In the impossible transfer destination data area, data relating to transfer destination account information (account identifier and recipient name) that cannot be transferred is recorded. In this embodiment, the account identifier of the bank account that cannot be transferred is composed of the name of the financial institution, branch, deposit type, and account number of the bank account that cannot be transferred.

  In the corrected transfer destination data area, data relating to the corrected transfer destination account information (account identifier and payee name) is recorded. In the present embodiment, the account identifier of the corrected transfer destination is composed of the financial institution name, branch, deposit type, and account number of the corrected transfer destination account.

  In the inquiry form data storage unit 35, as shown in FIG. 6, inquiry form data 351 for the created inquiry form is recorded. In addition, the inquiry form management data 350 is recorded for each transfer request that cannot be made and needs to be inquired using the inquiry form. The inquiry form management data 350 is recorded when a transfer failure occurs and an inquiry using an inquiry form is necessary. The inquiry form management data 350 includes data relating to an inquiry number, a transfer impossible time, a client customer identifier, and a status.

  In the reference number data area, data related to a reference number, which is an identifier for inquiring the transfer request data 330 when transfer is impossible, is recorded. In this embodiment, the inquiry number included in the inquiry message received from the destination host computer 60 is recorded as the inquiry number.

In the transfer impossible time data area, data related to the date and time when transfer failure occurred is recorded.
Data on the client identifier of the client is recorded in the client customer identifier data area.

  In the status data area, data relating to the status when the inquiry form is transmitted to the customer, the reply is received, and the transfer is made to the correction transfer destination account is recorded. Specifically, flags for specifying “accumulating”, “inquiry card transmission”, “answer reception”, “change request transmission”, and “combination request transmission” are recorded. “Accumulating” is recorded when an inquiry form that has not yet been transmitted to the customer is being accumulated. “Send inquiry form” is recorded when this inquiry form is sent to the customer facsimile machine 83. “Reply to reply” is recorded when a reply to the inquiry form is received from the customer facsimile machine 83. “Change request transmission” is recorded when a response message regarding the transfer to the corrected transfer account based on the response is transmitted to the destination host computer 60. “Send back request” is recorded when a reply message related to a back request based on the reply is sent to the destination host computer 60.

The inquiry form data 351 is data for outputting an inquiry form. This inquiry form data 351 is generated and stored according to the processing, and is deleted when facsimile transmission is performed.
In the transmission condition data storage unit 36, transmission condition data relating to conditions for transmitting the inquiry form to the transfer requester is recorded. In the present embodiment, as the transmission condition data, the data related to the customer identifier of the customer (transfer requester) to be immediately notified to the transfer requester when the reference form data is created without accumulating the reference form data. Record. In this embodiment, as will be described later, in the case of a transfer request by a transfer requester whose customer identifier is recorded in the transmission condition data storage unit 36, the inquiry form data is not accumulated and the inquiry form data is not stored. When a request is made, a confirmation request text (inquiry form) is immediately sent to the transfer requester. On the other hand, when the customer identifier is not recorded in the transmission condition data storage unit 36, the inquiry form data is accumulated, and inquiry forms relating to the inability to transfer generated within a predetermined period are collectively transmitted to the transfer requester.

The image recognition data storage unit 37 stores image data (image data) of a transfer request document read by the scanner device 44 installed in a store or data center of the financial institution A. In the present embodiment, the image data of the transfer request document is recorded in association with the receipt number of the transfer request document. This reception number is included in the transmission number.

  Next, a procedure of processing performed when transfer to a transfer request addressed to another bank becomes impossible using the above system will be described with reference to FIGS. Here, the processing when receiving the inquiry message (FIGS. 7 to 9), the transmission management processing (FIG. 10), and the reply document receiving processing (FIG. 11) will be described separately.

(Inquiry message processing)
The destination host computer 20 of the financial institution A that has received the transfer request from the customer records the transfer request data 330 in the transfer request data storage unit 33 and creates a transfer request message for the transfer process based on the transfer request data 330. . Then, the destination host computer 20 sends the created transfer request message to the network system 70. The transfer request message sent to the network system 70 is transmitted to the destination host computer 60 of the financial institution B based on the identification information of the destination financial institution B included in the transfer request message.

  The destination host computer 60 that has received the transfer request message determines whether or not transfer is possible based on the transfer request message. Specifically, it is determined whether or not there is an account with the transfer destination account number specified in the transfer request message, and whether or not the account name matches the recipient name. If the transfer is possible, a deposit process to the transfer account is executed.

  On the other hand, if the transfer is impossible, the destination host computer 60 creates an inquiry message for notifying that transfer is impossible, and sends it to the network system 70. The inquiry message sent to the network system 70 is transmitted to the destination host computer 20 of the financial institution A based on the identification information of the destination financial institution A included in the inquiry message. This inquiry message includes data relating to the reference number set based on the transmission number and the bank account identifier that cannot be transferred.

Processing when the inquiry message is received in this manner will be described with reference to FIGS.
As shown in FIG. 7, the management computer 21 of the destination host computer 20 that has received the inquiry message first specifies the transmission classification based on the transmission number in the inquiry message, thereby specifying the transfer request data creation location and the like. (Step S1-1). Specifically, the transmission classification corresponding to the transfer request data creation location or the like is specified according to the numbering system of the transmission number.

  Then, the management computer 21 determines whether confirmation of the keystroke content is necessary (step S1-2). The determination as to whether or not the keystroke content needs to be confirmed is made based on the specified transmission category. Here, if the transmission category is “sales office transmission (manual key)”, “data entry (manual key)” or the like, it is determined that confirmation of the key content is necessary. That is, when data is input based on the transfer request form entered by the customer, it is determined that the keystroke content needs to be confirmed.

  If it is necessary to confirm the keystroke content (YES in step S1-2), processing for confirming the keystroke content is performed. This process will be described with reference to FIG. As shown in FIG. 8, the management computer 21 first collates the data included in the received inquiry message with the image recognition data of the undirectable transfer request form (step S2-1). Specifically, first, the reception number is extracted from the reference number included in the inquiry message, and based on this, the image data recorded in the image recognition data storage unit 37 is searched. Then, the retrieved image data is read by an OCR (Optical Character Reader) means, and a transfer destination account identifier and a recipient in the image data are specified. Then, the bank account identifier and payee are compared with the bank account identifier and payee included in the inquiry message.

  Here, when the image recognition data cannot be automatically confirmed (NO in step S2-2), the management computer 21 instructs the operator to visually confirm (step S2-3). Specifically, a collation screen for instructing visual confirmation is displayed on the operator terminal 51. On this collation screen, the image recognition data and the contents of the inquiry message are displayed. On the operator terminal 51, the operator collates the transfer destination (account identifier and payee) in the image recognition data with the transfer destination included in the inquiry message. The collation screen is provided with a match button used when matching, a correction input unit used when performing correction input, and a correction registration button used when registering with the corrected input content. When the transfer destination in the image recognition data matches the transfer destination included in the inquiry message, the operator selects the match button. On the other hand, if they do not match, the operator performs correction input of the transfer destination (account identifier or recipient) that does not match the image recognition data, and performs correction registration using the correction registration button. When the match button is selected, the management computer 21 records the match flag in association with the inquiry message. On the other hand, when correction input of the transfer destination is performed, the transfer destination account identifier or the payee that has been corrected and input is recorded in association with the inquiry message. If automatic confirmation is possible (YES in step S2-2), the process proceeds to step S2-4.

  Then, the management computer 21 determines whether or not there is a keystroke mistake (step S2-4). Specifically, if automatic confirmation is possible, whether there is a keystroke error by checking whether the transfer destination account identifier in the image recognition data matches the transfer destination account identifier included in the inquiry message. Determine. In this case, if there is no match, there is a keystroke mistake. On the other hand, if automatic confirmation is impossible, it is determined whether or not there is a keystroke error based on data input through visual confirmation by the operator. Here, when a match flag is recorded in association with the inquiry message, there is no keystroke mistake. On the other hand, if the bank account identifier or payee that has been corrected and entered in association with the inquiry message is recorded, there is a keystroke error.

  If there is a keystroke error (YES in step S2-4), the management computer 21 transmits a response message for the change request to the destination host computer 60 (step S2-5). Specifically, first, the account identifier and payee of the corrected transfer destination are specified. Here, the financial institution name, branch, deposit type, and account number of the corrected transfer destination are used as the account identifier of the corrected transfer destination. Then, a reply message including a reference number included in the inquiry message, a correction transfer destination (account identifier and payee name), a change request flag, and identification information of the transmission destination financial institution B is sent to the network system 70. The reply message sent to the network system 70 is transmitted to the destination host computer 60 of the financial institution B based on the identification information of the destination financial institution B.

On the other hand, if there is no keystroke mistake (NO in step S2-4), the process returns to step S1-3 of the flow shown in FIG.
If NO in step S2-4 or confirmation of the keystroke content is not required (NO in step S1-2), the inquiry form data for the transfer requester is created based on the reference number (step S1-3). ). Specifically, first, the transmission number in the transfer request data storage unit 33 is searched using the reference number, and the transfer request data 330 of the searched transmission number is extracted. Then, an inquiry form is created in which the request date, requester, client customer identifier, client contact information, transfer type, transfer amount, transfer-destination account identifier and payee name included in the transfer request data 330 are set. The inquiry form data 351 is recorded in the inquiry form data storage unit 35. This inquiry form is provided with a check field for a change request or reorganization request that can be entered in the form of a mark sheet, a check field for whether or not there is a desire to change to a correction candidate transfer destination, and a correction transfer destination input field.

Next, the management computer 21 checks whether it is a request using ATM (step S1-4). First, based on the transfer type included in the transfer request data 330, the call classification in the call classification data storage unit 31 is searched. Then, a corresponding category corresponding to the retrieved outgoing category is extracted, and this corresponding category (“correction history recording required” or “correction history recording unnecessary”) is determined.

  When the correspondence classification is “no correction history recording required” (YES in step S1-4), the management computer 21 checks whether the client contact address included in the transfer request data 330 is a mobile phone number (step S1-8). Specifically, when the client contact address starts with a specific station number (for example, “090”) indicating a mobile phone number, it is determined that the client contact address is a mobile phone number.

  If the client contact number is a mobile phone number (YES in step S1-8), the management computer 21 automatically sends a message regarding a store visit request (step S1-9). Specifically, the management computer 21 automatically sends a calling signal to the mobile phone number of the customer mobile phone terminal 82 designated as the client contact address by the automatic call means of the destination host computer 20. When the transfer requester responds to the incoming call to the customer mobile phone terminal 82, the destination host computer 20 outputs a message requesting to visit the store.

  On the other hand, if the client contact number is not a mobile phone number (NO in step S1-8), the management computer 21 instructs a manned call (step S1-10). Specifically, the management computer 21 causes the operator terminal 51 to display a manned call instruction screen including the contents of the inquiry message and the transfer request data 330. The operator makes a call using the telephone terminal 52 to the telephone number of the client contact address included in the transfer request data 330 displayed on the manned call instruction screen. When the transfer requester or the like responds to the incoming call to the customer telephone terminal 81, the operator confirms the identity of the transfer requester and requests the store visit.

  On the other hand, if the correspondence category is “requires correction history recording” (NO in step S1-4), the management computer 21 searches for past undirectable response results (step S1-5). Specifically, the customer identifier of the correction history data 340 is searched by the client customer identifier included in the transfer request data 330.

  Here, when the correction history data 340 of the customer identifier to be searched is recorded in the correction history data storage unit 34 and there is a past unanswerable answer record (in the case of YES in step S1-6), the management computer 21 Then, a statement to request correction of the transfer request form data is attached to the inquiry form data (step S1-7). Specifically, the correction transfer destination (account identifier and recipient name) of the searched correction history data 340 is described in an inquiry form created as a correction candidate. Then, the inquiry form data 351 for this inquiry form is updated and recorded in the inquiry form data storage unit 35. On the other hand, when there is no past unanswerable answer record (NO in step S1-6), the process of step S1-7 is skipped.

  Next, as shown in FIG. 9, the management computer 21 checks whether there is a transmission condition (step S3-1). Specifically, the customer identifier in the transmission condition data storage unit 36 is searched by the requester customer identifier in the transfer request data 330. In the present embodiment, as described above, the customer identifier is recorded in the transmission condition data storage unit 36 when the inquiry form is transmitted every time without transmitting the inquiry form data as the transmission condition.

  Here, when the customer identifier to be searched is recorded and there is a transmission condition (YES in step S3-1), the management computer 21 attaches a barcode indicating the reference number to the inquiry slip (step S3). -2). Specifically, the reference number is converted into a barcode by the barcode conversion means and attached to the inquiry form, and the inquiry form data 351 relating to this inquiry form is updated and recorded in the inquiry form data storage unit 35.

  Then, the management computer 21 transmits the inquiry form to the transfer requester's registered facsimile number (step S3-3). Specifically, the management computer 21 first displays on the operator terminal 51 an inquiry form transmission screen for displaying the inquiry form data 351. This inquiry form transmission screen is provided with a transmission button and a cancel button. The send button is a button used when the inquiry form is sent by facsimile. The cancel button is a button used when canceling the transmission of the inquiry form. When the operator visually confirms the inquiry form displayed on the operator terminal 51 and determines that the inquiry form may be transmitted to the customer, the operator makes a transmission request using the transmission button.

  When a transmission request is made, the management computer 21 extracts a facsimile number from the customer data storage unit 32 based on the customer identifier. Then, the facsimile sending means converts the inquiry form data into a TIFF type file for facsimile transmission, and transmits it to this facsimile number. When the inquiry form is transmitted by facsimile, the management computer 21 deletes the corresponding inquiry form data 351 from the inquiry form data storage unit 35.

This inquiry form is received and output by the customer facsimile apparatus 83 of the transfer requester.
And the management computer 21 performs transmission recording about this inquiry tag (step S3-4). Specifically, “inquiry form transmission” is recorded as the status of the inquiry form management data 350 corresponding to this inquiry form.

  On the other hand, when there is no transmission condition, that is, when the customer identifier is not recorded in the transmission condition data storage unit 36 (NO in step S3-1), the management computer 21 accumulates the inquiry form data (step S3). -5). Specifically, the inquiry form data 351 is accumulated in the inquiry form data storage unit 35. Further, the inquiry form management data 350 corresponding to the inquiry form data 351 is recorded in the inquiry form data storage unit 35. Here, “accumulating” is recorded as the status.

(Transmission management process)
Next, a transmission management process for transmitting an inquiry form based on the accumulated inquiry form data will be described with reference to FIG.

  As shown in FIG. 10, the management computer 21 first searches the stored inquiry forms (step S4-1). In this embodiment, an inquiry form that has been accumulated for 20 minutes is searched. Specifically, first, the inquiry form management data 350 whose status is “Accumulating” is specified. Next, a time 20 minutes before the current system time is calculated. Then, from the identified inquiry form management data 350, the inquiry form management data 350 whose transfer impossible time is earlier than this time is searched.

  If there is a transfer request that has passed 20 minutes (YES in step S4-2), the management computer 21 extracts an inquiry form for the same transfer requester (step S4-3). Specifically, the inquiry form management data 350 having the same client identifier as that included in the inquiry form management data 350 of the inquiry form after 20 minutes, and the status is “Accumulating” Extracted from the inquiry form data storage unit 35. Further, the inquiry form data 351 is specified based on the extracted inquiry number of the inquiry form management data 350.

  Then, the management computer 21 attaches a barcode indicating the reference number to the inquiry form (step S4-4). Specifically, the extracted inquiry form data 351 is converted into a barcode by the barcode conversion means and attached to the inquiry form, and the inquiry form data 351 of the inquiry form is stored in the inquiry form data storage unit 35. Record update.

  Then, the management computer 21 transmits the inquiry form to the transfer destination facsimile number of the transfer requester (step S4-5). Specifically, the same processing as step S3-3 is performed on the extracted inquiry form data 351. This inquiry form is received and output by the customer facsimile apparatus 83 of the transfer requester. And the management computer 21 performs transmission recording about this inquiry tag (step S4-6). Specifically, “inquiry form transmission” is recorded as the status of the inquiry form management data 350 corresponding to this inquiry form.

On the other hand, if there is no request after 20 minutes have passed (NO in step S4-2), this transmission management process is terminated.
(Answer receipt process)
The transfer requester who has received the inquiry form by the customer facsimile apparatus 83 enters a check in the check column for either the change request or the reorganization request in the inquiry form. Here, in the case of a change request, if a correction transfer destination based on a past undeliverable response record is described in the inquiry form, the transfer requester confirms whether or not the transfer request can be changed to this correction candidate transfer destination. Then, put a check in one of the check boxes for whether or not there is a change request. If the change cannot be made, the account identifier and the name of the payee are entered in the entry field of the payee in the inquiry form. In the case of a change request, if there is no correction transfer destination based on the past undeliverable response record in the inquiry form, the correction transfer destination account identifier and recipient name are entered in the correction transfer entry field of the inquiry form. Fill out. Then, the transfer requester transmits an inquiry form (answer) filled with this answer to the designated facsimile number using the customer facsimile machine 83. In the present embodiment, the designated facsimile number is a facsimile number assigned to the facsimile means of the destination host computer 20. The data received by the destination host computer 20 by this facsimile number is recorded in a predetermined storage unit of the destination host computer 20.

A process (response document reception process) when a response document is received will be described with reference to FIG.
As shown in FIG. 11, the management computer 21 recognizes the barcode attached to the received answer sheet and identifies the reference number (step S5-1). More specifically, the barcode reading means reads the barcode in the received answer sheet data, and specifies the reference number by this barcode. Then, the management computer 21 searches the inquiry form data storage unit 35 based on this inquiry number, and records “answer received” as the status of the retrieved inquiry form management data 350.

  Next, the management computer 21 determines a change request or a reorganization request based on the check entered in the check column of the answer sheet (step S5-2). Specifically, the mark reading means reads and checks the check described in the check column in the answer sheet.

When the change request is checked (in the case of “change” in step S5-2), the management computer 21 creates a response message for the change request and automatically transmits it to the destination host computer 60 (step S5-3). Specifically, first, the management computer 21 specifies the corrected bank account identifier and payee name based on the answer sheet. Here, when the check box for the change candidate's transfer request to the transfer destination account is checked, the correction transfer destination (transfer of the correction candidate) from the correction history data storage unit 34 based on the customer identifier and the impossible transfer destination. The previous account identifier and recipient name) are extracted. On the other hand, when the check column of no change to the transfer destination account of the correction candidate is checked, the correction transfer destination entered in the correction transfer destination entry column of the answer sheet is read by the OCR means. Then, a change request including the inquiry number included in the inquiry message, the specified correction transfer destination (transfer destination account identifier and recipient name), and identification information of the financial institution B as the transmission destination is created. Then, the management computer 21 sends an answer message including this change request to the network system 70. The reply message sent to the network system 70 is transmitted to the destination host computer 60 of the financial institution B based on the identification information of the destination financial institution B. The management computer 21 records “change request transmission” as the status for the inquiry form management data 350 specified by the reference number.

  Then, the management computer 21 automatically creates a transfer data correction request list for each transfer requester (step S5-4). Transfers for each client identifier using the client's customer identifier, the transfer requester name included in the created change request, the impossible transfer destination (account identifier and recipient name), and the modified transfer destination (account identifier and recipient name) Create data related to the data correction request list. This data is recorded in a predetermined storage unit in the destination host computer 20. And it prints using the printing apparatus in the financial institution A at a predetermined timing, and submits it to the branch in charge of the transfer requester. As a result, the branch in charge can grasp the inability to make a transfer request.

  And the management computer 21 accumulate | stores a customer identifier, an impossible transfer destination, and a correction transfer destination in the correction history data memory | storage part 34 based on an answer sheet (step S5-5). Specifically, the customer identifier specified from the transfer request data 330 based on the reference number specified by the barcode, the impossible transfer destination and the corrected transfer destination included in the response message are recorded.

  When there is a check in the recombination request (in the case of “combination” in step S5-2), the management computer 21 transmits a reply message of the recombination request to the destination host computer 60 (step S5-6). Specifically, the management computer 21 creates a response message including a reference number included in the inquiry message, a recombination request flag, and identification information of the financial institution B that is a transmission destination, and sends it to the network system 70. The reply message sent to the network system 70 is transmitted to the destination host computer 60 of the financial institution B based on the identification information of the destination financial institution B. Note that the management computer 21 records “combination request transmission” as the status for the inquiry form management data 350 specified by the reference number.

  In this case, the management computer 21 waits for reception of a return message for returning the return money from the destination host computer 60. When receiving the return message for returning the return money from the destination host computer 60 (YES in step S5-7), the management computer 21 identifies the transfer requester based on the return message, and designates the designated account. Is automatically deposited (step S5-8). Specifically, first, the transfer request data storage unit 33 is searched based on the reference number included in the return message, and the client customer identifier is extracted. Then, the customer data storage unit 32 is searched by this client customer identifier (customer identifier), and the account identifier is extracted. Then, the reconstitution funds are deposited into the designated account specified by the account identifier.

As described above, according to the present embodiment, the following effects can be obtained.
In the above-described embodiment, the transmission category data storage unit 31 that records the transmission category and the correspondence category in association with each other, and the correction history data storage unit 34 that records the impossible transfer destination that cannot be transferred and the correction transfer destination in association with each customer. Is used. Then, when the management computer 21 of the destination host computer 20 receives a notification indicating that the transfer request cannot be made, the correspondence classification is specified using the transmission classification data storage unit 31 based on the transmission classification included in the transfer request, When the correspondence classification is “requires correction history recording”, the transfer history included in the received transfer request that cannot be transferred is searched using the correction history data storage unit 34. And when the impossible transfer destination is recorded about the customer in the correction history data storage part 34, the correction transfer destination corresponding to this impossible transfer destination is acquired, the inquiry form which displayed this correction transfer destination is created, and this The data is transmitted to the customer's customer facsimile machine 83. Then, when a reply document in which the confirmation result is entered in the inquiry form is received from the customer, the modification history data 340 is recorded in the modification history data storage unit 34 based on the reply document.

Thereby, the financial institution A can acquire the transfer destination of the correction candidate corresponding to the impossible transfer destination based on the correction history, create an inquiry form displaying the correction candidate, and provide it to the customer. Thereby, the customer can confirm the correction candidate displayed on the inquiry form, and can notify the answer sheet in which the confirmation result is written on the inquiry form. And the financial institution A can receive the correction instruction | indication by a customer, can correct a transfer destination efficiently, and can perform a transfer process.

  Accordingly, when the transfer request becomes impossible, the financial institution A can efficiently perform the transfer process to the corrected transfer destination upon receiving an instruction regarding the correction of the transfer destination from the customer. On the other hand, when the transfer request becomes impossible, the customer can efficiently instruct the financial institution A to correct the transfer destination using the inquiry form displaying the correction candidates corresponding to the impossible transfer destination. .

  In the above embodiment, a customer identifier is recorded in the transmission condition data storage unit 36 for a customer whose transmission condition is to immediately send an inquiry form. When the customer identifier is recorded in the transmission condition data storage unit 36, the inquiry form is immediately transmitted to the customer after the inquiry form is created. On the other hand, when the customer identifier is not recorded in the transmission condition data storage unit 36, when a transfer failure is acquired, the inquiry form is accumulated, and a predetermined time (20 minutes) has elapsed since the accumulation of the inquiry form for the customer is started. Later, the accumulated inquiry about transfer failure is sent to the user. Accordingly, the inquiry forms accumulated during a predetermined time after the accumulation of the inquiry forms can be collectively transmitted to the customer. Therefore, the customer can receive a plurality of inquiry forms together, and the complexity of the procedure can be reduced. On the other hand, a customer who desires correction as quickly as possible can obtain an inquiry form immediately after creating the inquiry form. Accordingly, it is possible to provide an inquiry form at a timing according to the customer's request.

  In the above-described embodiment, a bar code for specifying a transfer request is attached to the inquiry slip transmitted by facsimile to the customer. Then, the management computer 21 receives the inquiry form (answer) filled with the confirmation result by the customer, reads the barcode attached to the answer, specifies the transfer request, and relates to the impossible transfer destination related to this. The correction history is recorded in the correction history data storage unit 34. As a result, with respect to the inquiry form (answer form) in which the confirmation result is entered by the customer, the transfer request can be efficiently identified and the correction history can be recorded using the barcode attached to the answer form.

  -In the above embodiment, when the management computer receives a reorganization message, the management computer identifies the transfer requester based on the recombination message, and deposits the amount in the recombination message to the designated account of the transfer requester. . Accordingly, by automatically depositing the designated account of the transfer requester based on the return message, the customer can be refunded efficiently in the case of return.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, when there is a transmission condition that the inquiry form is immediately transmitted, the customer identifier is recorded in the transmission condition data storage unit 36. Then, if the customer identifier is not recorded in the transmission condition data storage unit 36, the inquiry form is facsimile-transmitted to the customer after accumulating for 20 minutes. Instead, the standby reference time may be changed for each customer. In this case, standby reference time data storage means for recording data relating to the standby reference time is provided for each customer. Then, when the inquiry message regarding the inability to transfer is received, this inquiry form may be accumulated during the standby reference time for the customer, and the accumulated inquiry form may be transmitted to the customer after the standby reference time has elapsed. Specifically, the accumulation start time (transfer impossible time) is acquired for each customer identifier, and the standby reference time elapsed time is calculated. Then, by comparing the current time measured by the time measuring means with the calculated standby reference time elapsed time, the standby reference time elapsed is detected. Alternatively, a timer (time measuring means) is provided for each customer identifier, and when accumulation is started for each customer identifier, measurement of the accumulation time by each timer is started. Then, the standby reference time elapse is detected by comparing the acquired storage time with the standby reference time. Then, after the standby reference time has elapsed, the accumulated inquiry forms are transmitted to the customer. Thereby, the inquiry forms accumulated during the standby reference time registered for each customer can be transmitted together. Therefore, a more preferable service can be provided for each customer.

  Further, the inquiry form may be transmitted when the predetermined number of cases is exceeded even within the standby reference time. In this case, a transfer impossible notification reference number data storage means for recording data related to the transfer impossible notification reference number for each customer is provided. And when the management computer 21 receives the inquiry message regarding the inability to transfer, the management computer 21 starts measuring the waiting time for this customer, and counts the number of ineffective transfers waiting for the inquiry to this customer. Then, when the number of transfer impossible cases exceeds the transfer impossible notification reference number within the standby reference time, an inquiry form is sent to the customer. Specifically, even if the waiting reference time elapsed time calculated based on the accumulation start time (transfer impossible time) has not elapsed, if the number of transfer impossible exceeds the reference number of transfer impossible notifications, Ship. Alternatively, even if the accumulation time measured by the timer for each customer identifier does not reach the standby reference time, if the transfer impossible number exceeds the transfer impossible notification reference number, an inquiry form is sent to the customer. As a result, for each customer, if the number of payment failures accumulated during the waiting reference time exceeds the number of payment impossible notification criteria, the inquiry form is quickly compiled even if the waiting reference time has not been reached. Can be sent.

  In the above embodiment, the customer sends back the confirmation result (answer) of the inquiry form received by facsimile and notifies the financial institution A of the confirmation result of the inquiry content regarding the inability to transfer. Instead, the inquiry content regarding the inability to transfer may be transmitted to the customer by e-mail, and the customer may return an e-mail in which an answer to this is described. In this case, based on the reply described in the returned e-mail, the management computer 21 specifies a correction transfer destination in the case of a change request, a change request, a reorganization request, or a change request.

1 is a schematic diagram of a system according to an embodiment of the present invention. Explanatory drawing of the data recorded on the transmission classification data storage part. Explanatory drawing of the data recorded on the customer data storage part. Explanatory drawing of the data recorded on the transfer request data storage part. Explanatory drawing of the data recorded on the correction history data storage part. Explanatory drawing of the data recorded on the inquiry vote data storage part. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention. Explanatory drawing of the process sequence of one Embodiment of this invention.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 20 ... Destination host computer, 21 ... Management computer, 31 ... Transmission classification data storage part as request classification data storage means, 32 ... Customer data storage part as user account designation data storage means, 34 ... As correction history data storage means Correction history data storage unit 60...

Claims (6)

Request category data storage means that records the request category and the correspondence category in association with each other, correction history data storage means that records in association the impossible transfer destination account information and the correction transfer destination account information for each user, and for each user Standby reference time data storage means for recording data related to standby reference time for accumulating transfer impossible, timing means, transfer impossible notification reference number data storage means for recording data on transfer impossible notification reference number for each user, and counter And using a management computer to perform a response process for a transfer request that cannot be transferred,
The management computer is
Identifying a correspondence category using the request category data storage means based on the request category included in the transfer request when a transfer impossible notification is received for the transfer request;
Searching the transfer destination of the transfer request of the received transfer impossible notification using the correction history data storage unit based on the correspondence category;
When the transfer destination that cannot be transferred is recorded as the impossible transfer destination account information in the correction history data storage means with respect to the user of the transfer request, the correction transfer destination account information corresponding to the impossible transfer destination account information is acquired. , Create a confirmation request to display this ,
For the user related to the non-transfer notice, time measurement is started using the timing means, and during the waiting reference time for the user in the non-transfer notice, based on the non-transfer notice received for the user Accumulate confirmation request text,
Count the number of transfer impossible for each user identifier using the counter,
Sending the accumulated confirmation request text to the user when the transfer impossible number exceeds the transfer impossible notification reference number within the standby reference time, or when the standby reference time has elapsed ,
And a step of recording a correction history in the correction history data storage unit based on the confirmation result when a confirmation result is received from the user.   The confirmation request message sent to the user includes a display code for specifying the transfer request,
  The step of recording the correction history based on the confirmation result includes a table included in the confirmation result message when the confirmation result message in which the confirmation result is entered by the user in the confirmation request message is received.
2. The transfer request handling processing method according to claim 1, wherein the transfer request is identified by reading the identification code, and the correction history of the impossible transfer destination account information relating thereto is recorded in the correction history data storage means.   Further using a user account designation data storage means for recording the user identifier in association with the account identifier of the designated account of the user,
  When the management computer receives a return message, the transfer requester is specified based on the return message, and the designated account of the transfer requester is specified using the user account specification data storage means. 3. The method according to claim 1, further comprising the step of depositing a reimbursement amount into the designated account of the transfer requester based on the reorganization message.   Request category data storage means that records the request category and the correspondence category in association with each other, correction history data storage means that records in association the impossible transfer destination account information and the correction transfer destination account information for each user, and for each user Standby reference time data storage means for recording data related to standby reference time for accumulating transfer impossible, timing means, transfer impossible notification reference number data storage means for recording data on transfer impossible notification reference number for each user, and counter And a transfer request response processing program for performing a response process for a transfer request that cannot be transferred using a management computer,
  The management computer,
  When a transfer impossible notification is received for a transfer request, based on a request category included in the transfer request, a corresponding category identifying unit that identifies a corresponding category using the request category data storage unit;
  Based on the correspondence classification, a transfer destination search means for searching for a transfer destination of the transfer request of the received transfer impossible notification using the correction history data storage means,
  When the transfer destination that cannot be transferred is recorded as the impossible transfer destination account information in the correction history data storage means with respect to the user of the transfer request, the correction transfer destination account information corresponding to the impossible transfer destination account information is acquired. , Create a confirmation request to display this,
  For the user related to the non-transfer notice, time measurement is started using the timing means, and during the waiting reference time for the user in the non-transfer notice, based on the non-transfer notice received for the user Accumulate confirmation request text,
  Count the number of transfer impossible for each user identifier using the counter,
  Confirmation request means for transmitting the accumulated confirmation request text to the user when the number of incapable transfer within the waiting reference time exceeds the reference number of non-transferable notification or when the waiting reference time has elapsed,
  Confirmation result registration means for recording a correction history in the correction history data storage means based on the confirmation result when a confirmation result is received from the user
Transfer request processing program to function as.   The confirmation request message sent to the user includes a display code for specifying the transfer request,
  When the confirmation result registration means receives the confirmation result message in which the confirmation result is entered by the user in the confirmation request message, the transfer result is specified by reading the display code included in the confirmation result message. 5. The transfer request handling processing program according to claim 4, wherein the correction history of the impossible transfer destination account information relating to the function is recorded as means for recording in the correction history data storage means.   Further using a user account designation data storage means for recording the user identifier in association with the account identifier of the designated account of the user,
  When the management computer further receives a reorganization message, the transfer requester is identified based on the recombination message, and the transfer requester is identified using the user account designation data storage means.
6. The transfer request handling processing program according to claim 4 or 5, wherein the specified account is specified and functioned as means for depositing the reimbursement amount into the specified account of the transfer requester based on the reorganization message. .

Images