JP2020042383A - Transfer management system, transfer management method and transfer management program - Google Patents

Abstract

To provide a transfer management system capable of reducing a burden of reverse transfer on a customer even if a plurality of transfer errors occur to a transfer request.SOLUTION: A transfer management system 80 comprises a reception unit 81 and a totaling unit 82. The reception unit 81 receives a telegraphic message based upon a transfer error occurring to a transfer request made for each case based upon a collective transfer indication by a customer. The totaling unit 82 deposits reverse transfer funds, corresponding to transfer requests that respective received telegraphic messages indicate, into special accounts provided, customer by customer, and then totals the reverse transfer funds of the customers.SELECTED DRAWING: Figure 10

Description

  The present invention relates to a transfer management system for managing a transfer error, a transfer management method, and a transfer management program.

  In recent years, exchange transfer processing has been performed among many financial institutions. Generally, the processing of the exchange transfer is performed by a host computer of a transfer source financial institution (sometimes referred to as a destination or destination financial institution) from a host computer of a transfer destination financial institution (a destination or destination financial institution). This is performed by transmitting a transfer message to the host computer of (1).

  On the other hand, it is said that an exchange transfer error (payment error) has occurred in a few percent of domestic exchange transfers, which is one of the factors that squeeze the branches that handle the transfer. Examples of the exchange transfer error include, for example, a slight name difference, an account number error, and the like.

  Generally, for a transfer that has been determined to be an exchange transfer error by the transfer-destination financial institution, a fund return process (return) from the transfer-destination financial institution is performed. For example, Patent Document 1 describes a reversion processing system that efficiently processes post-reassembly processing. The recall processing system described in Patent Document 1 searches for an answer message corresponding to a replacement message received with the return of funds from the transfer destination financial institution from an answer message requesting reimbursement to the transfer destination financial institution. Is linked with the replacement message and the answer message.

JP 2014-106612 A

  On the other hand, there are cases where customers such as local governments make a batch transfer request. The destination financial institution individually makes a transfer request based on the collective transfer request, but a plurality of transfer errors may occur at one time.

  In such a case, in the method described in Patent Literature 1, in the method of individually confirming the post-processing contents to the transfer request customer for all transfer errors and performing reintegration, both the financial institution and the customer In addition, there is a problem that a great load is imposed on the transfer handling.

  Therefore, an object of the present invention is to provide a transfer management system, a transfer management method, and a transfer management program that can reduce the load of reinstatement on a customer even when a plurality of transfer errors occur in a transfer request.

  A threat transfer management system according to the present invention includes a receiving unit that receives a message based on a transfer error generated for a transfer request performed for each case based on a batch transfer instruction from a customer, and a separate account provided for each customer. And a totalizing unit that receives the reinstatement fund of the transfer request indicated by each received message and totals the reinstatement fund of the customer.

  In the transfer management method according to the present invention, a message based on a transfer error generated for a transfer request made for each case based on a batch transfer instruction from a customer is received, and received in a separate account provided for each customer. The refunding fund of the transfer request indicated by each message is deposited, and the refunding fund of the customer is totaled.

  A transfer management program according to the present invention is provided in a computer, a receiving process for receiving a message based on a transfer error generated for a transfer request performed for each case based on a batch transfer instruction from a customer, and provided for each customer. The refunding fund of the transfer request indicated by each received telegram is deposited in the separate account, and a totalizing process for totalizing the refunding fund of the customer is executed.

  ADVANTAGE OF THE INVENTION According to this invention, even if several transfer errors generate | occur | produce with respect to a transfer request, the load of the recall to a customer can be reduced.

It is a block diagram showing the example of composition of the first embodiment of the transfer management system by the present invention. It is explanatory drawing which shows the example of output of the description for every telegram. It is explanatory drawing which shows the example of output of a reception slip. It is an explanatory view showing an example of repatriation via another account. 6 is a flowchart illustrating an operation example of the transfer management system according to the first embodiment. 5 is a flowchart illustrating an operation example of the transfer management server of the first embodiment. It is a block diagram showing the example of composition of the 2nd embodiment of the transfer management system by the present invention. It is explanatory drawing which shows the other example of recall via another account. It is a flow chart which shows the example of operation of the transfer management system of a 2nd embodiment. It is a block diagram showing the outline of the transfer management system by the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
The transfer management system of the present invention can be used as a system of a destination financial institution or a system of a destination financial institution. Hereinafter, the transfer management system of the present invention will be described by dividing the embodiment into the roles of each financial institution.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration example of a first embodiment of a transfer management system according to the present invention. The transfer management system 100 according to the present embodiment includes a storage unit 10, a transfer management server 20, and a terminal 30. The transfer management system 100 according to the first embodiment is a system that is assumed to be used as a system of a destination financial institution. The transfer management server 20 is provided, for example, for each financial institution.

  The storage unit 10 is a storage device that stores various information. The storage unit 10 is provided, for example, in an accounting host computer (not shown), and the accounting host computer is communicably connected to the transfer management server 20 and the terminal 30.

  The storage unit 10 is a storage device that stores various information. The storage unit 10 of the present embodiment stores a separate account 11. The separate account 11 is an account for temporarily storing funds and deposits, and is an account opened by each financial institution in advance for each customer.

  The transfer management server 20 includes a storage unit 22, an error receiving unit 23, an error sorting unit 24, and an output unit 25.

  The storage unit 22 is also a storage device that stores various information. The storage unit 22 of the present embodiment also stores the customer master 12. The customer master 12 of the present embodiment stores information in which information of a customer making a transfer request is associated with information for identifying a separate account 11 opened for the customer. Further, the customer master 12 includes information for identifying whether or not a customer who performs a plurality of recalls collectively (hereinafter, referred to as a collective recall customer). Note that the customer information includes a name (for example, a kana name) that can specify the customer information (client information) included in the message. The customer master 12 is set to include information that can uniquely identify each customer. The customer master 12 is registered in the storage unit 22 in advance by, for example, a person in charge of each financial institution.

  In general, in a local public organization or the like, a client is assigned to each processing unit (department unit). For example, even if the same "Osaka Kafu Zimukoku" is a customer, if the processing unit is a plurality of offices ("AAA gym show", "BBB gym show", "CCCCC gym show"), the customer master 12 is registered as a different transfer requester. You.

  In the present embodiment, when the destination financial institution receives a lump-sum transfer instruction that combines a plurality of transfer requests from a customer, the accounting host computer of the destination financial institution sends the lending financial institution to the destination financial institution based on the lump-sum transfer instruction. Make a transfer request for each case. In the following description, a public institution such as a local public entity is exemplified as a customer, and a lump-sum transfer instruction of a public money exchange transmitted from a public institution is illustrated as a lump-sum transfer instruction. However, the customer is not limited to a public institution, and the lump-sum transfer instruction is not limited to the lump-sum transfer instruction for public money exchange.

  Here, it is assumed that the transfer processing is not performed normally and a transfer error occurs in the destination financial institution. In this case, a process of returning funds from the destination financial institution (that is, refunding funds) is performed. Generally, fund repatriation is performed for each transfer request, so when a transfer error occurs for a plurality of transfer requests, a plurality of messages indicating fund repatriation are transmitted from the destination financial institution to the destination financial institution. You.

  The error receiving unit 23 receives, from the destination financial institution, a message (more specifically, a message (replacement data) indicating fund repatriation) based on the transfer error generated in response to the transfer request.

  When the error receiving unit 23 receives a plurality of messages for the same transfer requester (customer), the error sorting unit 24 refers to the customer master 12 and sets the transfer requester (customer) as a target for collective reassembly. Determine whether the customer. If the transfer requester is a lump-sum recall customer, the error sorting unit 24 deposits the recall fund of the transfer request indicated by each received telegram into the separate account 11 provided for the customer. In the case where one transfer error is received, the error sorting unit 24 may directly transfer the reimbursement funds to the account of the transfer requester (customer).

  The error sorting unit 24 adds the reinstatement funds indicated by the message to the separate account 11 for each case, and totals the reinstatement funds of the customer for each batch transfer instruction.

  In general, it is not possible to simply collect the refunding funds included in a plurality of received messages. For example, even if the information on the refunding fund indicated by the received message is temporarily stored in the database, the refunding fund cannot be simply collected based on the stored information. The reason why such a report cannot be organized is as follows.

  For example, it is assumed that two transfer requests of 10,000 yen and 50,000 yen are each determined to be a transfer error. In this case, the transfer error is treated as two cases, that is, a transfer error of 10,000 yen and a transfer error of 50,000 yen. These cases are required to be processed as separate cases, and are guarded from being handled as different amounts. In other words, a transfer error of 10,000 yen must be dealt with by either depositing or refunding 10,000 yen. Therefore, just because there is a transfer error of 10,000 yen and a transfer error of 50,000 yen, it cannot be used immediately for the purpose of 60,000 yen. This is because if a transfer error of 10,000 yen and a transfer error of 50,000 yen are used for a purpose of 60,000 yen, it becomes unknown how each transfer error was processed.

  Therefore, in the present embodiment, the financial institution previously establishes an additional account 11 as an account for refunding the reinstatement fund, and the error sorting unit 24 stores the reinstatement fund indicated by the message for each case in the extra account 11. Make a deposit. By depositing the reinvestment fund of each case into the separate account 11, each case can be treated as a completed case, so that each case can be put together.

  Further, it is also conceivable that such a collecting process is realized by an accounting host computer. However, it is often difficult to incorporate such processing into the accounting host computer. On the other hand, in the present embodiment, the transfer management server 20 provided separately from the accounting host computer can collect the reinstatement funds, thereby simplifying post-processing of reintegration while suppressing the influence on the existing system. It becomes possible.

  If the transfer requester is not a lump-sum recall customer, the error sorting unit 24 notifies the terminal 30 of the contents of the transfer error in order to individually handle the transfer error. At this time, the error sorting unit 24 may cause the output unit 25, which will be described later, to output a specification for confirming the case in which the payment cannot be made.

  The output unit 25 outputs various information related to the transfer request in which a transfer error has occurred. The output unit 25 may output, for example, a statement for each telegram deposited in the special account 11, as a result of collecting the transfer errors. Since the repatriation fund returned to the customer is the totalized amount, the output unit 25 outputs the details of each telegram deposited in the separate account 11 so that the customer can confirm the breakdown of the repatriation. it can. In addition, the output unit 25 may output a reception slip or a work statement in which a reason for a failure to receive payment and the like are described in order to individually handle the transfer error.

  FIG. 2 is an explanatory diagram illustrating an example of output of a statement for each message received in another account. The description illustrated in FIG. 2 is an example in which details including a transfer time, a transfer destination, a cause of a transfer error, and a reimbursement are output for each transfer requester.

  FIG. 3 is an explanatory diagram showing an output example of a reception slip. The reception slip illustrated in FIG. 3 is an example of a form output in the event of a transfer error, and includes the contents of a transfer message (for example, a transfer amount and a withdrawal account) and the cause of the transfer error (“ Recipient name mismatch)). The output unit 25 may display the details illustrated in FIGS. 2 and 3 on a screen or may output the details as a form.

  Note that, in the above description, an example has been given of a case where the target for collecting the reintegration and the target for outputting the details are the cases of the batch transfer instruction. However, the target for collecting the reconciliation and the target for outputting the statement are not limited to the case of one batch transfer instruction. The output of the recall and the statement may be not only the unit of the lump-sum transfer instruction, but also a unit sent to another bank during a certain period (for example, the same day), or a unit returned from another bank during a certain period. Is also good.

  Further, when there are a plurality of cases for which remittance was requested on the same day, the output unit 25 may collect the cases of the batch transfer instruction and the plurality of cases for which remittance was requested on the same day. For example, it is assumed that the customer makes a lump-sum transfer request in the morning of August 20 and another lump-sum transfer request in the afternoon. In this case, the output unit 25 may combine the requests for the batch transfer in the morning and the afternoon into one.

  In addition, even if the disabled case extends over a plurality of days, the output unit 25 collectively processes the cases up to the date of return. For example, suppose that 100 items were sent to other banks a day, and 50 items were sent on a second day. However, when the impossibility of the case processed by the other bank on the first day is also returned on the second day, the output unit 25 collects the impossibility cases of the first day and the second day. In this case, there is one type of specification.

  The terminal 30 includes a display unit 31 and a control unit 32. The terminal 30 is a terminal that performs processing for a transfer error in accordance with an operation by a person in charge of each financial institution.

  The display unit 31 displays various information under the control of the control unit 32. The display unit 31 is realized by, for example, a display device or the like.

  The control unit 32 displays the contents of the transfer error notified from the error sorting unit 24 on the display unit 31. Then, the control unit 32 receives various operations of the person in charge of the displayed transfer error. The control unit 32 may, for example, deposit the reinstatement fund directly into the customer's account. In the case where the customer's special account 11 exists, the control unit 32 may deposit the reinstatement fund into the customer's special account 11.

  In addition, the control unit 32 may collect the refunded funds deposited in the special account 11 and deposit the refunded funds into the customer's account in accordance with the instruction of the operator. At this time, the control unit 32 may collectively deposit all reimbursement funds deposited in the separate account 11 into the customer's account, or may combine the reimbursement funds for each lump-sum transfer instruction into the customer's account. You may deposit. However, the target of the lump-sum payment is not limited to the lump-sum transfer instruction.

  FIG. 4 is an explanatory diagram showing an example of repatriation via another account. In the example shown in FIG. 4, a transfer management server 20, a terminal 30 (entry terminal), and an accounting host computer 40 are provided in the destination financial institution F1 of the bank. When receiving the lump-sum transfer instruction from the public institution F3, which is a customer, the accounting host computer 40 transmits a money transfer transfer message 41 to the destination financial institution F2 of another bank. It is assumed that a transfer error has occurred in the destination financial institution F2.

  It is assumed that a transfer error has been returned to the destination financial institution F2 due to, for example, unnecessary inquiry or a request from the client. When the transfer management server 20 (more specifically, the error receiving unit 23) receives the money order exchange data 42 that has been refunded from the destination financial institution F2 of another bank, the error sorting unit 24 Automatic payment 43 is made to the separate account 11 for each customer of the person (public institution), and the return funds are collected.

  In addition, the error sorting unit 24 notifies the entry terminal of the replacement data that has not been included in the collection. Further, the output unit 25 outputs the details 44 of the case for which payment has become impossible. The person in charge of the destination financial institution can deposit the refunding fund 45 to the special account 11 via the entry terminal. Thereafter, the collected funds 46 are returned to the public agency F3 according to the instruction of the person in charge.

  Although FIG. 4 illustrates the case where the destination financial institution F2 is another bank, the destination financial institution F2 may be its own bank.

  The error receiving unit 23, the error sorting unit 24, and the output unit 25 are realized by a CPU of a computer that operates according to a program (transfer management program). For example, the program may be stored in the storage unit 22 of the transfer management server 20, and the CPU may read the program and operate as the error receiving unit 23, the error sorting unit 24, and the output unit 25 according to the program. Further, each of the error receiving unit 23, the error sorting unit 24, and the output unit 25 may be realized by dedicated hardware.

  Next, the operation of the transfer management system of the present embodiment will be described. FIG. 5 is a flowchart illustrating an operation example of the transfer management system 100 of the present embodiment.

  The accounting host computer of the destination financial institution receives the lump-sum transfer instruction from the public institution as the customer (step S11). The accounting host computer issues a transfer request for each case based on a batch transfer instruction from the customer (step S12). The transfer management server 20 (more specifically, the error receiving unit 23) receives a plurality of messages based on the transfer error generated in response to the transfer request from the destination financial institution (Step S13).

  The transfer management server 20 (more specifically, the error sorting unit 24) deposits the reimbursement fund of the transfer request indicated by each received message into the separate account 11 provided for each customer (step S14). The terminal 30 (more specifically, the control unit 32) collects the reimbursement funds deposited in the special account 11 and collectively deposits them into the account of the public institution that is the customer (step S15).

  FIG. 6 is a flowchart illustrating an operation example of the transfer management server 20 of the present embodiment. The error receiving unit 23 receives a message based on a transfer error generated for a transfer request made for each case based on a batch transfer instruction from the customer (step S21). The error sorting unit 24 deposits the reinstatement fund of the transfer request indicated by each received message into the separate account 11 provided for each customer, and totalizes the reinstatement funds of the customer (step S22).

  As described above, in the present embodiment, the error receiving unit 23 receives a message based on a transfer error generated for a transfer request made for each case based on a batch transfer instruction from a customer. Then, the error sorting section 24 deposits the reinstatement fund of the transfer request indicated by each received message into the separate account 11 provided for each customer, and totals the reinstatement funds of the customer. Therefore, even if a plurality of transfer errors have occurred in response to the transfer request, the load of recalling on the customer can be reduced.

Embodiment 2. FIG.
Next, a second embodiment of the transfer management system according to the present invention will be described. FIG. 7 is a block diagram showing a configuration example of the second embodiment of the transfer management system according to the present invention. The transfer management system 200 according to the present embodiment includes a storage unit 10, a transfer management server 50, and a terminal 30. The transfer management system 200 of the second embodiment is a system that is assumed to be used as a system of a destination financial institution. The contents of the terminal 30 are the same as in the first embodiment.

  In this embodiment, the transfer management system 200 receives a plurality of transfer requests from the destination financial institution that has received the lump-sum transfer instruction from the customer. In the following description, a public institution such as a local public entity is exemplified as a customer, and a lump-sum transfer instruction of a public money exchange transmitted from a public institution is illustrated as a lump-sum transfer instruction. For example, a situation is assumed in which a collective transfer instruction is issued from a public institution to a destination store of the bank and a plurality of transfer requests are made with another store in the bank as a destination store.

  Here, it is assumed that a plurality of transfer errors have occurred in the accounting host computer that has received the transfer request. In the present embodiment, a description will be given of a method of collecting funds return processing (that is, fund return) for a plurality of transfer errors.

  The transfer management server 50 includes a storage unit 52, an error receiving unit 53, an error sorting unit 54, and an output unit 55.

  As in the first embodiment, the transfer management server 50 is provided, for example, for each financial institution. The storage unit 10 also stores the separate account 11 as in the first embodiment. The contents of the separate account 11 are the same as in the first embodiment. Further, the storage unit 52 stores the customer master 12 as in the first embodiment.

  The error receiving unit 53 receives a transfer error for a transfer request made to the own bank from, for example, the accounting host computer of the own bank. The message indicating the transfer error received here may be described as a destination error message.

  In addition, the destination error message may include information (hereinafter, referred to as an inquiry necessity flag) for identifying whether or not the customer is required to make an inquiry for a transfer error when a transfer error occurs. The inquiry necessity flag is used when the error sorting unit 54 described later determines whether or not to collect transfer errors for the customer.

  As in the first embodiment, when receiving a plurality of destination error messages for the same transfer requester (customer), the error sorting unit 54 refers to the customer master 12 and collects the transfer requester (customer) collectively. It is determined whether the customer is a reinstated customer. If the transfer requester is a lump-sum recall customer, the error sorting unit 54 deposits the recall fund of the transfer request indicated by each received error message to be received into the separate account 11 provided for the customer. The error sorting unit 54 collects the customer's refunding funds for each batch transfer instruction by depositing the refunding funds for the destination error telegram into the separate account 11 for each case.

  In addition, as a premise that the reinstatement fund of the transfer request indicated by the destination error message is deposited in the special account 11, the error sorting unit 54 sets the inquiry necessity flag included in the destination error message to “inquiry unnecessary”. May be targeted at only those customers who have That is, the error sorting unit 54 may deposit the reinstated funds of the transfer request indicated by the transfer error into the special account 11 when the customer does not need the inquiry.

  The destination error message includes the cause of the transfer error. Therefore, the cause of the transfer error to be collected may be determined in advance, and the error sorting unit 54 may set the transfer error matching the cause to be the collected target. For example, if the cause of the transfer error to be collected is defined as "payee name mismatch", the error sorting unit 54 may collect the transfer error whose cause is "payee name mismatch".

  Note that the cause of the predetermined transfer error is not limited to one, and the cause of the transfer error is not limited to “payee name mismatch”. Other causes of the transfer error include "subject difference", "account number difference", "no corresponding account", and the like. The error sorting unit 54 may collect the transfer errors irrespective of the cause of the transfer error, as long as the name of the client is registered as a collecting target (that is, a customer who collects and returns the package).

  As in the first embodiment, the output unit 55 may output a statement for each received case or a task statement. Further, the output unit 55 may automatically transfer the collected information of the reinstatement fund to the business office.

  FIG. 8 is an explanatory diagram showing another example of repatriation via another account. In the example shown in FIG. 8, a transfer management server 50, a terminal 30 (entry terminal), and an accounting host computer 60 are provided in the financial institution F4 of the own bank. Here, it is assumed that a transfer error occurs when the accounting host computer 60 receives a transfer message 47 relating to public money from the public institution F3 as a customer, for example, as a transaction between the head office and the branch.

  At this time, when the accounting host computer 60 transmits a plurality of destination error messages 48 to the transfer management server 50, the error sorting unit 54 automatically saves the target client (public institution) to the separate account 11 for each customer. Payment 43 is made and return funds are collected. In addition, the output unit 55 may automatically transfer the collected return fund information 49 to the business office.

  The error sorting unit 54 notifies the entry terminal of the replacement data that has not been included in the collection. In addition, the output unit 55 outputs the details 44 of the case in which payment cannot be made. The person in charge of the destination financial institution can deposit the refunding fund 45 to the special account 11 via the entry terminal. Thereafter, the collected funds 46 are returned to the public agency F3 according to the instruction of the person in charge.

  The error receiving unit 53, the error sorting unit 54, and the output unit 55 are realized by a CPU of a computer that operates according to a program (transfer management program). Further, each of the error receiving unit 53, the error sorting unit 54, and the output unit 55 may be realized by dedicated hardware.

  Next, the operation of the transfer management system of the present embodiment will be described. FIG. 9 is a flowchart illustrating an operation example of the transfer management system 200 of the present embodiment.

  The accounting host computer of the destination financial institution receives a transfer request for each case from the destination financial institution (step S31). The transfer management server 50 (more specifically, the error receiving unit 53) receives a destination error message based on a plurality of transfer errors from the accounting host computer (step S32).

  The transfer management server 50 (more specifically, the error sorting unit 54) transfers the reimbursement fund of the transfer request indicated by each received error message to be received to the separate account 11 provided for each customer (step S33). ). The terminal 30 (more specifically, the control unit 32) collects the reimbursement funds deposited in the special account 11 and collectively deposits them into the account of the public institution that is the customer (step S34).

  The operation of the transfer management server 50 of the present embodiment is the same as the operation of the transfer management server 20 of the first embodiment illustrated in FIG. Even with the configuration of the present embodiment, similarly to the first embodiment, even when a plurality of transfer errors occur for a transfer request, it is possible to reduce the load of recalling to the customer.

  Next, a modified example of the transfer management system according to the second embodiment will be described. In the second embodiment, a method has been described in which, when a plurality of transfer errors occur, the refunded funds for all the transfer errors are transferred to the special account 11.

  By the way, in the business of the financial institution, there is a case where a future transfer is made. Then, a cancellation process (a future date cancellation process) for the future transfer may be performed at a later date. Specifically, after a future date transfer is performed by specifying a date three days later, a transfer process (hereinafter, referred to as a corrected transfer) in which the details of the transfer are corrected (for example, a change in the transfer amount) is performed. There is.

  In this case, since the already-transferred transfer is valid, the transfer-destination financial institution performs a payment stop process on the transfer-destination account in order to make the transfer at future date an error. At this time, two transfer requests of a future transfer and a correction transfer have been made, but since the payment stop process has been performed, both transfer requests result in a transfer error.

  In this case, it is preferable that the first transfer request be refunded as a transfer error, and that the second transfer request be processed by the financial institution without being refunded. When a transfer request is made to the account on which the payment suspension processing has been performed, an error indicating that "account cannot be deposited" is usually returned.

  Therefore, when the error sorting unit 54 receives a plurality of transfer errors by the same customer indicating that the account cannot be credited, the error sorting unit 54 only transfers the reinstated funds of the transfer request indicated by the initially received destination error message to another account of the customer. Deposit 11 Then, the error sorting unit 54 notifies the terminal 30 of the contents of the remaining destination error message. The transfer request indicated by the destination error message notified to the terminal 30 is individually dealt with by the person in charge of each financial institution.

  In this way, the error sorting unit 54 performs reassembly only for the first received transfer error, thereby suppressing unnecessary procedures for the customer.

  Next, the outline of the present invention will be described. FIG. 10 is a block diagram showing an outline of the transfer management system according to the present invention. The transfer management system 80 (for example, the transfer management system 100, the transfer management system 200) according to the present invention provides a message (for example, based on a transfer error generated in response to a transfer request made for each case based on a batch transfer instruction from a customer). Receiving unit 81 (for example, the error receiving unit 23, the error receiving unit 53) for receiving the replacement data 42, the destination error telegram 48, and another account (for example, the separate account 11) provided for each customer. There is provided a counting unit 82 (for example, the error sorting unit 24, the error sorting unit 54) that receives the reinstatement fund of the transfer request indicated by each received message and totals the reinstatement funds of the customer.

  With such a configuration, even when a plurality of transfer errors have occurred in response to the transfer request, it is possible to reduce the reloading load on the customer.

  In addition, when the customer is a target of collective reinstatement, the tallying unit 82 may deposit the reinstatement fund into another account of the customer.

  In addition, when receiving a plurality of messages by the same customer indicating that the account cannot be deposited, the counting unit 82 may transfer only the reimbursement fund of the transfer request indicated by the first received message to another account of the customer. Good. According to such a configuration, it is possible to suppress imposing unnecessary procedures on the customer.

  When the cause of the transfer error specified by the received message matches the cause of the transfer error (for example, mismatch of the recipient name) predetermined as the collection target, the transfer error indicates the transfer error. The reimbursement fund of the transfer request may be transferred to another account.

  Further, the transfer management system 80 may include an output unit (for example, the output unit 25 and the output unit 55) that outputs, for each customer, a statement for each message received in another account. Since the repatriation fund returned to the customer is the totalized amount, the output unit outputs the statement, so that the customer can check the breakdown of the repatriation.

DESCRIPTION OF SYMBOLS 10 Storage part 11 Separate account 12 Customer master 20,50 Transfer management server 22,52 Storage part 23,53 Error receiving part 24,54 Error sorting part 25,55 Output part 30 Terminal 31 Display part 32 Control part 100,200 Transfer management system

Claims (9)

A receiving unit that receives a message based on a transfer error generated for a transfer request made for each case based on a batch transfer instruction from a customer;
A transfer unit for receiving the reimbursement fund of the transfer request indicated by each received message into a separate account provided for each customer, and counting the reimbursement funds of the customer. system. The remittance management system according to claim 1, wherein the totaling unit deposits the reinstatement fund into a separate account of the customer when the customer is a target of collective reinstatement. When receiving a plurality of messages from the same customer indicating that the account cannot be credited, the counting unit deposits only the refunded funds of the transfer request indicated by the first received message into another account of the customer. Item 6. The transfer management system according to Item 2. When the cause of the transfer error specified by the received telegram matches the cause of the transfer error predetermined as the collection target, the totaling unit transfers the refunded funds of the transfer request indicated by the transfer error to another account. The transfer management system according to claim 1 or 2. The transfer management system according to any one of claims 1 to 4, further comprising an output unit configured to output, for each customer, a statement for each message received in another account. Receives a message based on the transfer error that occurred for the transfer request made for each case based on the batch transfer instruction from the customer,
A remittance management method comprising: depositing a reinstatement fund of a transfer request indicated by each received telegram into a separate account provided for each customer; and totalizing the reinstatement funds of the customer. 7. The remittance management method according to claim 6, wherein when the customer is a target of collective repatriation, the repatriation fund is deposited in another account of the customer. On the computer,
A receiving process of receiving a message based on a transfer error generated for a transfer request made for each case based on a batch transfer instruction by a customer, and
A remittance management program for depositing reimbursement funds of a transfer request indicated by each received telegram into a separate account provided for each customer, and executing a tallying process for totalizing the reimbursement funds of the customers. On the computer,
9. The remittance management program according to claim 8, wherein, in the aggregation process, when the customer is a target of collective reinstatement, the reinstatement fund is deposited in another account of the customer.

Images