JP6214207B2 - Transfer data processing apparatus and method - Google Patents

Description

  The present invention relates to a transfer data processing apparatus and method. More specifically, according to the present invention, the transfer data addressed to the same bank account is aggregated to execute the transfer process, and when transferring the transfer payment details, the aggregated transfer data is decomposed into individual detailed data. The present invention relates to a transfer data processing apparatus and method that can be referred to above.

  Conventionally, the system of each financial institution can execute a process of transferring money from a first account (transfer source account) to a second account (transfer destination account). The transfer process includes both the case where the transfer source account and the transfer account are in the same financial institution, and the case where the transfer source account and the transfer account are in separate financial institutions connected via the Zengin System. Can be done.

  It is known that there are two types of transfer processing from a transfer source account to a transfer destination account, roughly divided from the data format used. In other words, the first format is called “recurring transfer (individual transfer)” that is used when the number of transfers is relatively small. The second format is when the number of transfers is relatively large. Is referred to as “total transfer (collective transfer)” (see Patent Document 1). Of these, the general transfer is used when a company wants to make a transfer to a large number of transfer destinations.

  FIG. 1 is a diagram for explaining an example of a general transfer data format. One set of data of general transfer includes header (H) record (including transfer source account information), one or more data (D) record (transfer destination details), trailer (T) record (including total number and total amount), And end (E) records. By using such a data format, it is possible to perform transfer from one transfer source account to a plurality of transfer destination accounts.

  In recent years, a shared service in which indirect operations such as accounting operations of group companies are aggregated and one company in the group undertakes these operations at once is becoming widespread. When using the shared service, the H record may designate a transfer source account of each company or a transfer source account of one company in the company group. When the shared service is not used, the total transfer data in which the transfer source account of each company in the group is designated as the H record is used.

  Furthermore, in recent years, a system in which a virtual account associated with a transfer person is set and the transfer person makes a transfer to the virtual account has become widespread. In this system, the funds transferred to the virtual account are transferred to the recipient's real account, and the account number of the virtual account is displayed in the transfer deposit details file (see Patent Document 2).

JP 2010-271859 A Japanese Patent No. 3029421

  When there is a one-to-one relationship between the transfer source and the transfer destination, the office work for confirming the payment details is not so complicated, although it depends on the number of data. However, in transactions between companies with a wide range of business partners, there are many cases where the transfer source and transfer destination are N to N (N is multiple), and in such cases, the administrative work required to confirm the payment details is extremely It becomes complicated. For this reason, for example, in order to cancel the billing data and the transfer deposit details, additional details data may be additionally transmitted between companies via means such as FAX or e-mail.

  The present invention has been made in view of such a problem, and an object thereof is to provide a transfer data processing apparatus and method capable of reducing office work in a company.

In order to solve the above-mentioned problem, the transfer data processing device according to the present invention is an aggregate data generation unit that generates aggregate data from a plurality of transfer data having a plurality of transfer destination accounts, the transfer data is the data were aggregated for each of the bank account, and only contains a unique transfer person's name for the total amount and the aggregate data of the transfer amount of money to be associated with the bank account, associated with the aggregated data and the aggregated data The transfer data to be generated includes an aggregate data generation unit having a common identifier, and a data decomposition unit for generating second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data The payment details data of is the data indicating the payment details for the bank account, and the first payment details data is the transfer of the aggregated data Includes a deposit item data for the aggregated data that results from physical, the second receiving detailed data, based on the common identifier of the transfer data associated with the aggregated data and the aggregated data for the aggregated data Including the deposit details data obtained by replacing the individual deposit details data with the individual deposit details data , wherein the second deposit detail data is such that the transfer name of the first deposit details data is a unique transfer person name for the aggregated data Data decomposition generated by identifying associated aggregated data by identifying and identifying individual transfer data associated with the aggregated data based on the common identifier of the identified aggregated data characterized in that it comprises a part, a.

The transfer data processing device according to the present invention is an aggregate data generation unit that generates aggregate data from a plurality of transfer data having a plurality of virtual accounts associated with a payer, wherein the aggregate data includes the transfer data An aggregated data generation unit that is data aggregated for each real account associated with the virtual account, and includes a total amount of transfer amounts associated with the virtual account and a unique transfer person name for aggregated data, and a first deposit A data decomposing unit that generates second receipt details data from the details data, wherein the first receipt details data and the second receipt details data are data indicating receipt details for the actual account, The first receipt details data includes receipt details data for the aggregate data generated as a result of transfer processing of the aggregate data, The second payment details data includes payment details data obtained by replacing the payment details data for the aggregated data with the individual transfer data based on the aggregated data and information on the transfer data associated with the aggregated data. deposit detailed data 2, comprising said account number of the virtual account associated with the individual transfer data, characterized by comprising a data decomposing unit.

The transfer data processing method according to the present invention is a step of generating aggregated data from a plurality of transfer data having a plurality of transfer destination accounts, wherein the aggregated data aggregates the transfer data for each transfer destination account. the is the data, and the transfer destination only contains a unique transfer person's name for the total amount and the aggregate data of the transfer amount of money to be associated with the account, transfer data associated with the aggregated data and the aggregated data have a common identifier, And a step of generating second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data are the receipt details for the transfer account. The first deposit statement data is associated with the aggregated data generated as a result of transfer processing of the aggregated data. Of including a deposit item data, the second receiving detailed data, the aggregate data and based on the common identifier of the transfer data associated with the aggregated data, separate said transfer data a deposit item data for said aggregated data And the second receipt details data is related aggregated data by identifying that the transfer name of the first receipt details data is a unique transfer name for the aggregate data. identifies, based on the common identifier of the identified said aggregated data, the generated by identifying the individual of the transfer data associated with the aggregated data, characterized by comprising the steps, a.

The transfer data processing method according to the present invention is a step of generating aggregate data from a plurality of transfer data having a plurality of virtual accounts associated with a payer, wherein the aggregate data includes the transfer data as the virtual account. Including a total amount of transfer amounts associated with the virtual account and a unique transfer person name for the aggregate data, and a second from the first receipt details data. Generating receipt details data, wherein the first receipt details data and the second receipt details data are data indicating receipt details for the real account, and the first receipt details data is: Including payment details data about the aggregated data generated as a result of transfer processing of the aggregated data, and the second payment details data , Based on the information on the aggregated data and the transfer data associated with the aggregated data, the payment details data for the aggregated data is replaced with individual transfer data, and the second deposit detail data is the includes an account number of the virtual account associated with the individual transfer data, characterized by comprising the steps, a.

  According to the present invention, since the receiving company can obtain two types of deposit details data, it is possible to reduce office work in the receiving company. Further, according to the present invention, the receiving company can obtain the deposit details data including the virtual account information, so that it is possible to reduce office work in the receiving company.

It is a figure explaining an example of the data format for total transfers. It is a whole figure for demonstrating the concept of the transfer data processing apparatus which concerns on this invention. It is a system configuration figure of a bank system. It is a figure explaining the detailed image of the transfer data which a payment side company and an aggregation server handle. It is a figure explaining the process which a decomposition | disassembly server produces | generates 2nd transfer payment details data based on 1st transfer payment details data. It is a flowchart explaining one Embodiment of the transfer process performed within a bank system. It is a flowchart explaining other embodiment of the transfer process performed within a bank system.

  Hereinafter, embodiments of the present invention will be described in detail. FIG. 2 is an overall view for explaining the concept of the transfer data processing apparatus according to the present invention. The overall view includes a bank system 100, a payer company 110 computer, and a payer company 120 computer, each connected by a network, from the payer company 110 to the payee company 120 via the bank system 100. The transfer process to is shown. In the following description, for the sake of convenience, the computer of the paying company 110 and the computer of the receiving company 120 may be simply referred to as “paying company 110” and “receiving company 120”, but both are synonymous. I want to be.

  The bank system 100 includes an aggregation server 101 that aggregates transfer data to the same bank account, and a decomposition server 102 that decomposes transfer receipt details data generated by the transfer based on the aggregated transfer data into individual details data. . Although not shown in FIG. 2, the bank system 100 can perform a transfer process, and has a database (DB) for storing various types of information as described with reference to FIG.

  The paying company 110 has transfer data 111X, in which the transfer source account is an account of company X, transfer data 111Y, which is an account of company Y, and transfer data 111Z, which is an account of company Z. Data 111 is transmitted to the bank system 100. FIG. 2 shows a configuration in which one paying company 110 generates and transmits a plurality of transfer data 111. However, each of the plurality of paying companies 110 has their own account (or a predetermined number related to the company). It may be configured to generate the transfer data 111 whose account is the transfer source account and transmit it to the bank system 100.

  The receiving company 120 can receive payment information from the bank system 100 to its own account (or a predetermined account related to the company) that is a transfer destination account. More specifically, the receiving company 120 receives two types of payment details data indicating payment details for the bank account, that is, payment details data based on the aggregated transfer data, and the aggregated transfer data. Transfer payment details data based on the decomposed details data can be received from the bank system 100.

  Further, as another embodiment, the receiving company 120 can transfer payment details data based on detailed data obtained by disassembling the aggregated transfer data even if the bank account 100 does not have its own account as a transfer destination account. Can be received from the bank system 100. In such a case, the receiving company 120 transmits the transfer payment details data based on the aggregated transfer data received from another bank to the bank system 100, and the aggregated transfer data generated by the bank system 100 is transmitted. Transfer payment details data based on the decomposed details data is received from the bank system 100. That is, the present invention can be used if an account of the paying company 110 exists in the bank system 100, and an account of the receiving company 120 may or may not exist in the bank system 100.

  FIG. 3 is a system configuration diagram of the bank system 100. The bank system 100 includes an aggregation server 101, a disassembly server 102, a contract DB 103, a second contract DB 104, a transfer request data 105, an aggregate data 106, a first transfer deposit details data 107, and a second deposit receipt details data 108. These components are connected to each other by a bus 109.

  The aggregation server 101 aggregates the detailed data of the transfer request data stored in the transfer request data 105 using the same transfer destination account as a key, and generates aggregate data 106. As will be described later, the transfer request data 105 stores the transfer request data received from the paying company 110.

  The disassembly server 102 generates second transfer deposit details data 108 from the first transfer deposit details data 107 using the association information between the detail data of the transfer request data 105 and the aggregated data 106. The association information can be an identifier such as a flag, and is set in both the aggregate data 106 and the detailed data of the corresponding transfer request data 105 when the aggregate server 101 generates the aggregate data 106.

The contract DB 103 stores contract information of the paying company 110 that uses transfer data aggregation and disassembly processing. The contract information includes attribute information such as the company name of the paying company 110, transfer source account information for identifying an account used as the transfer source account,
The second contract DB 104 stores contract information of the receiving company 120. The contract information includes attribute information such as the company name of the receiving company 120, information on the transfer destination account (actual account) of the receiving company 120, and the transfer person name set in the aggregated data 106. The transfer person name set in the aggregated data 106 is assigned to each paying company 110 so as to be a unique transfer requester name. The second contract DB 104 assigns a virtual account to the paying company 110 individually, and receives a contract for a service for transferring funds transferred to the virtual account by the paying company 110 to the real account of the receiving company 120. The second contract information of the company 120 is stored. The second contract information includes virtual account information associated with the real account of the receiving company 120 and associated with the individual paying company 110.

  The transfer request data 105 is a DB that stores transfer request data transmitted from the paying company 110 to the bank system 100. The transfer request data 105 may be any of the two types of data formats described above, but in this specification, for convenience of explanation, a data format for comprehensive transfer will be described as an example. Note that transfer request data that designates the transfer date as a specific future date may be stored in the transfer request data 105.

  The aggregated data 106 is aggregated data aggregated from the transfer request data 105 using the transfer destination account as a key, and is used for actual transfer processing.

  First transfer deposit details data 107 is transfer deposit details data generated as a result of the transfer process executed by the bank system 100. In the first deposit / payment details data 107, the deposit / payment details based on the aggregated data 106 are displayed.

  The second transfer receipt details data 108 is transfer receipt details data in which the transfer receipt details data based on the aggregated data included in the first transfer receipt details data 107 is replaced with individual detail data.

  Although not explicitly shown in FIG. 3, the bank system 100 includes a control unit, a main storage unit, an auxiliary storage unit, an I / F unit, and a display unit in addition to the above-described components, as in a general computer. Prepare.

  The control unit, also called a central processing unit (CPU), controls each component in the bank system 100 and calculates data, and reads various programs stored in the auxiliary storage unit into the main storage unit. Run. The main storage unit is also called a main memory, and stores various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit is a storage device typified by a hard disk (HDD) and is used when data and programs are stored for a long period of time.

  The I / F unit serves as an interface for transmitting and receiving data to and from other systems and devices, and provides an interface for receiving various commands and input data (such as various masters and tables) from the system operator. . The display unit provides a display screen for displaying the processed data.

  FIG. 4 is a diagram for explaining a detailed image of the transfer data handled by the paying company 110 and the aggregation server 101. The paying company 110 generates the transfer data 111 based on the invoice data received from the receiving company 120 by some means.

  FIG. 4 shows transfer data 111X generated based on a request from Company X. In the transfer data 111X, an account of the company X is designated as the transfer source account, the account of the transfer company A to the company E as the details of the transfer destination account, the transfer amount to each transfer account, and the bill related to each data Including the book number. Note that another account (for example, an account of a group company) associated with Company X may be designated as the transfer source account.

  FIG. 4 also shows transfer data 111Y and 111Z generated based on requests from the Y company and Z company, respectively. Similarly, in the transfer data 111Y, the account of the company Y is designated as the transfer source account, the details of the transfer destination account are the accounts of the transfer company A to the company C, the transfer amount to each transfer account, and the respective data. Including the relevant invoice number, the transfer data 111Z is specified as an account of the company Z as the transfer source account, the account of the transfer company C ~ E company as the details of the transfer destination account, the transfer amount to each transfer account, And the invoice number associated with each data.

  The paying company 110 transmits the transfer data 111X, the transfer data 111Y, and the transfer data 111Z to the bank system 100, and the transfer data 111 received by the bank system 100 is stored in the transfer request data 105.

  As another embodiment, company X, company Y, and company Z may generate the transfer data 111X, 111Y, and 111Z as described above and transmit them to the bank system 100, respectively.

  The aggregation server 101 reads the transfer data 111 from the transfer request data 105, identifies the detailed data with the same transfer destination account, and generates the integrated transfer data based on the identified detailed data. The generated aggregated transfer data is stored in the aggregated data 106. For example, the aggregation server 101 identifies detailed data in which the transfer destination account is an account of company A from the read transfer data 111X, 111Y, and 111Z, and generates aggregated transfer data. As shown in FIG. 4, in this aggregated transfer data, the account of company A is set as the transfer destination account, the total amount of the transfer amount of the detailed data identified as the transfer amount is set, and as the transfer person name The aggregation transfer person name extracted from the second contract DB 104 is set. As described above, the aggregation transfer person name to be set is stored in advance in the second contract DB 104 so as to be a unique transfer requester name.

  The aggregation server 101 performs processing for associating the aggregated data with the corresponding detailed data. For example, the aggregation server 101 can set an identifier such as a flag in both the aggregated data and the corresponding detailed data to indicate that they are associated with each other. Note that any type of identification code may be set as long as both can be associated with each other.

  The aggregation server 101 transfers the aggregated data (in the example of FIG. 4, transfer data for five cases where the transfer destination accounts are A company to E company) to a system that performs a transfer process in the bank system 100. The bank system 100 performs the transfer process based on the received aggregated data and generates first transfer deposit details data as shown in FIG. Data (for example, a flag) indicating the association between the aggregated transfer data and the corresponding detail data may be set in the first deposit details data.

  FIG. 5 is a diagram for explaining a process in which the disassembly server 102 generates second transfer deposit details data based on the first transfer deposit details data.

  The disassembly server 102 reads the first transfer deposit details data, and inquires of the second contract DB 104 whether or not the transfer person name included in the first transfer deposit details data is the transfer person name of the aggregated data. When it is determined that the transfer person name is for aggregation, the disassembling server 102 identifies aggregated data related to the first transfer deposit details data. Since the identified aggregated data includes data (for example, a flag) indicating the association between the aggregated data and the detailed data corresponding to the aggregated data, the disassembly server 102 determines that the aggregated data and the aggregated data Corresponding transfer request data is read from the aggregated data 106 and transfer request data 105.

  The disassembly server 102 replaces the transfer payment details based on the aggregated data in the first transfer payment details data with the transfer request data corresponding to the aggregated data (that is, the detail data before aggregation), and the second transfer deposit Generate detail data. For example, the transfer data (payment amount: 30000 yen, transfer name: FR11X) dated May 2, 2013 deposited in the account of Company A shown in FIG. The transfer data of 10,000 yen based on the invoice number 111 from the bank and the transfer data of 10,000 yen based on the invoice numbers 112 and 113 from the company Y are aggregated. The disassembly server 102 disassembles the transfer data dated May 2, 2013 deposited into the account of Company A into three detailed data as shown in FIG. 5, and generates the second transfer detailed payment data. To do. In this manner, as shown in FIG. 5, the disassembly server 102 replaces the transfer payment details based on the aggregated data, which are deposited in the accounts of the B company to the E company, with detailed data corresponding to the aggregated data. 2 transfer deposit details data is generated.

  As another embodiment, the disassembly server 102 uses the data (for example, a flag) indicating the association between the aggregated data and the corresponding detailed data stored in the first deposit / payment detailed data. The data and the corresponding transfer request data can be read from the aggregated data 106 and the transfer request data 105.

  The bank system 100 can transmit the first transfer deposit details data and the second transfer deposit details data in response to a request from the receiving company 120.

  FIG. 6 is a flowchart for explaining an embodiment of the transfer process executed in the bank system 100.

  In S <b> 601, the bank system 100 stores the transfer request data received from the paying company 110 in the transfer request data 105.

  In S602, the aggregation server 101 reads the transfer request data stored in the transfer request data 105, and identifies transfer request data to be transferred to the same transfer destination account using the transfer destination account as a key. The aggregation server 101 calculates the total amount of transfer amounts of the identified transfer request data, and generates aggregate data. As another embodiment, the transfer request data stored in the transfer request data 105 may be processed by excluding data in which the transfer date is set to the previous date. Processing of the excluded data is suspended until a predetermined date arrives.

  In S603, the aggregation server 101 makes an inquiry to the second contract DB 104, reads the transfer person name set in the transfer person name of the aggregate data, and sets it as the transfer person name of the aggregate data generated in S602.

  In S604, the aggregation server 101 sets an identifier (for example, a flag) for associating the aggregated data and the transfer request data that is the basis of the aggregated data with the aggregated data and the transfer request data, respectively. Stored in the aggregated data 106 and the transfer request data 105.

  In S605, the bank system 100 reads the transfer request data for which the identifier is not set in S604 from the transfer request data 105, and reads the aggregated data from the aggregated data 106, and executes the transfer process.

  In S <b> 606, the bank system 100 generates transfer deposit details data for each bank account, and stores it in the first deposit details data 107. Of the transfer deposit details data stored in the first deposit details data 107, the same identifier as that shown in S604 may be set in the transfer deposit details data based on the aggregated data.

  In step S <b> 607, the disassembly server 102 generates second transfer receipt details data from the first transfer receipt details data 107 and stores the second transfer receipt details data 108 in the second transfer receipt details data 108. More specifically, the disassembling server 102 reads the first transfer deposit details data, and inquires of the second contract DB 104 whether the transfer person name included in the first transfer receipt details data is the transfer person name of the aggregated data. . When it is determined that the transfer person name is for aggregation, the disassembling server 102 identifies aggregated data related to the first transfer deposit details data. Since the identified aggregated data includes an identifier indicating the association between the aggregated data and the detailed data, the disassembly server 102 determines the aggregated data and the corresponding transfer request data based on the identifier indicating the association. Are read out from the aggregated data 106 and the transfer request data 105. The disassembly server 102 replaces the transfer payment details based on the aggregated data in the first transfer payment details data with the transfer request data corresponding to the aggregated data (that is, the detail data before aggregation), and the second transfer deposit Generate detail data.

  As another embodiment, after identifying the identifier indicating the association as described above included in the first transfer deposit details data, the aggregated data and the corresponding transfer request data are extracted based on the identifier. As described above, the transfer deposit details based on the aggregated data in the first transfer deposit detail data are replaced with the transfer request data corresponding to the aggregated data (that is, the detail data before consolidation), and the second deposit Detailed data may be generated.

  FIG. 7 is a flowchart for explaining another embodiment of the transfer process executed in the bank system 100. In the present embodiment, a separate virtual account is assigned to each of the paying companies 110 by the receiving company 120, and the paying company 110 makes a transfer to the assigned virtual account and transfers it to the virtual account. The case where the funds are transferred to the corresponding real account of the receiving company 120 will be described.

  In S <b> 701, the bank system 100 stores the transfer request data received from the paying company 110 in the transfer request data 105.

  In S702, the aggregation server 101 reads the transfer request data stored in the transfer request data 105, and inquires of the second contract DB 104 whether or not the transfer destination account included in the transfer request data is a virtual account. . If it is determined that the account is a virtual account, the process proceeds to S703. If it is determined that the account is not a virtual account, the process proceeds to S602 in FIG.

  In S703, the aggregation server 101 reads the association information between the real account of the receiving company 120 and the virtual account assigned to the individual paying company 110 from the second contract DB 104, and uses the association information to obtain S702. After the virtual account included in the transfer request data read out in step 1 is replaced with a real account, transfer request data to be transferred to the same real account is identified using the real account as a key. The aggregation server 101 calculates the total amount of transfer amounts of the identified transfer request data, and generates aggregate data. As another embodiment, the transfer request data stored in the transfer request data 105 may be processed by excluding data in which the transfer date is set to the previous date. Processing of the excluded data is suspended until a predetermined date arrives.

  In S704, the aggregation server 101 makes an inquiry to the second contract DB 104, reads the transfer person name set in the transfer person name of the aggregated data, and sets it as the transfer person name of the aggregated data generated in S703.

  In S <b> 705, the aggregation server 101 sets an identifier (for example, a flag) for associating the aggregated data and the transfer request data that is the basis of the aggregated data with the aggregated data and the transfer request data, respectively. Stored in the aggregated data 106 and the transfer request data 105.

  In S706, the bank system 100 reads the transfer request data for which the identifier is not set in S705 from the transfer request data 105, reads the aggregated data from the aggregated data 106, and executes the transfer process for the virtual account. . Thereafter, the bank system 100 performs a transfer process from the virtual account to the corresponding real account. As another embodiment, the bank system 100 uses the association information between the real account and the virtual account read from the second contract DB 104 to perform the payment process on the virtual account without performing the deposit process on the virtual account. You may make it perform a transfer process.

  In S <b> 707, the bank system 100 generates transfer deposit details data for each real account and stores the transfer deposit details data 107 in the first transfer deposit details data 107. Among the transfer deposit details data stored in the first transfer deposit details data 107, the same identifier as shown in S705 may be set in the transfer deposit details data based on the aggregated data.

  In step S <b> 708, the disassembly server 102 generates second transfer receipt details data from the first transfer receipt details data 107 and stores the second transfer receipt details data 108 in the second transfer receipt details data 108. More specifically, the disassembling server 102 reads the first transfer deposit details data, and inquires of the second contract DB 104 whether the transfer person name included in the first transfer receipt details data is the transfer person name of the aggregated data. . When it is determined that the transfer person name is for aggregation, the disassembling server 102 identifies aggregated data related to the first transfer deposit details data. Since the identified aggregated data includes an identifier indicating the association between the aggregated data and the detailed data, the disassembly server 102 determines the aggregated data and the corresponding transfer request data based on the identifier indicating the association. Are read out from the aggregated data 106 and the transfer request data 105. The disassembly server 102 replaces the transfer payment details based on the aggregated data in the first transfer payment details data with the transfer request data corresponding to the aggregated data (that is, the detail data before aggregation), and the second transfer deposit Generate detail data.

  Here, in the embodiment described with reference to FIG. 6, the transfer source account number included in the second transfer deposit details data is the account of the paying company 110, but in the embodiment described with reference to FIG. The transfer source account number included in the transfer payment details data is a virtual account number individually assigned to the paying company 110. By displaying the virtual account number in the second transfer deposit details data, it becomes easier for the receiving company 120 to link the invoice data to the deposit, and the efficiency of office work increases.

  As another embodiment, after identifying the identifier indicating the association as described above included in the first transfer deposit details data, the aggregated data and the corresponding transfer request data are extracted based on the identifier. As described above, the transfer deposit details based on the aggregated data in the first transfer deposit detail data are replaced with the transfer request data corresponding to the aggregated data (that is, the detail data before consolidation), and the second deposit Detailed data may be generated.

  In the two embodiments described with reference to FIGS. 6 and 7, it has been described that the first and second transfer deposit details data are generated in advance in the bank system 100, but only the first transfer deposit details data is generated. Alternatively, the second transfer deposit details data may be generated in response to a request from the receiving company 120. In such a case, in response to receiving the request from the receiving company 120 in the internet banking system provided by the bank system 100 or receiving the first deposit details data, the bank system 100 2 transfer payment details data may be generated and transmitted to the receiving company 120. Further, a predetermined screen of the Internet banking system may be used to show the second transfer deposit details data to the receiving company 120.

  In the embodiment described above, the configuration in which the aggregation server 101 and the decomposition server 102 are included in the bank system 100 has been described, but the server may be implemented as a server outside the bank system 100.

  In the embodiment described above, it has been described on the assumption that both the transfer source account and the transfer destination account are in the same bank system. However, in another embodiment of the present invention, only the transfer source account is in the bank system. All you need to do is In such a case, since the information of the receiving company 120 is not stored in the second contract DB 104, the bank system 100 mechanically generates and sets the transfer person name set in the aggregation code so as to be unique. Will be kept. Thereafter, the bank system 100 receives the first transfer payment details data from the receiving company 120, and uses the transfer person name and the aggregated data included in the transfer payment details data and the association information of the corresponding details data, etc. 2 transfer payment details data can be generated and the second transfer payment details data can be transmitted to the receiving company 120.

  Although the principle of the present invention has been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the spirit of the present invention. Will understand. That is, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium.

100 Bank System 101 Aggregation Server 102 Disassembly Server 103 Contract DB
104 Second Contract DB
105 Transfer Request Data 106 Aggregated Data 107 First Transfer Payment Details 108 Second Transfer Payment Details 110 Paying Company (Computer)
111 Transfer data 120 Receiving company (computer)

Claims (7)

An aggregate data generation unit that generates aggregate data from a plurality of transfer data having a plurality of transfer account, wherein the aggregate data is data obtained by aggregating the transfer data for each transfer account, and the transfer destination look including a unique transfer names for the total amount and the aggregate data for transfer amount associated with the account, transfer data associated with the aggregated data and the aggregate data have a common identifier, and aggregate data generation unit,
A data decomposing unit that generates second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data indicate the receipt details for the transfer account. The first receipt details data includes receipt details data for the aggregate data generated as a result of transfer processing of the aggregate data, and the second receipt details data includes the aggregate data and the aggregate Based on the common identifier of the transfer data associated with the data, including payment details data obtained by replacing the payment details data for the aggregated data with the individual transfer data, and the second payment details data includes the first payment details data Identify related aggregated data by identifying that the transfer person name in the receipt details data is a unique transfer person name for the aggregated data , Based on the common identifier of the identified said aggregated data, the generated by identifying the individual of the transfer data associated with the aggregated data, transfer the data processing apparatus characterized by comprising a data decomposing unit . The transfer data processing apparatus according to claim 1 , further comprising contract information storage means for storing a unique transfer person name for the aggregated data. An aggregated data generating unit that generates aggregated data from a plurality of transfer data having a plurality of virtual accounts associated with a payer, wherein the aggregated data aggregates the transfer data for each real account associated with the virtual account An aggregate data generation unit that includes data and a total transfer amount associated with the virtual account and a unique transfer person name for the aggregate data;
A data decomposing unit that generates second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data are data indicating receipt details for the actual account. The first receipt details data includes receipt details data for the aggregate data generated as a result of the transfer processing of the aggregate data, and the second receipt details data includes the aggregate data and the aggregate data. Based on the information of the transfer data associated with the payment data, including the payment details data obtained by replacing the payment details data for the aggregated data with the individual transfer data, the second payment details data being associated with the individual transfer data is including an account number of the virtual account, transfer the data processing device, characterized in that it comprises a data decomposition section. 4. The transfer data processing apparatus according to claim 3 , wherein the information of the aggregate data and the transfer data associated with the aggregate data is an identifier included in the transfer data and the aggregate data. The transfer data processing apparatus according to claim 4 , further comprising contract information storage means for storing a unique transfer person name for the aggregated data and association information between the virtual account and the real account. A step of generating aggregated data from a plurality of transfer data having a plurality of transfer destination accounts, wherein the aggregated data is data obtained by aggregating the transfer data for each of the transfer destination accounts, and is associated with the transfer destination account look including the total amount and a unique transfer names for aggregated data transfer amount to be, transfer data associated with the aggregated data and the aggregate data have a common identifier, and a step,
Step of generating second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data are data indicating receipt details for the bank account. And the first receipt details data includes receipt details data for the aggregate data generated as a result of the transfer processing of the aggregate data, and the second receipt details data includes the aggregate data and the aggregate data. Based on the common identifier of the associated transfer data, it includes payment details data obtained by replacing the payment details data for the aggregated data with the individual transfer data, and the second payment details data is the first payment details. Identify the relevant aggregated data by identifying that the transferor name of the data is a unique transferor name for the aggregated data, Based on the common identifier of another said aggregated data, the generated by identifying the individual of the transfer data associated with the aggregated data, transfer the data processing method characterized by comprising the steps. Generating aggregated data from a plurality of transfer data having a plurality of virtual accounts associated with a payer, wherein the aggregated data is data obtained by aggregating the transfer data for each real account associated with the virtual account. And including a total transfer amount associated with the virtual account and a unique transfer person name for aggregate data;
Step of generating second receipt details data from the first receipt details data, wherein the first receipt details data and the second receipt details data are data indicating receipt details for the actual account. The first receipt details data includes receipt details data for the aggregate data generated as a result of the transfer processing of the aggregate data, and the second receipt details data is associated with the aggregate data and the aggregate data. Based on the information of the transfer data to be transferred, including payment details data obtained by replacing the payment details data for the aggregated data with the individual transfer data, the second payment details data being a virtual associated with the individual transfer data transfer data processing method which comprises the account account number, and a step.

Images