JP6254661B1 - Account management system, bank system, account management method and program - Google Patents

Abstract

An account management system, a bank system, an account management method, and a program capable of associating a virtual account and a real account after the occurrence of a transaction are provided. A virtual account management data storage unit 22 stores virtual account specifying data for specifying a plurality of virtual accounts that are not previously associated with a real account of a financial institution. The transaction occurrence confirmation unit 34 confirms the occurrence of a transaction that causes a claim for money. When the occurrence of the transaction is confirmed by the transaction occurrence confirmation unit 34, the virtual account determination unit 36 deals with any one or a plurality of virtual accounts among the plurality of virtual accounts identified based on the virtual account identification data. As a payment destination. The account associating unit 38 associates a real account that is to be deposited when a procedure for depositing money is performed by designating a virtual account to be determined. [Selection] Figure 9A

Description

  The present invention relates to an account management system, a bank system, an account management method, and a program.

  By establishing a virtual account associated with the real account of the money billing source for each money billing destination, the billing address where the money was deposited based on the account number of the virtual account where the money was deposited The technology that made it possible to grasp is known. In this technique, when a procedure for depositing money is performed by designating a virtual account, a deposit process is performed on a real account of a billing source associated with the virtual account.

  As an example using this technology, Patent Document 1 describes a debt collection support system that issues billing data in which a virtual account associated with a client company that is a billing source is designated as a deposit destination. In the claim collection support system described in Patent Document 1, billing data is output as a payment slip to which an account number of a virtual account associated with a billing source is added. Moreover, in the claim collection support system described in Patent Document 1, when there is a deposit to a virtual account, the deposit application process is performed by comparing the deposit data associated with the deposit with the above billing data. Then, the processing result is notified to the client company.

JP 2003-67583 A

  In the claim collection support system described in Patent Document 1, when a client company that is a billing source applies for the use of a virtual account to a bank, transfer-dedicated account number data associated with a real account of the billing source is given. When the client company that is the billing source charges a fee to the client user that is the billing destination, one of the account numbers set in the transfer-dedicated account number data is numbered. As described above, in the system described in Patent Document 1, the actual account of the billing source that is subjected to the deposit process when the deposit procedure of money specifying the virtual account is performed in the virtual account of the account number to be numbered. Associated.

  Assume that there is a shortage of available virtual accounts associated with the billing real account. In this case, in the claim collection support system described in Patent Document 1, the billing source applies for the use of a new virtual account to the bank, and the virtual account number cannot be assigned unless the new virtual account becomes available. Therefore, it takes time to issue billing data. Also, managing the remaining number of virtual accounts that can be used at the billing source takes time and effort for management.

  Here, in order to reduce the labor of the management, it is conceivable that the billing source makes many virtual accounts available in advance. However, this would incur an extra cost for the billing source to maintain a virtual account that is not expected to be used for the time being. In addition, in the bank system, extra resources are required to maintain a virtual account that is not expected to be used for the time being. Also, for example, when the bank system executes confirmation processing for the payment of all virtual accounts, confirmation processing is also performed for virtual accounts that do not need to be confirmed. The processing load increases.

  The present invention has been made in view of the above circumstances, and one of its purposes is to provide an account management system, a bank system, an account management method and a program capable of associating a virtual account and a real account after the occurrence of a transaction. It is to provide.

  In order to solve the above problems, an account management system according to the present invention includes a storage unit that stores virtual account specifying data for specifying a plurality of virtual accounts that are not previously associated with a real account of a financial institution, Confirmation means for confirming the occurrence of a transaction that causes a claim, and any one of a plurality of virtual accounts identified based on the virtual account identification data when the occurrence of the transaction is confirmed by the confirmation means Alternatively, a determination means for determining a plurality of virtual accounts as a payment destination in the transaction, and a real account to be processed when money is deposited by designating the determined virtual account, And an association means for associating with.

  In one aspect of the present invention, it further includes issuing means for issuing billing data in which the determined virtual account is designated as a deposit destination.

  In the aspect of the invention, the association unit changes the real account associated with the virtual account that satisfies a predetermined condition.

  In one aspect of the present invention, the information processing apparatus further includes a reception unit that receives from the bank system designation of a plurality of virtual accounts that are not previously associated with a real account of a financial institution, and the determination unit includes a plurality of designated units. One or a plurality of virtual accounts of the virtual accounts are determined, and the association means specifies a virtual account to be determined and when a money deposit procedure is performed, a real account to be processed for payment Is associated with the virtual account.

  In addition, the bank system according to the present invention is determined from output means for outputting designation of a plurality of virtual accounts not previously associated with a real account of a financial institution, and a plurality of the designated virtual accounts. A receiving means for receiving an instruction for associating one or a plurality of virtual accounts with a real account to be deposited when a money deposit procedure is performed by designating the virtual account; and according to the reception of the instructions Association means for associating the determined virtual account with the real account to be deposited.

  Further, the account management method according to the present invention includes a step of storing in a storage means virtual account specifying data for specifying a plurality of virtual accounts that are not previously associated with a real account of a financial institution, and a cause of claiming money And confirming the occurrence of the transaction and, when the occurrence of the transaction is confirmed, any one or a plurality of virtual accounts of the plurality of virtual accounts specified based on the virtual account specifying data in the transaction A step of determining as a payment destination, and a step of associating with the virtual account a real account that is to be subjected to a payment process when the determined virtual account is designated and money is deposited.

  Further, another account management method according to the present invention includes a step of outputting designation of a plurality of virtual accounts that are not previously associated with a real account of a financial institution, and is determined from among the plurality of designated virtual accounts A step of receiving an instruction to associate one or a plurality of virtual accounts and a real account to be deposited when a money deposit procedure is performed by designating the virtual account; And associating the determined virtual account with the real account to be deposited.

  In addition, the program according to the present invention is a procedure for storing virtual account specifying data for specifying a plurality of virtual accounts that are not previously associated with a real account of a financial institution in a storage means, a transaction that causes a claim for money. A procedure for confirming the occurrence, and when the occurrence of the transaction is confirmed, any one or a plurality of virtual accounts identified based on the virtual account identification data is determined as a payment destination in the transaction. And a procedure for associating the actual account to be deposited with the virtual account when the money depositing procedure is performed by designating the determined virtual account.

  Further, another program according to the present invention is determined from a procedure for outputting designation of a plurality of virtual accounts that are not previously associated with a real account of a financial institution, and one of the plurality of designated virtual accounts. Or a procedure for accepting an instruction associating a plurality of virtual accounts with a real account that is to be deposited when a procedure for depositing money is performed by designating the virtual account, and is determined according to acceptance of the instructions And causing the computer to execute a procedure for associating the virtual account with the real account to be deposited.

It is a figure which shows an example of the whole structure of the account management system which concerns on one Embodiment of this invention. It is a figure which shows an example of account related management data. It is a figure which shows an example of account related management data. It is a figure which shows an example of sales data. It is a figure which shows an example of claim data. It is a figure which shows an example of claim data. It is a figure which shows an example of seller master data. It is a figure which shows an example of supplier master data. It is a figure which shows an example of virtual account management data. It is a figure which shows an example of payment details data. It is a functional block diagram which shows an example of the function implemented by the accounting system which concerns on one Embodiment of this invention. It is a functional block diagram which shows an example of the function mounted by the bank system which concerns on one Embodiment of this invention. It is a flowchart which shows an example of the flow of the process performed in the accounting system which concerns on one Embodiment of this invention. It is a flowchart which shows an example of the flow of the process performed in the accounting system and bank system which concern on one Embodiment of this invention. It is a flowchart which shows an example of the flow of the process performed in the accounting system and bank system which concern on one Embodiment of this invention.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing an example of the overall configuration of an account management system 1 according to an embodiment of the present invention. As shown in FIG. 1, the account management system 1 according to the present embodiment includes an accounting system 10, a bank system 12, a plurality of seller terminals 14, and a plurality of deposit terminals 16. The accounting system 10, the bank system 12, the seller terminal 14, and the deposit terminal 16 are connected to a computer network 18 such as the Internet. Therefore, the accounting system 10, the bank system 12, the seller terminal 14, and the deposit terminal 16 can communicate with each other via the computer network 18.

  The accounting system 10 is a computer system such as a server computer in which accounting software is installed. The accounting system 10 includes, for example, a processor 10a, a storage unit 10b, a communication unit 10c, an output unit 10d, and an input unit 10e.

  The processor 10a is a program control device such as a CPU that operates according to a program installed in the accounting system 10, for example. The storage unit 10b is, for example, a storage element such as a ROM or a RAM, a hard disk drive, or the like. The storage unit 10b stores a program executed by the processor 10a. The communication unit 10c is a communication interface such as a network board that communicates with the bank system 12 and the seller terminal 14 via the computer network 18, for example. The output unit 10d is, for example, a display unit such as a display that displays and outputs information according to an instruction input from the processor 10a, and an audio output unit such as a speaker that outputs audio. The input unit 10e is, for example, a keyboard, a mouse, a microphone, or the like that outputs the content of an operation performed by the user to the processor 10a.

  The bank system 12 is a computer system such as a server computer that manages an account of a bank customer who is an administrator of the bank system 12, for example. The bank system 12 includes, for example, a processor 12a, a storage unit 12b, a communication unit 12c, an output unit 12d, and an input unit 12e.

  The processor 12a is a program control device such as a CPU that operates according to a program installed in the bank system 12, for example. The storage unit 12b is, for example, a storage element such as a ROM or a RAM, a hard disk drive, or the like. The storage unit 12b stores a program executed by the processor 12a. The communication unit 12 c is a communication interface such as a network board that communicates with the accounting system 10 and the deposit terminal 16 via the computer network 18, for example. The output unit 12d is, for example, a display unit such as a display that displays and outputs information according to an instruction input from the processor 12a, and an audio output unit such as a speaker that outputs audio. The input unit 10e is, for example, a keyboard, a mouse, a microphone, or the like that outputs the content of an operation performed by the user to the processor 12a.

  In the bank system 12 according to the present embodiment, two types of accounts, for example, a real account and a virtual account are managed. In the present embodiment, when a procedure for depositing money is performed by designating a virtual account, a deposit process for a real account associated with the virtual account is executed.

  The association between the virtual account and the real account is managed by the account association management data illustrated in FIGS. 2A and 2B. FIG. 2A shows one account-related management data, and FIG. 2B shows three account-related management data. FIG. 2A shows an example of account-related management data in a situation where virtual accounts with virtual account numbers 9000002 and 9000003 have not been opened (not activated). FIG. 2B shows an example of account-related management data in a situation after these virtual accounts are opened (activated).

  As shown in FIGS. 2A and 2B, the account related management data according to the present embodiment includes a virtual account number and a real account number. In this embodiment, when a procedure for depositing money is performed by designating a virtual account, a process of depositing the actual account number associated with the virtual account number of the virtual account in the account-related management data is executed. The Here, for example, money deposited in a virtual account may be transferred to a real account with a real account number associated with the virtual account number of the virtual account in the account-related management data. In this case, the transfer from the virtual account to the real account may be performed collectively at a predetermined timing, or may be performed every time there is payment to the virtual account.

  The seller terminal 14 is a computer such as a personal computer, a smartphone, or a tablet terminal used by a user who uses the accounting system 10.

  The deposit terminal 16 is a computer such as an automatic teller machine (ATM), a personal computer, a smartphone, and a tablet terminal for depositing into an account managed by the bank system 12.

  In the present embodiment, for example, a transaction that causes a charge for money occurs between the user of the accounting system 10 and another user. Specifically, for example, it is assumed that a user who is a business partner of the user purchases a product or service sold by the user of the accounting system 10 as a seller.

  In this case, it is assumed that the seller requests the issuance of billing data by registering the sales data illustrated in FIG. 3 corresponding to the transaction through the seller terminal 14 in the accounting system 10. Then, the accounting system 10 issues billing data illustrated in FIG. 4A and FIG. 4B with the seller as the billing source and the business partner as the billing destination.

  FIG. 3 shows three pieces of sales data. As shown in FIG. 3, the sales data according to the present embodiment includes, for example, a slip ID, a seller ID, a supplier ID, money amount data, summary data, application status data, and the like. The slip ID included in the sales data is, for example, identification information of the sales data. The seller ID included in the sales data is, for example, identification information of the seller in the transaction associated with the sales data, that is, the user of the accounting system 10. The supplier ID included in the sales data is, for example, the identification information of the supplier in the transaction associated with the sales data. The amount data included in the sales data is, for example, data indicating the amount of sales associated with the sales data. The summary data included in the sales data is data indicating the contents of a transaction associated with the sales data, such as the name of a sold product or service. The application status data included in the sales data is, for example, data indicating whether or not payment of money corresponding to a charge in a transaction associated with the sales data has been confirmed. In this embodiment, for example, “completed” is set as the application status data included in the sales data of sales for which payment of money has been confirmed, and application status data included in the sales data of sales for which payment of money has not been confirmed Is set to “not yet”.

  FIG. 4A shows an example of billing data associated with sales data with a slip ID of 0002, and FIG. 4B shows an example of billing data associated with sales data with a slip ID of 0003.

  The data format of billing data is not particularly limited. For example, the billing data may be in text format or PDF format.

  The billing data issuance format is not particularly limited. For example, a recording medium such as paper on which the contents of the billing data are recorded may be printed out from a printer provided in the seller terminal 14. In this case, the seller who is the billing source may mail the billing data printed to the customer who is the billing destination. Further, for example, an e-mail including billing data may be transmitted to the e-mail address of the business partner.

  As shown in FIGS. 4A and 4B, the billing data according to the present embodiment includes, for example, bill number I1, billing source information I2, billing destination information I3, billing amount information I4, item information I5, and transfer destination. Account number I6 is included.

  Here, as the invoice number I1 included in the billing data, for example, a slip ID included in the sales data associated with the billing data is set. In addition, as the billing source information I2 included in the billing data, for example, the name of the seller associated with the seller ID included in the sales data associated with the billing data is set. In addition, as the billing destination information I3 included in the billing data, for example, the name of the trading partner associated with the business partner ID included in the sales data associated with the billing data is set. In addition, as the billing amount information I4 included in the billing data, for example, the value of the amount data included in the sales data associated with the billing data is set. Further, as the item information I5 included in the billing data, for example, the value of summary data included in the sales data associated with the billing data is set.

  Note that the name of the seller set as the billing source information I2 is specified based on, for example, the seller master data illustrated in FIG. FIG. 5 shows two pieces of merchant master data. As shown in FIG. 5, the seller master data includes, for example, the seller ID of the seller, name data indicating the name of the seller, and the account number of the seller's real account. . Here, in the present embodiment, it is assumed that a real account of the account number has already been opened in the bank that manages the bank system 12.

  Further, the name of the supplier set as the billing destination information I5 can be specified based on, for example, the supplier master data illustrated in FIG. FIG. 6 shows three supplier master data. As shown in FIG. 6, the supplier master data indicates, for example, a supplier ID that is identification information of a supplier of one or a plurality of sellers registered in the accounting system 10, and a name of the supplier. Name data, etc. are included.

  In this embodiment, for example, the account number of the seller's real account is not set as the transfer account number I6 included in the billing data. Instead, in this embodiment, for example, as the transfer account number I6 included in the billing data, the account number of the virtual account specified based on the combination of the seller ID and the customer ID associated with the billing data is Is set.

  Here, the account number of the virtual account set as the transfer destination account number I6 is specified based on, for example, virtual account management data illustrated in FIG. FIG. 7 shows 50 virtual account management data. As shown in FIG. 7, the virtual account management data according to the present embodiment includes, for example, a virtual account number, a seller ID, a supplier ID, and opening status data.

  In the present embodiment, for example, the range of virtual account numbers that can be used in the accounting system 10 is notified from the bank system 12 to the accounting system 10. When the accounting system 10 receives the notification of the range of the virtual account numbers from the bank system 12, for example, it generates virtual account management data associated with each of the virtual account numbers belonging to the range. At this stage, a virtual account associated with a virtual account number belonging to the range is not opened in the bank system 12.

  Here, for example, a list of virtual account numbers including one or more virtual account numbers themselves available in the accounting system 10 may be notified from the bank system 12 to the accounting system 10. In this case, the accounting system 10 generates virtual account management data associated with the virtual account number notified from the bank system 12. Further, the virtual account number notified in this case does not need to be a serial number.

  The opening status data included in the virtual account management data is data indicating whether or not a virtual account associated with the virtual account management data is opened in the bank system 12. In the present embodiment, for example, “not established” is set as the value of the establishment status data included in the virtual account management data associated with the virtual account that has not been established. In this embodiment, since the virtual account associated with the virtual account management data is not opened at the timing when the virtual account management data is generated, in the initial state, the value of the opening status data included in the virtual account management data is “unopened” Opening "will be set. In the initial state, the values of the seller ID and the customer ID included in the virtual account management data are empty.

  In this embodiment, the value of the seller ID and the customer ID is empty and the value of the opening status data is “not yet opened” in response to the occurrence of a transaction in a new combination of the seller and the customer. One or more of the account management data is selected. Then, the seller ID of the seller in the transaction is set as the seller ID included in the selected virtual account management data, and the supplier of the supplier in the transaction as the supplier ID included in the selected virtual account management data An ID is set. Further, the value of the opening status data included in the selected virtual account management data is changed to “opening”. Then, the accounting system 10 transmits a virtual account opening instruction associated with the virtual account management data to the bank system 12. The timing at which the virtual account opening instruction is transmitted is not particularly limited. For example, it may be the timing at which sales data is registered or the timing at which billing data is issued.

  In the present embodiment, the bank system 12 opens a virtual account, for example, in response to receiving an opening instruction transmitted from the accounting system 10. In the present embodiment, for example, a virtual account number to be opened and a real account number are associated with the opening instruction. In this embodiment, the account related management data illustrated in FIGS. 2A and 2B is generated when a virtual account is opened.

  For example, assume that the account-related management data is in the state shown in FIG. 2A. Here, it is assumed that the bank system 12 receives an opening instruction associated with the virtual account number 9000002 and the real account number 1000001. Further, it is assumed that the bank system 12 receives an opening instruction associated with the virtual account number 9000003 and the real account number 1000002. In this case, as shown in FIG. 2B, account related management data including a combination of virtual account number 9000002 and real account number 1000001 and account related management data including a combination of virtual account number 9000003 and real account number 1000002 are generated. The Rukoto.

  Note that the account-related management data according to the present embodiment does not include information related to the billing destination in the billing data. Therefore, the establishment instruction received from the accounting system 10 does not need to be associated with information related to the billing destination in the billing data such as the business partner ID.

  When the opening of the virtual account and the generation of the account-related management data are completed, the bank system 12 transmits an opening process end notification indicating that the opening process of the virtual account has ended to the accounting system 10. When the accounting system 10 receives the opening processing end notification, for example, the accounting system 10 changes the value of the opening status data included in the virtual account management data associated with the virtual account to “opened”.

  Here, for example, it is assumed that the business partner who has received the issued billing data has performed a deposit procedure for the account indicated in the billing data from the depositing terminal 16 with the amount of money indicated in the billing data. In this case, the bank system 12 executes a process of depositing the amount of money in the real account associated with the virtual account for which the deposit procedure has been performed. Here, the bank system 12 may execute a transfer process in which money deposited in the virtual account is transferred to the real account of the billing source.

  In the present embodiment, for example, according to the deposit process of money to the real account, the bank system 12 receives the payment details data illustrated in FIG. Sent to system 10.

  FIG. 8 shows two deposit details data. As shown in FIG. 8, the payment details data includes, for example, a real account number, a payment virtual account number, payer name data, and payment amount data. The actual account number included in the deposit details data is, for example, the account number of the actual account on which the deposit process has been executed. The deposit virtual account number is, for example, the account number of the virtual account on which the deposit procedure has been performed. The payer name data is data indicating the name of the payer designated at the deposit terminal 16 when depositing into the virtual account. The deposit amount data is data indicating the amount designated at the time of deposit procedure to the virtual account.

  For example, when money transfer processing from a virtual account to a real account is performed collectively at a predetermined timing such as a predetermined time every day, payment details data associated with each of a plurality of transfers performed collectively is received from the bank system 12. It is transmitted to the accounting system 10.

  When receiving the payment details data, the accounting system 10 executes, for example, sales data clearing processing. Here, for example, virtual account management data including the value of the deposit virtual account number included in the deposit details data as the value of the virtual account number may be specified. And, for example, if there is one piece of sales data that includes the seller ID and business partner ID included in the specified virtual account management data and the value of the application status data is “not yet”, the sales data The value of the consumption status data included may be changed to “Done”. Here, for example, when there are a plurality of sales data including the seller ID and the business partner ID included in the specified virtual account management data and the value of the application status data is “not yet”, the seller You may make it notify that to the seller terminal 14 of the seller corresponding to ID. Note that the sales data consumption process is not limited to the above-described process, and other known methods may be used.

  As described above, in the present embodiment, a virtual account associated with the real account of the money billing source is provided for each money billing destination, and the payment virtual account number is included in the payment detail data. Therefore, in this embodiment, based on the account number of the virtual account where money was deposited, the billing destination that deposited the money can be accurately grasped.

  Further, in the present embodiment, when a transaction occurs in a combination of a seller and a business partner that has not been traded until now, a virtual associated with the combination of the seller and the business partner is generated according to the occurrence of the transaction. An account number for the account is assigned. Then, the virtual account is associated with the seller's real account so that the virtual account is opened. Thus, according to the present embodiment, the virtual account and the seller's real account can be associated after the transaction occurs.

  In the present embodiment, the billing data can be issued even in a situation where the virtual account is not associated with the seller's real account. Therefore, in the present embodiment, it is possible to prevent the occurrence of a situation where it takes time to issue billing data due to a lack of available virtual accounts associated with the seller's real account. In the present embodiment, the seller does not need to manage the remaining number of available virtual accounts in order to prevent a shortage of available virtual accounts associated with the seller's real account. Therefore, in this embodiment, the trouble of managing the virtual account by the seller is reduced.

  Further, in the present embodiment, it is not necessary to manage a virtual account whose billing destination is undetermined in the bank system 12 in association with a real account, and only a virtual account that is likely to be deposited when a transaction occurs is associated with the real account. It is enough to manage. Therefore, in this embodiment, the number of opened virtual accounts associated with real accounts can be minimized.

  In the present embodiment, it is not necessary for the seller to make many virtual accounts available in advance. Therefore, in this embodiment, there is no extra cost for maintaining a virtual account that is not expected to be used for the time being by the seller. In this embodiment, the bank system 12 does not require resources for maintaining a virtual account that is not expected to be used for the time being. In addition, since the number of opened virtual accounts associated with real accounts is minimized, for example, even when the bank system 12 executes confirmation processing for the presence / absence of payment for all virtual accounts, the confirmation processing The processing load is reduced.

  Hereinafter, functions of the accounting system 10 and the bank system 12 according to the present embodiment and processing executed by the accounting system 10 and the bank system 12 according to the present embodiment will be further described.

  FIG. 9A is a functional block diagram illustrating an example of functions implemented in the accounting system 10 according to the present embodiment. Note that in the accounting system 10 according to the present embodiment, not all of the functions shown in FIG. 9A need be implemented, and functions other than the functions shown in FIG. 9A may be implemented.

  As shown in FIG. 9A, the accounting system 10 according to the present embodiment functionally includes, for example, a master data storage unit 20, a virtual account management data storage unit 22, a sales data storage unit 24, a virtual account designation receiving unit 26, Virtual account management data generation unit 28, request reception unit 30, sales data registration unit 32, transaction occurrence confirmation unit 34, virtual account determination unit 36, account association unit 38, billing data issuance unit 40, payment details data reception unit 42, consumption Include a process execution unit 44.

  The master data storage unit 20, the virtual account management data storage unit 22, and the sales data storage unit 24 are mainly implemented by the storage unit 10b. The virtual account designation receiving unit 26, the request receiving unit 30, the deposit details data receiving unit 42, and the communication unit 10c are mainly mounted. The virtual account management data generation unit 28, the sales data registration unit 32, the transaction occurrence confirmation unit 34, the virtual account determination unit 36, and the application process execution unit 44 are mainly implemented by the processor 10a. The account association unit 38 and the billing data issuing unit 40 are mainly implemented by the processor 10a and the communication unit 10c.

  The above functions may be implemented by causing the processor 10a to execute a program including instructions corresponding to the above functions, installed in the accounting system 10 which is a computer. This program is supplied to the accounting system 10 via a computer-readable information storage medium such as an optical disk, a magnetic disk, a magnetic tape, or a magneto-optical disk, or via the Internet.

  FIG. 9B is a functional block diagram showing an example of functions implemented in the bank system 12 according to the present embodiment. In the bank system 12 according to the present embodiment, not all the functions shown in FIG. 9B need be implemented, and functions other than the functions shown in FIG. 9B may be implemented.

  As shown in FIG. 9B, the bank system 12 according to the present embodiment functionally includes, for example, an account related management data storage unit 50, a virtual account designation output unit 52, an opening instruction reception unit 54, a virtual account opening unit 56, A deposit procedure receiving unit 58, a deposit process execution unit 60, a deposit details data generating unit 62, and a deposit details data transmitting unit 64 are included.

  The account related management data storage unit 50 is mainly implemented by the storage unit 12b. The virtual account designation output unit 52, the opening instruction reception unit 54, the payment procedure reception unit 58, and the payment details data transmission unit 64 are mainly implemented by the communication unit 12c. The deposit process execution unit 60 and the deposit details data generation unit 62 are mainly implemented by the processor 12a. The virtual account opening unit 56 is mainly implemented by the processor 12a and the communication unit 12c.

  The above functions may be implemented by executing a program including instructions corresponding to the above functions installed in the bank system 12 that is a computer by the processor 12a. This program is supplied to the bank system 12 via a computer-readable information storage medium such as an optical disk, a magnetic disk, a magnetic tape, or a magneto-optical disk, or via the Internet.

  In this embodiment, the master data storage unit 20 stores, for example, merchant master data illustrated in FIG. 5 and supplier master data illustrated in FIG.

  In this embodiment, the virtual account management data storage unit 22 stores, for example, virtual account management data illustrated in FIG. The virtual account management data according to the present embodiment includes, for example, virtual account identification data (a virtual account number in the example of FIG. 7) that identifies a plurality of virtual accounts that are not previously associated with a real account of a financial institution. It is.

  In the present embodiment, the sales data storage unit 24 stores, for example, sales data illustrated in FIG.

  In this embodiment, for example, the virtual account designation receiving unit 26 receives from the bank system 12 designation of a plurality of virtual accounts that can be used in the accounting system 10 that is not associated with a real account of a financial institution in advance. Here, the virtual account designation receiving unit 26 may receive from the bank system 12 a range of account numbers of virtual accounts that can be used in the accounting system 10. The virtual account designation receiving unit 26 may receive a list of virtual account numbers including one or a plurality of virtual account numbers themselves that can be used in the accounting system 10 from the bank system 12.

  In this embodiment, for example, the virtual account management data generation unit 28 generates virtual account management data illustrated in FIG. 7 and stores the virtual account management data in the virtual account management data storage unit 22. Here, the virtual account management data generation unit 28 may generate virtual account management data corresponding to the virtual account for which the virtual account designation receiving unit 26 has received the designation. For example, it is assumed that the virtual account designation receiving unit 26 receives a range of account numbers from 9000001 to 9000050. In this case, the virtual account management data generation unit 28 may generate 50 virtual account management data each including any number from 9000001 to 9000050 as a virtual account number. For example, it is assumed that the virtual account designation receiving unit 26 receives a list of virtual account numbers. In this case, the virtual account management data generation unit 28 may generate virtual account management data associated with each of the virtual account numbers included in this list. The virtual account management data generation unit 28 may generate virtual account management data in which the values of the seller ID and the supplier ID are empty and the value of the opening status data is “not yet opened”.

  In the present embodiment, for example, the request receiving unit 30 receives a request for processing to be executed by the accounting system 10 from the seller terminal 14. Here, for example, the request receiving unit 30 may receive a sales registration request or a purchase data issue request.

  In the present embodiment, for example, the sales data registration unit 32 generates sales data illustrated in FIG. 3 and stores the sales data in the sales data storage unit 24. Here, the sales data registration unit 32 may generate sales data in response to receiving the sales registration request.

  In the present embodiment, the transaction occurrence confirmation unit 34 confirms, for example, the occurrence of a transaction that causes a claim for money. The transaction occurrence confirmation unit 34 may confirm sales data newly registered at predetermined time intervals, for example. Further, the transaction occurrence confirmation unit 34 may monitor registration of new sales data, for example. In this case, for example, at the timing when the sales data is registered, the occurrence of a transaction that causes a claim for money is confirmed. Further, the transaction occurrence confirmation unit 34 may specify each seller ID and supplier ID of the newly registered sales data. Further, the transaction occurrence confirmation unit 34 may specify the number of newly registered sales data as the number of transactions that have occurred.

  When the occurrence of a transaction is confirmed by the transaction occurrence confirmation unit 34, the virtual account determination unit 36 determines a virtual account that is a deposit destination in the transaction. Here, the virtual account determination unit 36 determines any one or a plurality of virtual accounts among the plurality of virtual accounts when the transaction generation confirmation unit 34 confirms the occurrence of the transaction that causes the billing of money. May be. Further, the virtual account determination unit 36 may select any one or more of virtual account management data in which the values of the seller ID and the supplier ID are empty, for example. The virtual account determination unit 36 may select a virtual account corresponding to the transaction, that is, a virtual account used in the transaction when the occurrence of the transaction that causes the billing of money is confirmed.

  In this embodiment, for example, the account associating unit 38 associates, with the virtual account, a real account that is to be deposited when a virtual account to be elected is designated and money is deposited.

  Here, for example, the account association unit 38 checks whether or not there is virtual account management data including the seller ID and the customer ID specified by the transaction occurrence confirmation unit 34 as the seller ID and the customer ID, respectively. May be. If such virtual account management data does not exist, the account association unit 38 identifies the seller identified by the transaction occurrence confirmation unit 34 as one of the seller IDs and supplier IDs of the selected virtual accounts. You may set ID and supplier ID.

  Further, the account association unit 38 may transmit a virtual account opening instruction to the bank system 12. The opening instruction may include an instruction for associating a real account that is to be deposited when a virtual account to be elected is designated and a deposit process is performed with the virtual account. . For example, the account association unit 38 may transmit to the bank system 12 a virtual account opening instruction corresponding to the virtual account number included in the virtual account management data in which the seller ID and the business partner ID are set.

  Here, the account association unit 38 is, for example, the virtual account number included in the virtual account management data in which the seller ID and the business partner ID are set, and the real account associated with the seller ID in the seller master data. The opening instruction including the account number may be transmitted.

  It should be noted that it is not necessary to determine in advance which merchant and trader are assigned the virtual account that is selected when the occurrence of a transaction that causes a claim for money is confirmed. For example, the virtual account determination unit 36 may secure the number of virtual accounts specified as the number of transactions generated by the transaction occurrence confirmation unit 34. After that, the account association unit 38 determines a seller and a business partner who use the secured virtual account, and corresponds the seller ID of the seller and the business partner ID of the business partner to the secured virtual account. The virtual account management data may be set.

  The billing data issuing unit 40 issues billing data illustrated in FIGS. 4A and 4B. Here, for example, the billing data issuing unit 40 may issue billing data in response to receipt of a purchase data issuing request.

  For example, it is assumed that the billing data issuing unit 40 receives a request for issuing billing data associated with sales data, for example. In this case, the billing data issuing unit 40 specifies a slip ID included in the sales data. Further, the billing data issuing unit 40 specifies the value of the name data associated with the seller ID included in the sales data in the seller master data. Further, the billing data issuing unit 40 specifies the value of the name data associated with the supplier ID included in the sales data in the supplier master data. Further, the billing data issuing unit 40 specifies the amount data and summary data values included in the sales data. Further, the billing data issuing unit 40 specifies a virtual account number associated with a combination of a seller ID and a business partner ID included in the sales data in the virtual account management data.

  Then, the billing data issuing unit 40 generates billing data based on these specified values. In the billing data generated here, the specified slip ID is set as the bill number I1. In addition, a value of name data associated with the identified seller ID is set as billing source information I2. Moreover, the value of the name data matched with the specified trader ID is set as the billing destination information I3. Further, the value of the specified amount data is set as billing amount information I4. Further, the value of the specified summary data is set as the item information I5. Further, the identified virtual account number is set as the transfer destination account number I6.

  In the present embodiment, for example, the deposit details data receiving unit 42 receives the deposit details data illustrated in FIG. 8 from the bank system 12.

  In the present embodiment, for example, the application process execution unit 44 executes the sales data application process described above based on the received payment details data.

  In the present embodiment, the account-related management data storage unit 50 stores, for example, account-related management data illustrated in FIGS. 2A and 2B.

  In this embodiment, for example, the virtual account designation output unit 52 outputs designation of a plurality of virtual accounts that are not previously associated with a real account of a financial institution. Here, the virtual account designation output unit 52 may transmit the range of the account numbers of the virtual accounts that can be used in the accounting system 10 to the accounting system 10.

  In the present embodiment, for example, the opening instruction reception unit 54 receives a virtual account opening instruction from the accounting system 10. As described above, the opening instruction includes an instruction for associating a real account to be deposited with the virtual account when a procedure for depositing money is performed by designating a virtual account to be elected. It may be.

  In this embodiment, for example, the virtual account opening unit 56 executes a virtual account opening process (activation process) that has received an opening instruction. Here, the opening process may include, for example, a process of generating new account related management data and storing it in the account related management data storage unit 50. Here, for example, account-related management data including each of the virtual account number and the real account number associated with the accepted opening instruction as the virtual account number and the real account number may be generated.

  Further, the virtual account opening unit 56 may transmit an opening process end notification to the accounting system 10 when the execution of the virtual account opening process is completed. Then, the account association unit 38 may change the value of the opening status data of the virtual account management data corresponding to the virtual account for which the opening process has been executed to “opened” in response to the reception of the opening process end notification.

  In this embodiment, the deposit procedure accepting unit 58 accepts, from the deposit terminal 16, for example, a deposit procedure for money in which a virtual account, a payer name, and a deposit amount are specified.

  In the present embodiment, for example, the deposit process execution unit 60 executes a deposit process according to the accepted deposit procedure. Here, for example, the deposit processing execution unit 60 may once execute the deposit processing to the virtual account and then transfer to the real account associated with the virtual account in the account related management data. Moreover, the deposit process execution part 60 may perform the deposit process to the real account linked | related with the virtual account designated in the deposit procedure in account related management data, for example. In addition, the content of the deposit process by the transfer that designates the virtual account by the payer in this embodiment is not limited to a specific process, and the content of the process is particularly a deposit process according to the embodiment of the virtual account. Does not matter.

  In the present embodiment, for example, the payment details data generation unit 62 generates payment details data corresponding to the executed payment processing. The receipt details data generation unit 62, for example, the real account number of the real account on which the deposit process has been executed, the virtual account number of the virtual account designated in the deposit procedure, the name of the payer designated in the deposit procedure, and the deposit Each amount of money may be specified. And the payment details data generation part 62, for example, specifies each of the specified real account number, virtual account number, payer name, payment amount, real account number, virtual account number, payer name data value, and You may produce | generate the receipt description data included as a value of deposit amount data.

  In this embodiment, for example, the payment details data transmission unit 64 transmits the payment details data generated by the payment details data generation unit 62 to the accounting system 10.

  Hereinafter, an example of a flow of processing related to sales data registration and billing data issuance executed in the accounting system 10 will be described with reference to a flowchart shown in FIG. At the start of the following processing example, the value of the seller ID and the business partner ID included in the virtual account management data whose virtual account number is 9000003 is empty, and the value of the opening status data is “not yet opened” And Further, at the start of the following processing example, it is assumed that the sales data whose slip ID is 0003 illustrated in FIG. 3 is not stored in the sales data storage unit 24.

  First, it is assumed that the request receiving unit 30 receives a sales registration request (S101).

  Then, the sales data registration unit 32 registers the sales data associated with the sales registration request received in the process shown in S101 (S102). Here, for example, sales data whose slip ID is 0003 illustrated in FIG. 3 is generated and stored in the sales data storage unit 24. Then, the transaction occurrence confirmation unit 34 confirms the occurrence of a transaction corresponding to the sales data (S103).

  Then, the virtual account determination unit 36 determines whether or not a virtual account corresponding to the combination of the seller and the business partner indicated in the sales data exists (S104). Here, for example, it is determined whether or not virtual account management data including 002 as the seller ID and 103 as the supplier ID is stored in the virtual account management data storage unit 22.

  If it is determined that it does not exist (S104: N), the virtual account determination unit 36 selects one of the virtual account management data in which the values of the seller ID and the supplier ID are empty (S105). ). Here, for example, virtual account management data having a virtual account number of 9000003 is selected.

  Then, the account association unit 38 sets the seller ID and customer ID of the virtual account management data corresponding to the virtual account selected in the process shown in S105 (S106). Here, for example, the seller ID and customer ID included in the sales data registered in the process shown in S102 are set as the seller ID and customer ID of the virtual account management data whose virtual account number is 9000003.

  Then, the account association unit 38 transmits to the bank system 12 a virtual account opening instruction corresponding to the virtual account management data in which the seller ID and the customer ID are set in the process shown in S106 (S107). For example, a virtual account number 9000003 and a real account number 1000002 are associated with the opening instruction. Then, the account association unit 38 changes the value of the opening status data of the virtual account management data corresponding to the virtual account selected in the process shown in S105 to “opening” (S108).

  Here, when it is determined in the process shown in S104 (S104: Y) or when the process shown in S108 is completed, the request receiving unit 30 corresponds to the sales data registered in the process shown in S102. Assume that a request for issuing billing data is received (S109). Then, the billing data issuing unit 40 generates billing data illustrated in FIG. 4B corresponding to the sales data whose slip ID is 0003 (S110). Then, the billing data issuing unit 40 issues the billing data generated in the processing shown in S109 (S111), and the processing shown in this processing example is ended.

  As described above, in this processing example, even when a virtual account is not opened, that is, when a procedure for depositing money is performed by designating a virtual account, an association between the actual account to be deposited and the virtual account is performed. Even if it is not made, it is possible to issue billing data with the virtual account as the transfer destination.

  Next, an example of the flow of processing related to the opening of a virtual account executed in the bank system 12 and the accounting system 10 will be described with reference to the flowchart shown in FIG. Note that at the start of the following processing example, it is assumed that the account related management data whose virtual account number is 9000003 is not stored in the account related management data storage unit 50.

  First, it is assumed that the opening instruction reception unit 54 receives from the accounting system 10 the opening instruction for the virtual account transmitted in the process shown in S107 described above (S201). Then, the virtual account opening unit 56 executes a virtual account opening process that has received the opening instruction (S202). Here, for example, generation of account-related management data including 9000003 as the virtual account number and including 1000002 as the real account number, and storing the account-related management data in the account-related management data storage unit 50 are also part of the opening process. Run as.

  When the execution of the opening process ends, the virtual account opening unit 56 transmits an opening process end notification associated with the virtual account number of the opened virtual account to the accounting system 10 (S203).

  Then, in response to receipt of the opening process end notification, the account association unit 38 changes the value of the opening status data of the virtual account management data including the virtual account number associated with the opening process end notification to “opened”. (S204), and the processing shown in this processing example ends.

  Next, an example of the flow of processing relating to payment executed in the bank system 12 and the accounting system 10 will be described with reference to the flowchart shown in FIG.

  First, it is assumed that the deposit procedure accepting unit 58 has accepted a deposit procedure for money (S301). Here, in the deposit procedure, it is assumed that 9000003 is designated as the virtual account number, “B3 Corporation” is designated as the payer name, and 20,000 yen is designated as the deposit amount.

  Then, the payment process execution part 60 specifies the real account linked | related with the virtual account designated in the payment procedure received by the process shown to S301 (S302). Here, for example, 1000002 which is the real account number of the real account associated with the virtual account whose virtual account number is 9000003 is specified.

  Then, the depositing process execution unit 60 executes the depositing process to the real account specified in the process shown in S302 (S303).

  Then, the payment details data generation unit 62 generates payment details data corresponding to the payment processing executed in the processing shown in S303 (S304). Here, for example, payment details data including 1000002 as the real account number and 9000003 as the payment virtual account number shown in FIG. 8 is generated.

  Then, the payment details data transmission unit 64 transmits the payment details data generated by the process shown in S304 to the accounting system 10 (S305).

  Then, the account association unit 38 of the accounting system 10 executes an application process based on the received payment details data (S306), and the process shown in this process example is completed. Here, for example, the value of the consumption status data of the sales data whose slip ID is 0003 may be changed to “Done”.

  In addition, this invention is not limited to the above-mentioned embodiment.

  For example, in the above-described embodiment, a virtual account is assigned for each combination of a seller and a business partner, but a virtual account may be assigned for each transaction. In this case, the virtual account management data may further include a slip ID. In this case, for example, it is not necessary to execute the process shown in S104 illustrated in FIG. 10, and the virtual account management data to which the seller ID and the business partner ID are not assigned every time sales data is registered. Either of these may be elected. Then, the slip ID, the seller ID, and the supplier ID included in the registered sales data may be set as the slip ID, the seller ID, and the supplier ID of the selected virtual account management data. Further, in this case, in response to acceptance of a request for issuing billing data corresponding to sales data, the virtual account number associated with the slip ID of the sales data in the virtual account management data is set as the transfer account number I6. Data may be issued.

  In addition, for example, a virtual account determination program that determines a virtual account that is a deposit destination in a transaction that causes money billing may be installed in the accounting system 10. The virtual account determination program may be stored in the storage unit 10b of the accounting system 10. The virtual account determination program may include virtual account specifying data for specifying a plurality of virtual accounts that are not previously associated with the actual account of the financial institution. Here, as an example of the virtual account specifying data, a list of virtual account numbers of a plurality of virtual accounts not previously associated with a real account of a financial institution, or data indicating a range of virtual account numbers of the plurality of virtual accounts Etc. The virtual account specifying data may be data indicating a condition (for example, a 7-digit number starting with 9) to be satisfied by a plurality of virtual accounts specified based on the virtual account specifying data. The virtual account determination program may include upper limit number data indicating the upper limit number of virtual accounts that can be determined as a deposit destination in the transaction.

  The virtual account determination program may be provided from a bank that is an administrator of the bank system 12. Here, it is assumed that the bank system 12 is used by a plurality of accounting systems 10. In this case, the virtual account determination program installed in each of the plurality of accounting systems 10 may be set so that the virtual accounts specified based on the virtual account specifying data do not overlap each other.

  Then, the accounting system 10 may execute the virtual account determination program when the occurrence of the transaction that causes the billing of money is confirmed. And any one or a plurality of virtual accounts of a plurality of virtual accounts specified based on virtual account specification data contained in the virtual account determination program may be determined as a payment place in the transaction. Further, the accounting system 10 may determine a virtual account with the upper limit number indicated by the above-described upper limit number data as the upper limit.

  Then, the accounting system 10 obtains the virtual account number of the determined virtual account, the seller ID of the seller in the transaction, the supplier ID of the customer in the transaction, and the opening status data whose value is “not opened”. Including virtual account management data may be generated. Then, the accounting system 10 may transmit to the bank system 12 an instruction to open a virtual account determined as a deposit destination in the transaction.

  The accounting system 10 does not need to execute the virtual account determination program at the timing when the occurrence of the transaction is confirmed. For example, the accounting system 10 may execute a virtual account determination program in advance to determine a candidate for a deposit destination. Then, the accounting system 10 may determine the candidate virtual account as a payment destination in the transaction when the occurrence of the transaction that causes the billing of money is confirmed.

  As described above, after the accounting system 10 associates the actual account of the seller in the transaction with the virtual account determined by the virtual account determination program, the bank system 12 recognizes the account number of the virtual account. You may do it.

  Further, for example, the account association unit 38 may change a real account associated with a virtual account that satisfies a predetermined condition.

  For example, the value of the seller ID and the customer ID of the virtual account management data including the seller ID and the customer ID included in the sales data whose value of the application status data is changed to “done” is changed to empty Also good. Alternatively, for example, the value of the seller ID and the customer ID of the virtual account management data after a predetermined time has elapsed since the values of the seller ID and the customer ID may be set to be empty.

  And when generation | occurrence | production of a new transaction is confirmed, you may set seller ID and customer ID in the said transaction to the said virtual account management data. In this case, the account association unit 38 may transmit an instruction to change the association between the virtual account and the real account to the bank system 12. Then, the virtual account opening unit 56 of the bank system 12 may change the association between the virtual account and the real account.

  In addition, the division of roles of the accounting system 10, the bank system 12, the seller terminal 14, and the deposit terminal 16 in the account management system 1 is not limited to the above. For example, both the function shown in FIG. 9A and the function shown in FIG. 9B may be implemented in one computer system.

  The specific character strings and numerical values described above and the specific character strings and numerical values in the drawings are examples, and are not limited to these character strings and numerical values.

  1 account management system, 10 accounting system, 10a processor, 10b storage unit, 10c communication unit, 10d output unit, 10e input unit, 12 bank system, 12a processor, 12b storage unit, 12c communication unit, 12d output unit, 12e input unit , 14 Seller terminal, 16 Deposit terminal, 18 Computer network, 20 Master data storage unit, 22 Virtual account management data storage unit, 24 Sales data storage unit, 26 Virtual account designation reception unit, 28 Virtual account management data generation unit, 30 Request acceptance unit, 32 Sales data registration unit, 34 Transaction generation confirmation unit, 36 Virtual account determination unit, 38 Account association unit, 40 Billing data issue unit, 42 Payment details data reception unit, 44 Application processing execution unit, 50 Account related Management data storage unit, 52 Virtual account designation output unit, 54 Opening instruction Display receiving unit, 56 virtual account opening unit, 58 depositing procedure receiving unit, 60 depositing process execution unit, 62 depositing details data generating unit, 64 depositing details data transmitting unit.

Claims (8)

Accepting means for accepting from the bank system designation of a plurality of unopened virtual accounts that are not previously associated with a real account of a financial institution;
Storage means for storing virtual account specifying data for specifying a plurality of unopened virtual accounts specified;
A means of confirming the occurrence of a transaction that causes a monetary charge;
When the occurrence of the transaction is confirmed by the confirmation means, any one or a plurality of virtual accounts among the plurality of unopened virtual accounts identified based on the virtual account identification data are set as depositees in the transaction. Determining means to determine as,
Opening an instruction virtual account to be the determining, and the actual account to deposit process is when the monetary payment procedure by specifying the virtual account is, the banking system an indication that associated with the virtual account An association means to send to
An account management system comprising: Issuing means for issuing billing data in which the determined virtual account is designated as a payment destination;
The account management system according to claim 1. The association means changes the real account associated with the virtual account that satisfies a predetermined condition.
The account management system according to claim 1 or 2. Output means for outputting designations of a plurality of unopened virtual accounts that are not previously associated with real accounts of financial institutions;
Instructions for opening one or more virtual accounts determined from a plurality of designated virtual accounts that have not been opened , and the procedure for depositing money by designating the one or more virtual accounts and the virtual accounts An accepting means for accepting an instruction for associating with an actual account to be deposited when
An association means for performing establishment of the virtual account determined in response to the reception of the instruction , and associating the determined virtual account with the real account to be subjected to the deposit process;
A banking system characterized by including: The account management system accepting from the bank system designation of a plurality of unopened virtual accounts that are not previously associated with a real account of a financial institution;
Storing the virtual account specifying data for specifying the plurality of unopened virtual accounts specified in the storage means by the account management system ;
The account management system confirming the occurrence of a transaction that causes a claim for money;
When the occurrence of the transaction is confirmed by the account management system, any one or a plurality of virtual accounts of the plurality of unopened virtual accounts identified based on the virtual account identification data are included in the transaction. A step to determine the recipient,
The account management system, establishing instruction of the virtual account the determined, and the actual account to deposit process is when it is payment procedure of money by specifying the virtual account, be associated with the virtual account Sending instructions to the banking system ;
Account management method characterized by including. The banking system outputting a plurality of unopened virtual account designations not previously associated with a real account of a financial institution;
The bank system designates one or more virtual account opening instructions determined from among the plurality of unopened virtual accounts specified, the one or more virtual accounts, and the virtual account Receiving an instruction for associating with an actual account to be processed when money is deposited;
A step wherein the banking system, in response to reception of the instruction, the opening of the virtual account to be determined, and, for performing the association between the virtual account the actual account should the deposit process is to be determined,
Account management method characterized by including. A procedure for accepting from a bank system designation of a plurality of unopened virtual accounts that are not previously associated with a real account of a financial institution;
A procedure for storing virtual account specifying data for specifying a plurality of unopened virtual accounts specified in a storage means;
Instructions for confirming the occurrence of a transaction that causes a monetary charge,
A procedure for determining any one or a plurality of virtual accounts among the plurality of unopened virtual accounts specified based on the virtual account specifying data as depositees in the transaction when the occurrence of the transaction is confirmed ,
Opening an instruction virtual account to be the determining, and the actual account to deposit process is when the monetary payment procedure by specifying the virtual account is, the banking system an indication that associated with the virtual account Steps to send to
A program that causes a computer to execute. A procedure for outputting designations of a plurality of unopened virtual accounts that are not previously associated with a real account of a financial institution,
Instructions for opening one or more virtual accounts determined from a plurality of designated virtual accounts that have not been opened , and the procedure for depositing money by designating the one or more virtual accounts and the virtual accounts A procedure for accepting an instruction for associating with an actual account to be processed when
A procedure for executing the establishment of the virtual account to be determined in response to the reception of the instruction and the association between the virtual account to be determined and the real account to be subjected to the deposit process;
A program that causes a computer to execute.

Images