JP6943366B2 - Account management system - Google Patents

Description

The present invention relates to a technique for managing account information of a financial institution, and more particularly to a technique applicable to an account management system for managing a shared account among a plurality of people such as a household.

With the progress of IT technology, a mechanism for managing the personal asset status, such as generating and managing a user's household account book and managing bank account information, has been proposed. In recent years, a mechanism for easily collecting and browsing information has been proposed using a mobile terminal such as a smartphone owned by each user.

For example, Japanese Patent Application Laid-Open No. 2001-30679 (Patent Document 1) collects income and expenditure information including transaction information on a debit card and account information of a financial institution from a host computer, and based on this, household account book data is collected. The technology related to the generated household account book data creation system is described.

Further, in Japanese Patent Application Laid-Open No. 2005-38130 (Patent Document 2), a website for aggregation acquires deposit / withdrawal details of a plurality of financial institutions and displays them collectively, so that the deposit / withdrawal details can be displayed as a household account book application. The technology that makes it easy to take in all at once is described in.

In addition, Money Forward (registered trademark, non-patent document 1), which is a household account book application, is linked with Internet services provided by multiple financial institutions such as banks, securities companies, and credit card companies, and is owned by multiple users. It is possible to acquire an account and information related to the account, automatically create a household account book, and check the asset status.

JP 2001-306798 Japanese Unexamined Patent Publication No. 2005-38130

"Fully automatic household account book Money Forward", [online], Money Forward Co., Ltd., [Search on February 18, 2016], Internet <URL: https://moneyforward.com/>

For example, a newly-married couple has a need to establish a shared account for the couple and jointly manage the assets when building a shared asset in the household. In this respect, in any of the prior arts, each user can manage only the information related to the account in which he / she is the holder. Therefore, it is not assumed that each user independently browses the asset status of an account that is virtually shared by a plurality of people, such as a married couple, or conducts a transaction.

Therefore, an object of the present invention is to provide an account management system that supports management of a shared account that is substantially shared among a plurality of users.

The above and other objects and novel features of the present invention will become apparent from the description and accompanying drawings herein.

A brief description of typical inventions disclosed in the present application is as follows.

The account management system according to a typical embodiment of the present invention is an account management system that supports the management of accounts held by users in financial institutions, and is the information of the first user and the second user. The information is provided by the financial institution, a user database that holds the information of the shared account that holds the information of the shared account that is jointly managed with the second user in the account in the name of the first user, and the account database that holds the information of the shared account. Transaction processing of the financial institution based on instructions from the scraping processing unit that accesses the system and acquires the information of the shared account and the information processing terminal from the first user or the second user. It has a transaction processing unit that calls a programming interface provided by the system and performs transaction processing related to the shared account.

Among the inventions disclosed in the present application, the effects obtained by representative ones will be briefly described as follows.

That is, according to a typical embodiment of the present invention, it is possible to support management of a shared account that is substantially shared among a plurality of users.

It is a figure which showed the outline about the structural example of the account management system which is one Embodiment of this invention. (A) and (b) are diagrams showing an outline of an example of account management in one embodiment of the present invention. It is a figure which showed the example of the process flow of the initial registration of each user in one Embodiment of this invention. It is a figure which showed the example of the flow of transaction processing with a shared account in one Embodiment of this invention. It is a figure which showed the outline about the example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about another example of the screen which the account management application in one Embodiment of this invention displays on a user terminal. It is a figure which showed the outline about the example of the data structure of the user DB in one Embodiment of this invention. It is a figure which showed the outline about the example of the data structure of the account DB in one Embodiment of this invention. It is a figure which showed the outline about the example of the data structure of ToDoDB in one Embodiment of this invention. It is a figure which showed the outline about the example of the data structure of the log DB in one Embodiment of this invention. It is a figure which showed the outline about the example of the data structure of the comment DB in one Embodiment of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, in all the drawings for explaining the embodiment, in principle, the same reference numerals are given to the same parts, and the repeated description thereof will be omitted. On the other hand, the parts described with reference numerals in one figure may be referred to with the same reference numerals in the explanation of other figures, although they are not shown again.

<System configuration>
FIG. 1 is a diagram showing an outline of a configuration example of an account management system 1 according to an embodiment of the present invention. The account management system 1 of the present embodiment is, for example, a couple or a partner, user A (5a) and user B (5b) (hereinafter, these may be collectively referred to as "user 5"). However, it is an information processing system that makes it possible to jointly manage shared assets by using an account set up in a financial institution such as a bank as a shared account. Here, each user 5 can independently browse the contents of the shared account and perform transactions related to the shared account.

In addition, each other can exchange comments and messages regarding the asset status and transactions so that communication similar to the SNS (Social Networking Service) service can be taken. This makes it possible to communicate with each other regarding asset formation and disposal at an appropriate timing without restrictions on the location and time of each other. In addition, by recording the content of communication as a history, it is possible to easily confirm the content of decision-making related to asset formation and disposal, the background situation of individual transactions, etc. later.

Furthermore, the content of communication can be classified by attaching tags according to topics and the like. This makes it easy to grasp the content of communication and makes it possible to carry out transactions related to tags (topics) easily and quickly from there. In addition, by looking at the content of communication for each tag, smoother communication can be achieved.

The account management system 1 of FIG. 1 has, for example, the user terminals A (6a) and the user terminals A (6a) owned by the user A (5a) and the user B (5b), respectively, for the account management server 2 via the Internet 3. It has a configuration in which a user terminal B (6b) (hereinafter, these may be collectively referred to as a "user terminal 6") can be connected. In addition, Internet banking (IB), which is a transaction processing system provided by a bank having an account as a shared account for user A (5a) and user B (5b) to jointly manage assets, is provided on the Internet 3. System 4 is connected.

Each user terminal 6 is, for example, a mobile terminal such as a smartphone or a tablet terminal, and an account management application 61 is introduced therein. The account management application 61 is an application program that provides a user interface for each user 5 to manage an account. The contents of the user interface will be described later.

In the present embodiment, the account management application 61 is implemented as a client application for accessing each function provided by the account management server 2 described later, and is downloaded and introduced to each user terminal 6. Not limited. The website may be accessed by the account management server 2 via a Web browser or the like (not shown) on each user terminal 6. In this case, each user terminal 6 can be a stationary information processing terminal such as a PC (Personal Computer).

The account management server 2 is a server system composed of a virtual server constructed on a server device or a cloud computing service. For example, an interface unit 10, an account processing unit 20, a ToDo management unit 30, and a comment processing unit implemented as software that runs on middleware such as an OS (Operating System), a DBMS (DataBase Management System), and a Web server program (not shown). It has 40 and each part such as a data management unit 50. It also has tables such as a user database (DB) 51, an account DB 52, a ToDo DB 53, a log DB 54, and a comment DB 55, which are implemented as a database.

Although the account management application 61 and the account management server 2 are shown as one individual in FIG. 1, they may be configured as different individuals for each function or a group of a plurality of functions, for example. , The DB group of the account management server 2 may be configured on another server. Further, a part of the operation of the account management server 2 may be implemented so as to operate on the account management application 61, and conversely, a part of the operation of the account management application 61 may be operated on the account management server 2. It may be implemented in.

The interface unit 10 provides an interface function such as accepting a request and transmitting a response to the request to the account management application 61 on each user terminal 6. In addition to these, it has a function to notify the account management application 61 of the target user 5 by push notification when, for example, an event such as a fluctuation of the shared account or a comment is sent from the other user 5 is detected. You may be doing it. When the account management application 61 is implemented on a Web basis, or when the user terminal 6 accesses using a Web browser (not shown), screen contents are generated and via a Web server program (not shown). It may have a function to display. In addition, it may have a security function such as encryption / decryption of data exchanged with the outside. The content of the access from the user 5 is recorded in the log DB 54.

The account processing unit 20 has various units such as a scraping processing unit 21 and a transaction processing unit 22, and has a function of performing various processing on a shared account or a personal account of each user 5 in cooperation with the IB system 4. The scraping processing unit 21 has a function of automatically accessing the Internet banking website provided by the IB system 4 to extract and collect information related to shared accounts and personal accounts. For example, it can be implemented by appropriately using a commonly used known web scraping technique, tool, or the like. The collected information is reflected in the account DB 52 and the like.

The account processing unit 20 may have a function of analyzing the contents collected by the scrape processing unit 21 and performing predetermined processing according to the result. For example, it is possible to determine whether or not the balance is sufficient before withdrawing a credit card, utility charges, etc., and notify a warning if the balance is below a certain amount. In addition, it is possible to analyze the tendency of transactions and provide information such as output of advertisements / advertisements, advice on household budgets, news, etc. according to the tendency.

The transaction processing unit 22 calls the API (Application Programming Interface) for transaction processing provided by the IB system 4 based on the instruction from the user 5 via the interface unit 10, and enters and leaves the shared account and the personal account. It has a function to execute various transactions such as money and balance inquiry, transfer and transfer. The information on the transaction execution result is reflected in the account DB 52, the log DB 54, and the like.

The ToDo management unit 30 has a function of accepting registration of ToDo from each user 5 and recording it in ToDoDB53, and managing the deadline for each ToDo registered in ToDoDB53. Based on the instruction from the user 5, it may have a function of automatically registering ToDo, automatically executing the registered ToDo, and the like.

The comment processing unit 40 has a function of receiving comments and message inputs from each user 5 and recording them in the comment DB 55. Further, by notifying the destination of the input comment and further accepting the reply, text-based two-way communication between each user 5 is realized. Here, the methods and techniques used in general SNS services can be appropriately used. In the present embodiment, in addition to arbitrary comments, the history of transactions such as deposits and withdrawals and transfers to a shared account is treated in the same way as comments and can be viewed in a series of flows.

The comment processing unit 40 of the present embodiment further has a topic management unit 41, and has a function of classifying comments (or a series of comments and threads) and transaction history with tags corresponding to the topics. Have. The topic management unit 41 makes it possible to narrow down and extract a series of comments and the like according to the type of tag. In addition, when conducting a transaction from there, it is possible to automatically set the transaction content and condition content corresponding to the tag type. The screen image for registering / viewing comments and executing transactions will be described later.

The data management unit 50 has a function of managing access such as registration / update and reference of data to each database by using a DBMS function (not shown).

<Account management>
FIG. 2 is a diagram showing an outline of an example of account management in the present embodiment. FIG. 2A shows an example of the usage account of each user 5 to be managed by the account management system 1. User A (5a) and User B (5b) have "Account A" and "Account B" as their own personal accounts, respectively. And each user 5 has "account C" as a shared account jointly managed.

It does not matter if "Account C", which is a shared account, can be created under the joint name of each user 5, but in Japan, the current situation is finance that allows the creation of such a shared account (joint account). The institution is unknown. Therefore, on the account management system 1 of the present embodiment, the "account C" created in the name of one of the users 5 (user A (5a) in the example of FIG. 2) is treated as a shared account. And.

In this case, in the account management system 1, the user A (5a) can refer to the personal account "account A" and the shared account "account C", but the other user B ( 5b) The personal account "Account B" is controlled so that it cannot be referred to. On the contrary, the user B (5b) controls that the "account B" and the "account C" can be referred to, but the "account A" cannot be referred to. As described above, in the present embodiment, it is possible to construct and manage the shared assets while maintaining the assets belonging to the exclusive rights of each user 5 under the marital production system.

User A (5a) can arbitrarily transfer funds between "account A" and "account B", of which he / she is the holder ("fund transfer (1)" in the figure). In addition, the user B (5b) can arbitrarily transfer the funds from the "account B" in which the user A (5b) is the holder to the "account C" in which the user A (5a) is the holder (in the figure). "Transfer of funds (2)").

On the other hand, when user B (5b) arbitrarily transfers funds from "account C" to "account B" ("fund transfer (3)" in the figure), it is normal for financial institutions. It cannot be done by trading. In the present embodiment, for example, it is assumed that the user A (5a) gives the user B (5b) a comprehensive proxy right on the account management system 1. Then, the user B (5b) is allowed to transfer the funds from the "account C" to the "account B" on behalf of the user A (5a). It may be permitted only when the existence of the proxy right is approved by the financial institution, such as when the user B (5b) actually holds the proxy cash card for "account C".

In the present embodiment, in addition to enabling the transfer of funds between the personal account and the shared account of each user 5, the shared account is transferred to another destination (an account other than the name of each user 5). On the other hand, it is also possible to send money by transfer or the like. FIG. 2B shows an example of making a transfer from a shared account. Depending on the service content provided by the corresponding IB system 4, in addition to the transfer to the pre-registered transfer destination, the transfer may be performed each time. Similar to the case of FIG. 2A, the remittance may be performed not only by the user A (5a) who is the holder of the shared account "account C" but also by the user B (5b). ..

<Processing flow>
FIG. 3 is a diagram showing an example of a flow of initial registration processing of each user 5 when using the account management system 1 of the present embodiment. It is assumed that each user 5 has installed the account management application 61 (or Web browser) in his / her own user terminal 6 in advance.

For example, it is assumed that the user B (5b) who is not the holder of the shared account applies for the use of the application via the account management application 61 before the user A (5a) who is the holder of the shared account. (S01). Here, the attribute information such as the name of the user B (5b) is input, and the account information such as the user ID and password used in the account management application 61 is input. The account management server 2 that has received the application confirms the input information, records it in the user DB 51, and registers the use of the application (S02). The account management server 2 may issue account information such as a user ID and a password. In addition, the user registration may be performed through the two stages of provisional registration / main registration.

The user ID and / or password here may be the user ID and / or password when the Internet banking service provided by the IB system 4 is already used. Then, when the application for the use of the IB system 4 is currently applied, the application for the use of the account management application 61 may be omitted. Specifically, for example, when the user ID and / or password of the IB system 4 is input at the timing of applying for the use of the application via the account management application 61, the account management system 1 IBs the user ID and / or the password. Identify as system 4 user ID and / or password. Then, the related information (name, etc.) of the user 5 related to the target user ID is acquired from the IB system 4.

After that, the user B (5b) sets a shared account to be managed via the account management application 61 (S03), and further sets a personal account as needed (S04). The account management server 2 acquires the set account information and registers it in the account DB 52 (S05). The acquired account information includes, for example, an identification number such as a customer number and a user ID, and a password for the target account registered in the financial institution, which are acquired from the IB system 4.

After that, the user B (5b) sets a secret keyword valid only between the user A (5a) and the user B (5b) in the account management system 1 (S06). This keyword is for associating (associating) the user A (5a) with the user B (5b), and is registered in the user DB 51, for example. User B (5b) shares the content by, for example, verbally communicating the set keyword to user A (5a). After that, the user A (5a) is notified by sending an e-mail for inviting the other party's user A (5a) to the account management application 61 (S07).

In the example of FIG. 3, at this point in time, there is no systematic association with the other party user A (5a). Therefore, the user B (5b) cannot manage the shared account via the account management application 61, and can manage only the personal account of which he / she is the holder.

After that, when the user A (5a) who is the holder of the shared account receives the invitation email from the user B (5b) (S11), he / she applies for the use of the application via the account management application 61 (S12). .. Similar to the case of user B (5b), the attribute information such as the name of user A (5a) is input, and the account information such as the user ID and password used in the account management application 61 is input. The account management server 2 that has received the application confirms the input information, records it in the user DB 51, and registers the use of the application (S13).

After that, the user A (5a) inputs the keyword set in step S06 by the user B (5b) who sent the invitation email via the account management application 61 (S14). The account management server 2 authenticates based on whether or not the input keyword matches the one set by the user B (5b) (S15). If they match, the user B (5b) acquires the information of the shared account set in step S03, sets this as the shared account of the user A (5a), and uses the account management application 61. Presented to user A (5a) (S16). As a result, the user A (5a) and the user B (5b) are related on the system via the information of the shared account.

The user A (5a) further sets up a personal account via the account management application 61 as needed (S17). The account management server 2 acquires the set account information and registers it in the account DB 52 (S18). As in the case of step S05 in user B (5b), the acquired account information includes, for example, a customer number, a user ID, etc. related to the target account registered in the financial institution acquired from the IB system 4. The identification number and password of the are also included.

Through the above series of processes, the user A (5a) and the user B (5b) can be handled on the system as an entity that jointly manages the shared account. By this association, each user 5 can manage a shared account in addition to the personal account of which he / she is the owner via the account management application 61.

In the example of FIG. 3, the user B (5b) who is not the holder of the shared account is the shared account in the name of the user A (5a) who has been agreed with the user A (5a) first. Is registered as a management target, and then user A (5a) is invited, but the flow of processing is not limited to this. On the contrary, the flow of processing in which user A (5a), who is the holder of the shared account, first registers the shared account in which he / she owns the name as a management target, and then invites user B (5b). Of course it is possible.

Further, in the present embodiment, the user A (5a) is associated with the user A (5a) through the input of the keyword set by the user B (5b), and when the association is made, the user who has set the keyword. By applying the shared account set by B (5b) to user A (5a), the load of setting of user A (5a) is reduced, but the configuration is not limited to this. For example, both the user A (5a) and the user B (5b) may individually set the shared account information and associate the information when they match.

FIG. 4 is a diagram showing an example of a flow of transaction processing in a shared account using the account management system 1 of the present embodiment. FIG. 4 shows, as an example, a case where processing such as transfer is performed based on ToDo related to transaction processing in a shared account. For example, first, the user B (5b) inputs ToDo via the account management application 61 (S21), and the account management server 2 registers the information in the ToDoDB 53 (S22). As the content of ToDo, for example, "the user 5 in charge makes the transfer by a predetermined date such as the end of the month" is assumed. When inputting ToDo, user B (5b) may also input a comment or a message (S23). The account management server 2 registers the input comment in the comment DB 55.

When ToDo is registered in ToDoDB53, the account management server 2 pushes the contents to the user 5 (user A (5a) in the example of FIG. 4) who is in charge of ToDo (S25). The content of the notification is displayed on the user terminal 6a of the user A (5a) (S26). The notification may be displayed by the OS of the user terminal 6a or by the running account management application 61. The configuration may be such that the date and time for push notification can be set. User A (5a) can grasp the contents of ToDo by referring to the contents of the notification. Although not shown, the user A (5a) can communicate about ToDo and communicate by replying to the comment attached by the user B (5b). The ToDo of the user B (5b) who has received the notification may be incorporated into the ToDo of the user A (5a).

When the ToDo management unit detects that the ToDo due date has arrived, the account management server 2 push-notifies the user A (5a) who is in charge of the ToDo (S31). The content of the notification is displayed on the user terminal 6a of the user A (5a) (S32). The notification is not limited to the day of the due date, and may be given several days in advance depending on the setting. The push notification may also be given to the user B (5b) who has registered ToDo.

The user A (5a) who has confirmed the content of the notified ToDo instructs the execution of the transaction (transfer in the example of FIG. 4) specified for the target ToDo (S33). In the account management server 2, the transaction processing unit 22 calls the API that executes the transfer process and executes the transfer (S34). After that, the API that executes the balance inquiry process is called to confirm the account information such as the balance (S35). If it can be confirmed that the balance has been updated, the user A (5a) is notified of the completion of the transfer, and the user B (5b) is also notified by push (S36). The content of the notification is displayed on the user terminal 6 of each user 5 (S37, S38). Each user 5 can grasp that the transfer process related to ToDo has been completed by referring to the content of the notification.

Although not shown, each user 5 can register a comment for this notification to communicate with each other. Further, by associating the target ToDo with the execution content such as the transfer process related to the instruction, the target ToDo may be deleted from the ToDoDB 53 after receiving the notification of the transfer completion.

<User interface>
FIG. 5 is a diagram showing an outline of an example of a screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. Here, an example of screen transition when a user who is not the holder of the shared account (user B (5b) in the example of this embodiment) applies for the use of the account management application 61 is shown. The upper left screen of FIG. 5 shows an example of a screen in which account information is set as initial settings and user registration is performed. Here, the user B (5b) sets the user ID (“customer number” in the figure) and password used in the account management application 61. The account management application 61 may automatically set the initial value. In addition, commonly used spoofing prevention means such as registering account information through two steps of provisional registration / main registration can be appropriately used.

Here, when the "OK" button at the bottom of the screen is pressed (detailed operations such as tapping and clicking may differ depending on the device of the user terminal 6, but hereinafter collectively referred to as "pressing"), it is shown in the upper right screen of FIG. Display the setting screen of such an account. Here, the account number that specifies the shared account that the user B (5b) manages jointly with the other user (user A (5a) in this embodiment), and the user B (5b) are individuals. Specify the account number information that identifies the personal account to be managed. Here, the account number may be directly entered, or may be selected and set from the already registered information as shown in the figure.

When the "OK" button at the bottom of the screen is pressed, a keyword setting screen as shown in the screen at the bottom left of FIG. 5 is displayed. This keyword is a secret keyword that is valid only between the user A (5a) and the user B (5b) in the account management system 1. By requesting the other party's user A (5a) to input this keyword, it is possible to associate (associate) user A (5a) with user B (5b) while preventing spoofing. .. The keyword set here by the user B (5b) is shared outside the account management system 1 by, for example, verbally communicating it to the user A (5a). It is also possible to skip the keyword setting here.

Here, when the "OK" button at the bottom of the screen is pressed, the invitation screen of the other party as shown in the screen at the bottom right of FIG. 5 is displayed. Here, by inputting the e-mail address of the other party's user A (5a) and the content of the comment as the e-mail body, an invitation e-mail urging the user A (5a) to use the account management application 61 is sent. can do. It is also possible to skip the process of inviting the other party here.

FIG. 6 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. Here, when a user who is the holder of a shared account (user A (5a) in this embodiment) receives an invitation email from user B (5b) and applies for the use of the account management application 61. An example of the screen transition of is shown. The upper left screen of FIG. 6 shows an example of a state in which user A (5a) has received an invitation email. Here, if the user A (5a) has not yet installed the account management application 61 on the user terminal 6, he / she can download it from an appropriate website by pressing the "app download" button at the bottom of the screen. Can be introduced.

If the account management application 61 has already been installed, pressing the "Account Registration" button at the bottom of the screen will display a screen for user registration by setting account information as the initial settings, as shown in the upper right screen of FIG. do. Here, as in the case of the user B (5b) shown in FIG. 5, the user A (5a) sets the user ID (“customer number” in the figure) and the password used in the account management application 61. .. The account management application 61 may automatically set the initial value. In addition, commonly used spoofing prevention means such as registering account information through two steps of provisional registration / main registration can be appropriately used.

When the "OK" button at the bottom of the screen is pressed, a keyword input screen as shown in the lower left screen of FIG. 6 is displayed. This keyword is preset by the user B (5b) and is orally transmitted to the user A (5a). If the input contents here match those set in advance by user B (5b), user A (5a) and user B (5b) must be partners who jointly manage the shared account. Is authenticated.

Here, when the "OK" button at the bottom of the screen is pressed, the account setting screen as shown in the screen at the bottom right of FIG. 6 is displayed. Here, it is shown that the account already registered as the shared account by the user B (5b) is automatically set as the shared account of the user A (5a). In this case, the user A (5a) does not need to register the shared account again, and only needs to specify the information of the account number that identifies the personal account managed by the user.

FIG. 7 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. Here, an example of screen transition when each user 5 cancels the association with the other party is shown. The upper left screen of FIG. 7 shows an example of a login screen in which the user 5 specifies a user ID (“customer number”) and a password. Here, when the user 5 presses the "OK" button at the bottom of the screen to display a screen for making various settings as shown in the upper right screen of FIG. 7, and further presses "partner setting" here, the figure is shown. Display the screen for partner setting as shown in the lower left screen of 7.

Here, when the user 5 presses "disconnect", the other user 5 is notified that the association between the users 5 is canceled. The lower right screen of FIG. 7 is a normal screen (for example, a standby screen) of the user terminal 6 of the other user 5 and is in a state where a push notification indicating that a request for cancellation of the association has been made is displayed. An example is shown.

It should be noted that the actual cancellation of the association may be performed after waiting for the consent of the other party, or the cancellation is immediately made at the request of one user 5, and the other party is notified that the cancellation has been made. You may. After the association is canceled, access control is performed on the account management system 1 so that neither user 5 can refer to the past history of past transaction details and comments related to the shared account (use as the holder of the shared account). Person (user A (5a) in this embodiment) can individually refer to the transaction history of the account on the IB system 4).

FIG. 8 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The screen on the left side of FIG. 8 shows an example of the main screen. Here, for example, a calendar is displayed and the date on which ToDo is registered is marked. In addition, information on the balance of the account is displayed at the top of the screen. For the account balance information, for example, the balances of the shared account or the individual account may be displayed based on the instruction or setting from the user 5, or the total balance of these accounts may be displayed. May be good.

When this screen is scrolled upward or downward by using the touch panel function provided in the user terminal 6, a management history screen for a shared account is displayed as shown in the screen on the right side of FIG. Here, for example, in addition to the transaction history such as transfer and direct debit in the shared account, the history of exchanging comments between each user 5 is also displayed. This makes it possible to easily confirm the details of decision-making related to asset formation, disposal, etc., and the background of individual transactions. The history content to be displayed may be, for example, a configuration in which the entire history so far is scrolled, or only the history related to the year, month, and day specified in the calendar displayed before scrolling is scrolled and displayed. It may be a configuration.

Information on the history of exchanging comments can be obtained from the comment DB 55. On the other hand, the scrape processing unit 21 of the account management server 2 may access the IB system 4 to acquire the latest information on the account balance information and the transaction history information each time. Alternatively, the scraping processing unit 21 may periodically access the IB system 4 to acquire information and record the contents in the account DB 52, the log DB 54, or the like to improve the processing performance.

FIG. 9 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The screen on the left side of FIG. 9 is the same main screen as the example of FIG. Here, when the "My Page" button at the lower right of the screen is pressed, a screen for displaying information unique to each user 5 is displayed as shown in the screen on the right side of FIG. Here, for example, information on the balance of the personal account of user 5 and information on transaction history are displayed. It is also possible to switch the screen to the tab that displays the list of ToDo for which the user 5 is in charge.

FIG. 10 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The upper left screen of FIG. 10 is the same main screen as the example of FIG. Here, when the "ToDo" button at the lower left of the screen is pressed, the ToDo list screen as shown in the upper right screen of FIG. 10 is displayed. Here, you can switch tabs between the list of all ToDos and the list of ToDos for which you are in charge.

Here, when the target ToDo (ToDo at the top of the list in the example of the screen on the upper right of FIG. 10) is pressed, a detailed screen of ToDo settings as shown in the screen at the lower left of FIG. 10 is displayed. This screen can be switched to the comment screen as shown in the lower right screen of FIG. 10 by pressing the "comment" tab. Here, comments related to ToDo can be exchanged with the other user 5. In addition, a series of comments (and / or ToDo) can be classified by attaching a tag related to the content of ToDo (“cooking class” in the example of FIG. 10). The tag may be configured so that it can be selected from those prepared in advance on the system side via a list box or the like, or it may be configured so that the user 5 can newly register it at any time.

FIG. 11 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The upper left screen of FIG. 11 is the same main screen as the example of FIG. Here, when the "send / return money" button at the bottom center of the screen is pressed, a remittance screen as shown in the upper center screen of FIG. 11 is displayed. The balance information of the shared account is displayed at the top of the screen, and the buttons for each type of remittance are displayed at the bottom of the screen. Here, for example, remittance from one's own personal account to a shared account, remittance from a shared account to the personal account of the other user 5, remittance from a shared account to another destination, and from a shared account to one's own personal account. You can specify the remittance of. Here, for example, when remittance from one's own personal account to a shared account (leftmost button) is specified, a remittance instruction screen as shown in the upper right screen of FIG. 11 is displayed.

On the remittance instruction screen, for example, the remittance amount is specified by a slider as shown in the figure, a software keyboard with a numeric keypad (not shown), or the like. Then, when the "OK" button is pressed, a screen for inputting a PIN (Personal Identification Number) code as shown in the lower left screen of FIG. 11 is displayed. This PIN code is, for example, an authentication code that needs to be specified when actually sending money in the IB system 4. When the PIN code is entered and the "transfer" button is pressed, a confirmation screen as shown in the lower center screen of FIG. 11 is displayed. When the "comment" button is pressed here, a comment input screen as shown in the lower right screen of FIG. 11 is displayed. Here, in addition to inputting a comment, a tag related to the content of the remittance (“pocket money” in the example of FIG. 11) can be attached for classification.

FIG. 12 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The upper left screen of FIG. 12 is a normal screen (for example, a standby screen) of the user terminal 6, and shows an example of a state in which a push notification indicating that a payment has been made to the shared account is displayed. Here, for example, when the target notification is tapped, a screen for confirming the contents of payment and inputting a comment as shown in the upper center of FIG. 12 is displayed. If the comment input field is further tapped here, a screen for inputting a comment using the software keyboard is displayed as shown in the upper right screen of FIG. Here, in addition to inputting comments, tags related to transactions and the contents of comments (“eldest son” in the example of FIG. 12) can be attached for classification.

When the input of the comment is completed, a confirmation screen as shown in the lower left screen of FIG. 12 is displayed. Here, if the "OK" button is pressed while the comment is specified to be notified to the other party (in the example of FIG. 12, the check box of "Notify this memo to the other party"), the comment is notified to the other party as well. , Record in comment DB55.

In the present embodiment, the comment is transmitted only to the other party associated with the account via the shared account, but it is electronically sent to an external third party (“eldest son” in the example of FIG. 12). It may be configured so that comments and messages can be sent by means such as e-mail. In this case, the e-mail address of the third party (“eldest son”) may be manually specified by the user 5 each time, or may be selected from the e-mail addresses registered in advance in the system.

FIG. 13 is a diagram showing an outline of another example of the screen displayed on the user terminal 6 by the account management application 61 of the present embodiment. The upper left screen of FIG. 13 shows an example of a shared account management history screen similar to the screen on the right side of FIG. 8. Here, for example, in addition to transaction histories such as transfer and direct debit in a shared account, the history of exchange of comments between each user 5 is also integrated and displayed.

If you specify a tag in this state, as shown in the screen on the upper right of FIG. 13, the display content is narrowed down only to the comments and transaction history with the specified tag (“cooking class” in the example of FIG. 13). Can be done. This makes it possible to easily and efficiently confirm the transaction details related to the tag (topic), the decision-making details at that time, the background circumstances, and the like.

Then, when the "send / return money" button at the bottom center of the screen is pressed in this state, a remittance screen as shown in the lower left screen of FIG. 13 is displayed. Here, as transaction conditions such as the transfer destination and the transfer amount, the content related to the tag is automatically set as the default value. When there are a plurality of transfer destinations and transfer amount patterns, they may be displayed in a selectable form so that the user 5 can select them. The transaction conditions related to the tag may be specified in advance by each user 5, or may be inferred from the contents of the past transaction history (most frequent pattern, latest pattern, etc.). .. This makes it possible to carry out transactions related to the topic quickly and efficiently.

<Data structure>
FIG. 14 is a diagram showing an outline of an example of the data configuration of the user DB 51. The user DB 51 is a table that holds account information, attribute information, and the like of each user 5. For example, it has each item such as a user ID, a user name, authentication information, and a shared account.

The user ID item holds ID information for uniquely identifying each user 5. The user name item retains display information such as the name of the target user 5. The item of authentication information holds authentication information such as a password and biometric information corresponding to the user ID of the target user 5. The item of shared account information holds information such as an account number that identifies the shared account of the target user 5. As described above, the user 5 related to the user ID whose shared account information matches is treated as jointly managing the shared account.

FIG. 15 is a diagram showing an outline of an example of the data structure of the account DB 52. The account DB 52 is a table that holds information related to the accounts of financial institutions held by each user 5. For example, it has items such as a user ID, an account number, a financial institution, authentication information, and a shared account flag.

The item of the user ID holds the information of the user ID related to the user 5 who holds the target account (who is the holder). The value of this user ID is registered in the user DB 51 shown in FIG. 14 above. The account number item holds the information of the account number that identifies the target account. The item of financial institution holds information such as a name and a number that identifies the financial institution in which the target account is opened. The item of authentication information holds authentication information such as a PIN code and a password required when conducting a transaction related to a target account via the IB system 4. The item of the shared account flag holds the information of the flag indicating whether or not the target account is the shared account of the target user 5.

FIG. 16 is a diagram showing an outline of an example of the data structure of ToDoDB53. The ToDoDB 53 is a table that holds the contents of the ToDo registered by each user 5. For example, it has each item such as ToDo number, ToDo content, tag type, charge ID, deadline, and status.

The ToDo number item holds information such as a sequence number assigned to uniquely identify each ToDo. The ToDo content item retains information on the content related to the target ToDo. The format of the data is not particularly limited, and for example, it may be retained as simple text data or may be retained as structured data including a plurality of items. The tag type item holds information such as a code value and a name that specifies the tag type assigned to the target ToDo. Thereby, it is possible to specify the type of tag and control to display only the related ToDo.

The person-in-charge ID and deadline items hold information on the user ID that identifies the person in charge of executing the target ToDo and the execution deadline of the target ToDo, respectively. The status item holds a code value or text information indicating the current status of the target ToDo.

It should be noted that each user 5 associated with the shared account may be able to view all ToDos with each other, and may be visible to the other user 5 depending on the tag type, status, or new data item. It is also possible to have no configuration. It may be possible to specify an invisible period and a visible period.

FIG. 17 is a diagram showing an outline of an example of the data structure of the log DB 54. The log DB 54 is a table that holds a log of access to the account management server 2 by each user 5 and log data of actions such as performed operations and transactions. For example, it has each item such as a user ID, an action content, a tag type, and a time stamp.

The user ID item retains the user ID information of the user 5 who has performed the action related to the target log. The value of this user ID is registered in the user DB 51 shown in FIG. 14 above. The action content item holds information that identifies the content of the target action. For example, it is specified by the text indicating the action name or the code value. The tag type item holds information such as a code value and a name that specifies the tag type assigned to the target action. As a result, it is possible to specify the type of tag and control to display only the related log. The time stamp item holds the time stamp information at the time when the target log was recorded.

FIG. 18 is a diagram showing an outline of an example of the data structure of the comment DB 55. The comment DB 55 is a table that holds the contents of comments registered by each user 5. For example, it has each item such as a user ID, a thread number, a comment number, a comment content, a destination, a tag type, and a time stamp.

The user ID item retains the user ID information related to the user 5 who registered the target comment. The value of this user ID is registered in the user DB 51 shown in FIG. 14 above. The thread number and comment number items hold information such as a sequence number that uniquely identifies the thread to which the target comment belongs and the target comment. The comment content item holds text information indicating the content of the target comment.

The destination item holds the information of the user ID related to the user 5 of the destination / destination of the target comment. You may send yourself as a destination, or you may send a plurality of users 5 including yourself as a destination. In this case, the target comment may be shown to the other user 5, or may not be shown. Further, the configuration may be such that these can be set. The tag type item holds information such as a code value and a name that specifies the tag type attached to the target comment. As a result, it is possible to specify the type of tag and control to display only related comments. The time stamp item holds the time stamp information at the time when the target comment is registered.

The data configurations (items) of the tables shown in FIGS. 14 to 18 described above are merely examples, and other table configurations and data configurations can be used as long as similar data can be retained and managed. It may be.

For example, in the present embodiment, the user A (5a) and the user B (5b) are associated with each other using the registration information of the shared account as a key, but a dedicated key for the association is separately added to the data structure. On the other hand, the configuration may be such that all or part of the information of user A (5a) and all or part of the information of user B (5b) are associated with each other. As a result, the user A (5a) and the user B (5b) can be indirectly associated with each other via the key.

In addition, since the information recorded in each of the above tables is basically highly confidential personal information, it is desirable to strictly provide means for ensuring security for access to the data.

As described above, according to the account management system 1 according to the embodiment of the present invention, each user 5 sets the account provided on the IB system 4 of the financial institution as a shared account and jointly shares the assets. It is possible to manage. That is, each user 5 can independently browse the contents of the shared account and perform transactions related to the shared account.

In addition, each other can exchange comments and messages regarding the asset status and transactions so that communication similar to the SNS service can be taken. As a result, it is possible to communicate with each other at an appropriate timing without restrictions such as whereabouts and time. In addition, by recording the content of communication as a history, it is possible to easily confirm the content of decision-making related to asset formation and disposal, the background situation of individual transactions, and the like later.

Furthermore, the contents of communication and the contents of transactions can be classified by attaching tags according to topics and the like. This makes it easier to understand the content of communication and the content of transactions, and makes it possible to carry out transactions related to tags easily and quickly.

Although the invention made by the present inventor has been specifically described above based on the embodiments, the present invention is not limited to the above embodiments and can be variously modified without departing from the gist thereof. Needless to say. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to add / delete / replace a part of the configuration of the above-described embodiment with another configuration.

For example, in the above embodiment, as the user 5 who jointly manages the shared account, a pair of two people such as a married couple is described as an example, but there is a case where three or more people jointly manage the shared account. Can also be applied. Further, in the above embodiment, it has been described that each user 5 has a personal account in addition to the shared account, but it can be applied if there is at least a shared account jointly managed by each user 5. ..

The present invention can be used in an account management system that manages a shared account at home.

1 ... Account management system, 2 ... Account management server, 3 ... Internet, 4 ... IB system, 5a ... User A, 5b ... User B, 6a ... User terminal A, 6b ... User terminal B,
10 ... Interface part,
20 ... Account processing department, 21 ... Scrap processing department, 22 ... Transaction processing department,
30 ... ToDo Management Department,
40 ... Comment processing department, 41 ... Topic management department,
50 ... Data management department, 51 ... User DB, 52 ... Account DB, 53 ... ToDoDB, 54 ... Log DB, 55 ... Comment DB,
61 ... Account management app

Claims (7)

An account management system that supports the management of accounts held by users at financial institutions.
A user database that holds information on the first user and information on the second user,
An account database that holds information on a shared account that is jointly managed with the second user in the account in the name of the first user, and
A scraping processing unit that accesses the system provided by the financial institution to acquire information on the shared account, and
Based on the instruction from the first user or the second user via the information processing terminal, the programming interface provided by the transaction processing system of the financial institution is called to perform transaction processing related to the shared account. Transaction processing department to perform and
A comment processing unit that accepts input of comments from the first user and / or the second user via the information processing terminal for transaction processing related to the shared account and records them in a comment database. And have
The comment processing unit instructs the comment and / or the transaction processing related to the shared account, or the history thereof, from the first user or the second user via the information processing terminal. Has a topic management department that assigns tags based on
In a state where the comment with the specified tag is output to the information processing terminal based on the request from the first user or the second user via the information processing terminal. When an instruction for transaction processing relating to the shared account is received via the information processing terminal, a predetermined transaction condition corresponding to the specified tag is set as a default value.
Account management system. In the account management system according to claim 1,
The account database further holds information about the first account in the name of the first user and / or information about the second account in the name of the second user.
The transaction processing unit transfers funds between the first account or the second account and the shared account as transaction processing related to the shared account.
Account management system. In the account management system according to claim 1,
Based on the request from the first user or the second user via the information processing terminal, the information of the transaction processing related to the shared account and the history of the comment are integrated. Output to the processing terminal,
Account management system. In the account management system according to claim 1,
When the information for identifying the shared account designated by the first user and the information for identifying the shared account designated by the second user, which are stored in the user database, match. , An account management system in which the first user and the second user are users who jointly manage the shared account. In the account management system according to claim 1,
When the keyword specified by the first user, which is stored in advance in the user database, and the keyword specified by the second user via the information processing terminal match, or the user When the keyword specified by the second user, which is stored in advance in the database, and the keyword specified by the first user via the information processing terminal match, the first use An account management system in which a person and the second user are users who jointly manage the shared account. An account management system that supports the management of accounts held by users at financial institutions.
A user database that holds information on the first user and information on the second user,
An account database that holds information on a shared account that is jointly managed with the second user in the account in the name of the first user, and
A scraping processing unit that accesses the system provided by the financial institution to acquire information on the shared account, and
Based on the instruction from the first user or the second user via the information processing terminal, the programming interface provided by the transaction processing system of the financial institution is called to perform transaction processing related to the shared account. Transaction processing department to perform and
It has a ToDo management unit that accepts ToDo input related to transactions related to the shared account from the first user or the second user via the information processing terminal and records it in the ToDo database. ,
The ToDo and the contents of the transaction are associated with each other.
The information processing terminal of the user who is in charge of the ToDo is notified of the ToDo, and the information processing terminal is notified.
Based on the instruction from the person in charge of the ToDo to execute the transaction specified by the ToDo, the transaction processing with the contents of the transaction associated with the ToDo is executed.
Account management system. A user database that holds information on the first user and information on the second user,
An account database that holds information on a shared account jointly managed with the second user in the account of a financial institution in the name of the first user, and
A scraping processing unit that accesses the system provided by the financial institution to acquire information on the shared account, and
Based on the instruction from the first user or the second user via the information processing terminal, the programming interface provided by the transaction processing system of the financial institution is called to perform transaction processing related to the shared account. An information processing terminal included in an account management system that has a transaction processing unit that performs transactions.
The account management system
A comment processing unit that accepts input of comments from the first user and / or the second user via the information processing terminal for transaction processing related to the shared account and records them in a comment database. Have,
The comment processing unit instructs the comment and / or the transaction processing related to the shared account, or the history thereof, from the first user or the second user via the information processing terminal. Has a topic management department that assigns tags based on
In a state where the comment with the specified tag is output to the information processing terminal based on the request from the first user or the second user via the information processing terminal. When an instruction for transaction processing related to the shared account is received via the information processing terminal, a predetermined transaction condition corresponding to the specified tag is set as a default value.
The information processing terminal is an information processing terminal that requests the transaction processing unit to perform the transaction processing via the programming interface.

Images