JP2003323547A - Method and program for providing bank account information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method and a program for providing a bank account for providing a user with information on the balance in a bank account and efficiently managing the bank account. <P>SOLUTION: A management computer 21 calculates the amount of scheduled payment in a predicted request period by using a payment prediction function recorded in a payment prediction data memory part 24. If the payment prediction function depends on the history of payment, the management computer 21 specifies the payment history by using a key word included in a memorandum, and calculates the predicted balance based on the scheduled payment amount and the current balance. If the predicted balance exceeds the upper limit balance recorded in a notice condition data memory part 25, the management computer 21 notifies the user of the fact. If there is a shortage in the predicted balance relative to the lower limit balance, it is confirmed whether there is a bank account for compensating the shortage. If there is the bank account for compensating the shortage, the notice is given to the user together with a proposal of transferring money from the bank account to the one with the shortage. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an account information providing method and an account information providing program used when providing information on an account balance to a user.

[0002]

2. Description of the Related Art Today, users of deposit accounts of financial institutions often make various payments using the deposit accounts. Among these payments, there are usage charges for telephone, electricity, gas, water, etc., loan repayment, and credit card usage charges. In this case, these payments may be made using the automatic deposit account transfer service provided by the financial institution. In this automatic transfer service, a financial institution that receives a money collection consignment regularly deducts various charges from a predetermined account. By using such a service, the user can reliably pay various charges and repay the loan while saving the trouble of going to a store of a financial institution.

[0003]

However, in automatic transfer, loan repayment, etc., if the balance of the withdrawal amount or more is not in the user's deposit account on the day of withdrawal, the financial institution cannot withdraw. If it becomes impossible to withdraw, the reminder is notified to the user via telephone or letter. In addition, in the case of repayment of a loan, a penalty (demerit) such as the addition of past due interest may be imposed on the user.

Since the withdrawal information regarding various charges is notified to the user individually from the service providing company before the withdrawal date, the user can prepare the necessary balance in advance. However, since the notification date and the withdrawal date are different, the user may forget that there is an account withdrawal. In particular, the user does not always keep track of his or her own account balance, which may result in a careless lack of balance. Even in such a case, there is a case where a penalty is taken or a reminder is given and an unpleasant feeling is caused.

In addition, when a plurality of deposit account automatic transfer services are used, it may be troublesome twice to take measures for each withdrawal. You need to go through the procedure. Furthermore, if the deposit to this account is left unattended, such as a transfer of salary, the balance may be unnecessarily high.

[0006] Furthermore, a user who holds a plurality of accounts is
It is also possible to transfer money to this account from another account. However, which account should be transferred and how much should be transferred should be determined in consideration of the status of each account such as future balance transition and interest rates of multiple accounts.

The present invention has been made to solve the above problems, and an object thereof is to provide an account information providing a user with information regarding the balance of an account and efficiently managing the account. To provide a method and an account information providing program.

[0008]

In order to solve the above problems, the invention according to claim 1 stores a deposit / withdrawal prediction data storing a deposit / withdrawal prediction function for each deposit / withdrawal type into a user's account. A method for providing account information to the user using an account management system having means, a notification condition data storage means for recording a limit balance for notifying the user, and a management computer, the management computer Is an estimated amount calculation step of calculating an estimated amount of withdrawal / withdrawal to / from the account within a predetermined period using the deposit / withdrawal prediction function recorded in the deposit / withdrawal prediction data storage means, and the current balance and the previous value of the account. A balance forecasting step of calculating a future forecasted balance based on the planned withdrawal amount and a notification to the user when the forecasted balance exceeds the limit balance recorded in the notification condition data storage means. Go And summarized in that and a notification step.

According to a second aspect of the present invention, in the account information providing method according to the first aspect, the deposit / withdrawal prediction function is
It is a gist to include a function for calculating the planned deposit / withdrawal amount using a deposit / withdrawal history for a predetermined period to / from the account.

According to a third aspect of the present invention, in the account information providing method according to the second aspect, the deposit / withdrawal prediction function is
The gist is that it is a function that calculates the average value of past deposits and withdrawals.

According to a fourth aspect of the present invention, in the account information providing method according to the second aspect, the deposit / withdrawal prediction function is
The gist is that it is a function that calculates the highest past deposit / withdrawal amount.

The invention according to claim 5 is the method for providing account information according to claim 2, wherein the deposit / withdrawal prediction function is
The gist is that it is a function that calculates the minimum value of past deposits and withdrawals.

The invention according to claim 6 is the account information providing method according to any one of claims 2 to 5, wherein a keyword relating to a transaction is set in the identification of the deposit / withdrawal type, and the estimated amount is set. The gist of the calculating step is to extract a deposit / withdrawal history including the keyword in the abstract and calculate the scheduled deposit / withdrawal amount using the deposit / withdrawal amount of the deposit / withdrawal history.

The invention according to claim 7 is the method for providing account information according to any one of claims 1 to 6, wherein the user's account includes at least a first account and a second account. And the notification condition data storage means stores the first
The first lower limit balance is recorded as the limit balance of the account, and the second lower limit balance is recorded as the limit balance of the second account. In the account information providing method, the management computer may include the first lower limit balance. If the estimated balance of the account of the second account has a shortage amount with respect to the first lower limit balance, the estimated amount obtained by subtracting the insufficient amount from the estimated balance of the second account, and the second
And comparing the lower limit balance of the second account to the first account when the expected amount of money is greater than or equal to the second lower limit balance. The gist is to include the transfer proposal for the shortfall.

The invention according to claim 8 is the method for providing account information according to any one of claims 1 to 6, wherein the user's account includes at least a first account and a second account. And the notification condition data storage means stores the first
A first upper limit balance is recorded as the limit balance of the account, and a second upper limit balance is recorded as the limit balance of the second account. In the account information providing method, If the predicted balance of the account of the above-mentioned account causes a surplus amount with respect to the first upper limit balance, the expected amount of money obtained by adding the surplus amount to the predicted balance of the second account is compared with the second upper limit balance. If the expected amount of money is less than or equal to the second upper limit balance, the user is notified of the transfer of the surplus amount from the first account to the second account. The main point is to include.

The invention according to claim 9 is the invention according to claim 7 or 8.
In the account information providing method described in (1), when the user makes a transfer request for the transfer proposal of the notification,
The gist is that the management computer executes a transfer process of the transfer proposal.

According to a tenth aspect of the present invention, a deposit / withdrawal prediction data storage means for recording a deposit / withdrawal prediction function for each deposit / withdrawal type into a user's account, and a limit balance for notifying the user are recorded. A program for providing account information to the user by using an account management system having a notification condition data storage means and a management computer, wherein the management computer is used for depositing / withdrawing data recorded in the deposit / withdrawal prediction data storage means. An estimated amount calculation means for calculating an estimated deposit / withdrawal amount to the account within a predetermined period using a gold prediction function, and a future forecast balance based on the current balance of the account and the estimated deposit / withdrawal amount. And a function as a notifying means for notifying the user when the predicted balance exceeds the limit balance recorded in the notification condition data storage means. To.

The invention according to claim 11 is the program for providing account information according to claim 10, wherein the deposit / withdrawal prediction function uses the deposit / withdrawal history of the account for a predetermined period. The gist is to include a function to calculate the amount.

The invention according to claim 12 is, in the account information providing program according to claim 11, characterized in that the deposit / withdrawal prediction function is a function for calculating an average value of past deposit / withdrawal amounts. .

A thirteenth aspect of the present invention is the account information providing program according to the eleventh aspect, wherein the deposit / withdrawal prediction function is a function for calculating a maximum past deposit / withdrawal amount. .

The invention according to claim 14 is, in the account information providing program according to claim 11, characterized in that the deposit / withdrawal prediction function is a function for calculating a minimum value of past deposit / withdrawal amounts. .

The invention according to claim 15 is the same as claims 11 to 11.
In the account information providing program according to any one of 14 above, a keyword relating to a transaction is set in the identification of the deposit / withdrawal type, and the estimated amount calculation means extracts a deposit / withdrawal history including the keyword in a summary. The gist is to calculate the expected deposit / withdrawal amount using the deposit / withdrawal amount of the deposit / withdrawal history.

The invention according to claim 16 is the invention according to claims 10 to 10.
15. The account information providing program according to any one of 15, wherein the user's account includes at least a first account and a second account, and the notification condition data storage means stores the first account. A first lower limit balance is recorded as the limit balance of the account, and a second lower limit balance is recorded as the limit balance of the second account. The account information providing program causes the management computer to store the first balance. If the forecast balance of the account causes a shortfall with respect to the first lower limit balance,
If the expected amount of money obtained by subtracting the shortfall from the estimated balance of the second account and the second lower limit balance are further made to function, and the expected amount of money is equal to or greater than the second lower limit balance, It is a gist to include in the notification to the user a proposal to transfer the insufficient amount from the second account to the first account.

The invention according to claim 17 is the invention according to claim 10
15. The account information providing program according to any one of 15, wherein the user's account includes at least a first account and a second account, and the notification condition data storage means stores the first account. A first upper limit balance is recorded as the limit balance of the account, and a second upper limit balance is recorded as the limit balance of the second account. The account information providing program causes the management computer to store the first limit balance. When the forecast balance of the account causes a surplus amount with respect to the first upper limit balance,
If the estimated amount of money obtained by adding the surplus amount to the estimated balance of the second account and the second upper limit balance are further made to function, and the estimated amount of money is less than or equal to the second upper limit balance, The gist is that the notification to the user includes a transfer proposal of the surplus amount from the first account to the second account.

The invention according to claim 18 is, in the account information providing program according to claim 16 or 17, when the user makes a transfer request for the transfer proposal of the notification, the management computer Is to function as means for executing the transfer processing of the transfer proposal.

(Operation) According to the invention described in claim 1 or 10, the management computer uses the deposit / withdrawal prediction function recorded in the deposit / withdrawal prediction data storage means to deposit / withdraw to / from the account within a predetermined period. Calculate the estimated amount. Next, a future predicted balance is calculated based on the current balance of the account and the planned deposit / withdrawal amount. If the predicted balance exceeds the limit balance recorded in the notification condition data storage means, the user is notified. Therefore, the user can grasp the future forecast balance calculated by using the deposit / withdrawal forecast function. Therefore, when the account balance has an excess or deficiency, the user can take measures to correct the excess or deficiency by considering the future forecast balance.

According to the invention of claim 2 or 11,
The deposit / withdrawal prediction function includes a function of calculating a scheduled deposit / withdrawal amount using a deposit / withdrawal history of the account for a predetermined period. Even with regular deposits and withdrawals, the amount of deposits and withdrawals may fluctuate. Therefore, it is possible to calculate a certain estimated deposit / withdrawal amount based on the past record of deposit / withdrawal.

According to the invention of claim 3 or 12,
The deposit / withdrawal prediction function is a function for calculating an average value of past deposit / withdrawal amounts. Therefore, even if the amount of deposits and withdrawals in the past fluctuates, it is possible to calculate a more probable deposit and withdrawal amount.

According to the invention of claim 4 or 13,
The deposit / withdrawal prediction function is a function for calculating the highest past deposit / withdrawal amount. When the lower limit balance is used as the limit balance, it is possible to predict the possibility of exceeding the limit balance by assuming a large change in the withdrawal forecast. Further, when the upper limit balance is used as the limit balance, it is possible to predict the possibility of exceeding the limit balance by assuming a large change in the deposit prediction.

According to the invention of claim 5 or 14,
The deposit / withdrawal prediction function is a function for calculating the minimum value of past deposit / withdrawal amounts. When the lower limit balance is used as the limit balance, it is possible to predict the possibility of exceeding the limit balance assuming a small amount of deposit prediction. Further, when the upper limit balance is used as the limit balance, it is possible to predict the possibility of exceeding the limit balance by assuming a small withdrawal prediction.

According to the invention of claim 6 or 15,
Set a keyword to identify the deposit / withdrawal type. Then, the deposit / withdrawal history included in the abstract is extracted, and the planned deposit / withdrawal amount is calculated using the deposit / withdrawal amounts of the deposit / withdrawal history. Therefore, it is possible to efficiently extract a periodic deposit / withdrawal history.

According to the invention of claim 7 or 16,
When the predicted balance of the first account has a shortage amount with respect to the first lower limit balance, the expected amount obtained by subtracting the shortage amount from the predicted balance of the second account is compared with the second lower limit balance. To do. Then, when the estimated amount of money is equal to or more than the second lower limit balance, the notification to the user includes the transfer proposal of the insufficient amount from the second account to the first account. Therefore, the balance of each account can be adjusted within a range that does not exceed the limit balance.

According to the invention of claim 8 or 17,
When the forecast balance of the first account causes a surplus amount with respect to the first upper limit balance, the forecast amount of the second account plus the surplus amount is compared with the second upper limit balance. To do.
When the estimated amount is less than or equal to the second upper limit balance, the notification to the user includes a proposal to transfer the surplus amount from the first account to the second account. Therefore, the balance of each account can be adjusted within a range that does not exceed the limit balance.

According to the invention of claim 9 or 18,
When the user makes a transfer request for the transfer proposal of the notification, the management computer executes a transfer process of the transfer proposal. Therefore, the user can transfer money quickly.

[0035]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below with reference to FIGS. In the present embodiment, an account information providing method and an account information providing program used when providing information regarding the balance of the user's account to a user who holds a deposit account at a financial institution will be described. To provide this account information, the account management system 2
0 is used.

As shown in FIG. 1, the account management system 20
Is connected to the user terminal 10 and the banking system 30 via a network. This user terminal 10
It is used when receiving account information or instructing transfer or the like by communicating with the account management system 20. In this embodiment, a computer terminal or a mobile phone terminal is used as the user terminal 10.

The banking system 30 is a host computer system of a financial institution that manages user accounts. By accessing the banking system 30, it is possible to obtain deposit / withdrawal information and balance information regarding a deposit account.

The account management system 20 is a computer system managed by an account aggregator that provides an account aggregation service. Here, the account aggregation is an account information aggregation service that displays a plurality of accounts (banks, securities, etc.) on one screen. Normally, when using the online banking service, the user needs to manage the ID and the personal identification number registered in the financial institution for each account. In the account aggregation service, an account aggregator keeps the user's ID and personal identification number, logs in to the services of banks and securities companies, and provides the account information to the user. As a result, the user is freed from the trouble of managing the ID and the personal identification number and inputting the ID and the personal identification number for each login.

The account management system 20 includes a management computer 21 as shown in FIG. The management computer 21 has a control unit (CPU), a storage unit (RAM, ROM, hard disk, etc.), a data transmission / reception unit, etc., which are not shown. This management computer 21 includes processing procedures (including a planned amount calculation step, a balance prediction step, a notification step, a comparison step, etc.) described later regarding account information management.
Run the account information provision program for. As a result, the management computer 21 functions as means such as an estimated amount calculation means, a balance prediction means, a notification means, and a comparison means.

The management computer 21 is connected to a managed account data storage unit 22, a deposit / withdrawal history data storage unit 23, and a deposit / withdrawal prediction data storage unit 24 as deposit / withdrawal prediction data storage means. Further, the management computer 21 includes a notification condition data storage unit 25 and a predicted balance data storage unit 26 as notification condition data storage means.
Are connected.

FIG. 2 shows the managed account data storage unit 22.
As shown in, the managed account data 220 is recorded for the account (managed account) of the financial institution that is the target of the account aggregation service. The managed account data 220 is set when the user applies for a service request to the account aggregator. In this embodiment, the managed account data 220 includes
For each managed account, account identifier, user identifier, ID,
Data relating to the personal identification number and contact information are recorded in association with each other.

In the account identifier data area, the account
Data about the identifier for identifying the managed account for which the aggregation service has been requested is recorded. In the present embodiment, the account identifier is configured to include the financial institution code, branch code, deposit item code, and account number of the managed account.

In the user identifier data area, data relating to an identifier for identifying the account holder who is a user of the account aggregation service is recorded. In the present embodiment, the account aggregation service ID assigned by the account aggregator for each user is used. By using this account / aggregation service ID, the name, address, various attribute information, etc. of the account holder registered in another data storage unit can be extracted.

In the ID data area and the personal identification number data area, an ID and a personal identification number used when acquiring information about this account from the banking system 30 are recorded. This ID and personal identification number are used when the account management system 20 accesses the banking system 30 of the financial institution in which this account is opened and acquires various account information.

In the contact data area, data about a contact used when notifying the user is recorded.
In this embodiment, electronic mail is used as the notification means.
Therefore, in the contact data area, data regarding the electronic mail address of the contact desired by the user is recorded.

In the deposit / withdrawal history data storage unit 23, as shown in FIG. 3, deposit / withdrawal history data 230 relating to the deposit / withdrawal history of the managed account is recorded. The deposit / withdrawal history data 230 is recorded when the account management system 20 acquires deposit / withdrawal information from the banking system 30. In this embodiment, the account management system 20 accesses the banking system 30 in a predetermined cycle (here, once a day) to acquire deposit / withdrawal information. Then, the account management system 20 records the acquired deposit / withdrawal information as deposit / withdrawal history data 230.
In the deposit / withdrawal history data 230, data relating to the account identifier, summary, transaction date, deposit / withdrawal amount, and balance for each managed account are recorded in association with each other.

In the account identifier data area, data relating to an identifier for specifying the managed account in which deposit / withdrawal has been performed is recorded. In the summary data area, data about the summary included in the deposit / withdrawal information is recorded. This summary includes information about the supplier and the transaction content regarding deposit or withdrawal. For example, when a transfer is made from this account to another account, the holder's name of the transfer destination is recorded in the summary data area as the business partner. In the case of automatic withdrawal of electricity charges, telephone charges, etc. from this account, the details (“electricity charges”, “telephone charges”, etc.) are recorded as transaction details in the summary data area. Further, when the transfer is made to this account, the name and the name of the transfer person are recorded in the summary data area as the transaction partner. Furthermore, when cash is withdrawn using a cash card or the like, a "cash withdrawal" flag is recorded in the summary data area.

In the transaction date data area, data relating to the date of transaction such as deposit or withdrawal is recorded. In the deposit / withdrawal amount data area, the amount of money deposited into this account and data relating to the amount of money dispensed from this account are recorded.

In the balance data area, data relating to the balance resulting from the deposit and withdrawal is recorded. The balance included in the latest deposit / withdrawal history data 230 is the current balance of this account.

In the deposit / withdrawal prediction data storage section 24, as shown in FIG. 4, deposit / withdrawal prediction data 240 used when the account management system 20 makes a deposit / withdrawal prediction is recorded. The deposit / withdrawal prediction data 240 is recorded when the user sets balance prediction, which will be described later. In the present embodiment, the deposit / withdrawal prediction data 240 is recorded with data relating to an account identifier, a keyword, a deposit / withdrawal prediction function, a scheduled deposit / withdrawal date, and a remark for each managed account in association with each other.

In the account identifier data area, data relating to an identifier for identifying the managed account to which the deposit / withdrawal prediction is set is recorded. In the keyword data area, data regarding a keyword used for extracting the deposit / withdrawal history used for predicting the balance from the deposit / withdrawal history data storage unit 23 for each deposit / withdrawal type is recorded. For example, in the case of various charges, "telephone charge", "electricity charge",
Keywords such as "gas charge" or "water charge" included in the abstract are recorded. In addition, the salary and the like may be set to the name of the transfer person or the name of a storing organization such as a credit card company.

In the deposit / withdrawal prediction function data area, a function for predicting a future deposit / withdrawal amount (scheduled deposit / withdrawal amount) is recorded. This deposit / withdrawal prediction function includes a function for calculating an average value, a minimum value, a maximum value, etc. for the past 6 months. If the amount of money is determined in advance, a function that sets the amount of money for the scheduled deposit / withdrawal date is used. For example, in the case of setting for each month such as loan repayment, a function in which the repayment amount of the month is associated with the identifier of each month is set.

The scheduled deposit / withdrawal date data area records data relating to the scheduled deposit / withdrawal dates. For monthly deposits and withdrawals, please refer to "10th of every month" or "End of every month".
Etc. In the remarks data area, data relating to reference information regarding each deposit / withdrawal is recorded.

In the notification condition data storage section 25, as shown in FIG. 5, the notification condition data 250 relating to the condition when the account management system 20 notifies the user is recorded. The notification condition data 250 is recorded when the user sets balance prediction for a managed account described later. In the present embodiment, in the notification condition data 250, data regarding the account identifier, the desired forecast period, the lower limit balance as the limit balance, and the upper limit balance is recorded in association with each other for each managed account.

In the account identifier data area, data relating to the identifier for specifying the managed account is recorded. In the forecasted desired period data area, the management computer 2
1 makes a deposit / withdrawal prediction, and data relating to a period for calculating a forecast balance is recorded. In the present embodiment, the desired forecast period is “two days from the current day”, “one week from the current day”.
Alternatively, you can select from “1 month from the day”.

In the upper limit balance data area and the lower limit balance data area, data relating to the upper limit and the lower limit of the balance for notifying the user are recorded. If the upper limit balance and the lower limit balance have not been set, this is left blank. In this case, the upper limit balance is treated as unlimited and the lower limit balance is treated as "0", but the upper limit balance and the lower limit balance are not notified.

As shown in FIG. 6, the predicted balance data storage unit 26 records predicted balance data 260 regarding the balance predicted by the management computer 21. The forecast balance data 260 is recorded when the management computer 21 performs the forecast balance calculation process. In this embodiment,
In the forecast balance data 260, data relating to the account identifier, the forecast date, and the forecast balance are recorded in association with each other for each managed account.

In the account identifier data area, data relating to the identifier for specifying the managed account is recorded. In the forecast date data area, data regarding the date on which the forecast balance is assumed is recorded. Specifically, a date after the desired forecast period has elapsed from the date of calculating the forecast balance is used.

Data relating to the forecast balance on the forecast date is recorded in the forecast balance data area. When the management computer 21 newly calculates the forecast balance, the forecast balance data 260 is updated and recorded.

Next, in the system configured as described above, the procedure for carrying out the processing for notifying the user of the balance will be described. In the present embodiment, the processing at the time of registering the managed account, the processing at the time of calculating the predicted balance, the notification processing regarding the upper limit balance, and the notification processing regarding the lower limit balance will be described in this order. Further, the processing regarding the user who has received these various notifications will be described.

(Processing at Registration) First, the user specifies an account to be managed by the account aggregator and applies for a request for using the account aggregation service. This application for use includes the account identifier of the account to be managed and the email address of the contact. The account aggregator that accepts this application gives the user a user identifier (account aggregation service ID) and a password. Then, data relating to the account identifier and contact information is recorded in the managed account data storage unit 22 in association with the given user identifier. Then, the account aggregator provides the user with an account aggregation service ID and password for using the account aggregation service.

Next, the user sets various conditions used for the balance prediction and notification of the managed account. In this case, the user uses the web page for setting the balance forecast provided by the account management system 20. Specifically, the user uses the user terminal 10 to access the account management system 20 and makes a balance forecast setting request. In this case, the user uses the account / aggregation service ID and password. The account management system 20 authenticates the user, and when the authentication is completed, outputs the display screen 600 shown in FIG. 13 to the user terminal 10.

On this display screen 600, a selection tab 601, a selection tab 602, and a selection tab 6 which display managed accounts are displayed.
03 is included. Select the account to be set using this selection tab. In this embodiment, as shown in FIG.
Assume that one bank account is a managed account. The display screen 600 also includes a keyword input field 610, a prediction method input field 611, a scheduled date input field 612, and a remarks input field 613.

In this keyword input field 610, a keyword used when the balance is predicted based on the deposit / withdrawal history is set. Specifically, the words included in the summary of the deposit / withdrawal information acquired from the banking system 30 are set as keywords. In this embodiment, the electricity charge, the telephone charge, and the name of the credit company are set. Note that no keyword is set for loan repayment because no keyword is used when calculating the estimated balance.

In the predicting method input field 611, a predicting method of the amount of money to be deposited and withdrawn which is used when calculating the predicted balance is set. Here, it is possible to select from “6 month average value”, “6 month maximum value”, “6 month minimum value, etc.” and “monthly setting”, and each selection item is displayed in a pull-down display method. In addition,
When "Monthly setting" is selected, a screen for inputting the deposit / withdrawal amount for each month is displayed. It is set by entering the input field on this screen.

In the scheduled date input field 612, a scheduled date for depositing and withdrawing money is set. Here, for example, "1 monthly
You can select "0 day" or "the end of every month". Again, each item is selected using the pull-down display method.

In the remarks input field 613, reference information regarding each deposit / withdrawal is input. This remarks input field 613 is used when the user additionally notes the contents and notes regarding deposit and withdrawal for reference.

Further, on the display screen 600, a lower limit balance input field 620 and an upper limit balance input field 62 for setting notification conditions are set.
Including 1. The lower limit balance input field 620 is an input field for setting a lower limit balance for which notification is desired, and the upper limit balance input field 621 is an input field for setting an upper limit balance for which notification is desired. For example, here, the user is notified when the predicted balance of the account on the selection tab 601 becomes negative or exceeds 1 million yen.

Further, the display screen 600 includes a prediction desired period input field 630. The prediction desired period input field 630 is an input field for setting a period for which the balance is predicted. In this embodiment, it is possible to select from "1 month from the current day", "1 week from the current day", or "the current day or 2 days". For example, when “1 month from the current day” is set, the balance is predicted within 1 month from the current day, and when the notification condition is met during that period, the notification is given. In this embodiment, the desired forecast period is common to a plurality of managed accounts.

Similarly, the selection tab 602 and the selection tab 60
Various settings are also made for the managed accounts of 3. The setting execution button 640 is a selection button for registering the conditions set on the display screen 600. This setting execution button 64
When 0 is clicked, the user terminal 10 displays the display screen 60.
The various setting data input to 0 are transmitted to the account management system 20 together with the deposit account identifier. Upon receiving this data, the management computer 21 records data relating to the keyword, the deposit / withdrawal prediction function corresponding to the selected forecasting method, the scheduled deposit / withdrawal date, and the remarks in the deposit / withdrawal prediction data storage unit 24 in association with the account identifier. Further, the management computer 21 records data relating to the desired forecast period, the lower limit balance and the upper limit balance in the notification condition data storage unit 25 in association with the account identifier. In this way, various registrations of managed accounts are performed.

(Predicted Balance Calculation Processing) Next, the predicted balance calculation processing will be described with reference to FIG. The management computer 21 executes this processing at a fixed time every day.

First, the management computer 21 acquires deposit / withdrawal information of the managed account (S1-1). in this case,
The management computer 21 is a managed account data storage unit 22.
Access the banking system 30 for managing the managed account recorded in. Then, the deposit / withdrawal information of the managed account of the day is acquired from the banking system 30 by using the ID and the secret code recorded in the managed account data storage unit 22. This deposit / withdrawal information includes a summary, transaction date, deposit / withdrawal amount, and balance data. Then, the management computer 21 records the acquired deposit / withdrawal information in the deposit / withdrawal history data storage unit 23 together with the account identifier of this account.

Next, the management computer 21 identifies the deposit / withdrawal prediction data 240 for which the deposit / withdrawal is scheduled in the desired forecast period (S1-2). Specifically, the management computer 21 first extracts the desired forecast period of this account from the notification condition data storage unit 25.

Next, the management computer 21 specifies the deposit / withdrawal prediction data 240 including the scheduled deposit / withdrawal date within the desired forecast period from the present. In this case, consider the business day of the financial institution. That is, for example, when the withdrawal date of the account withdrawal set to “10th of every month” corresponds to a holiday of a financial institution, the next business day is set as the deposit / withdrawal date. In the case of "the end of every month", the last day of the current month will be the deposit / withdrawal date.

Next, the management computer 21 calculates the expected deposit / withdrawal amount based on the specified deposit / withdrawal prediction data 240. In this case, the specified deposit / withdrawal prediction data 240
Processing differs depending on the deposit / withdrawal prediction function included in (S1-
3). When the deposit / withdrawal prediction function is a function that does not depend on the deposit / withdrawal history (“No” in step (S1-3)), the month of the scheduled deposit / withdrawal date within the desired forecast period is specified and the amount is used (S1). -4).

On the other hand, when the deposit / withdrawal prediction function is a function dependent on the deposit / withdrawal history (in the case of “Yes”), the management computer 21 calculates the estimated deposit / withdrawal amount based on the history of the predetermined period. In this case, the deposit / withdrawal prediction function includes “average value for the past 6 months”, “maximum value for the past 6 months” or “minimum value for the past 6 months”. First, the management computer 21
Extracts the deposit / withdrawal history data 230 for a predetermined period based on the keyword of the managed account (S1-5). For example, when a “average value for 6 months” calculation function is recorded as a deposit / withdrawal prediction function whose keyword is “electricity rate”,
The management computer 21 first extracts the deposit / withdrawal history data 230 for the past 6 months from the deposit / withdrawal history data 230 including “electricity charge” in the description.

Next, the expected deposit / withdrawal amount is calculated based on the deposit / withdrawal amount included in the extracted deposit / withdrawal history data 230 (S1-6). For example, when the “average value for 6 months” calculation function is recorded as the deposit / withdrawal prediction function, the estimated deposit / withdrawal amount is calculated by calculating the average value of the specified deposit / withdrawal amounts. "Maximum value for 6 months" as a deposit / withdrawal prediction function
When the calculation function or the “minimum value for 6 months” calculation function is recorded, the maximum value or the minimum value of the specified deposit / withdrawal amount is calculated as the scheduled deposit / withdrawal amount.

The processes of steps (S1-3) to (S1-6) are performed on all the deposit / withdrawal prediction data 240 associated with this managed account. Next, the management computer 21 calculates the forecast balance for the forecast period (S1-7). Specifically, the management computer 21
The current balance of this managed account is stored in the forecast balance data storage unit 2
The forecast balance is calculated by adding and subtracting all the calculated deposit and withdrawal amounts extracted from 6.

Then, the management computer 21 records the calculated forecast balance in the forecast balance data storage unit 26. In this case, the date obtained by adding the desired forecast period to the current date is also recorded as the forecast date. This predicted balance calculation process is performed for all managed accounts. From the above,
The forecast balance calculation process ends.

(Upper limit balance notification process) Next, the upper limit balance notification process will be described with reference to FIG. This process is executed only for the account for which the upper limit balance is set in the notification condition data 250 after the above-described predicted balance calculation process is completed.

First, the management computer 21 compares the predicted balance calculated in the predicted balance calculation process with the upper limit balance set by the user (S2-1). In this case, the management computer 21 notifies the notification condition data storage unit 25 of the upper limit balance recorded in association with the account identifier of this managed account.
Extract from. When the predicted balance is less than or equal to the upper limit balance (“No” in step (S2-1)), the management computer 21 ends the upper limit balance notification process.

On the other hand, when the predicted balance exceeds the upper limit balance (in the case of "Yes" in step (S2-1)), the management computer 21 sends an electronic mail to the user terminal 10 (S2-2). . Specifically, the management computer 21 extracts the contact information of this user from the managed account data storage unit 22 and sends an e-mail to this contact information. This e-mail contains information that there is a possibility that the upper limit balance will be exceeded and an operation proposal.

User terminal 10 receiving this e-mail
Causes the display screen 500 shown in FIG. 11 to be output. This display screen 500 includes a tag 501 for displaying the balance and a tag 502 for displaying the details of the operation proposal in the underlined area. Here, the tag 501 includes a URL (Uniform Resource Locator) for displaying a balance list of a user's managed account, which will be described later. Further, the tag 502 includes a URL for displaying the operation proposal from the financial institution. This tag 5
When 02 is clicked, the browser is activated and the introduction screen of various products proposed by the financial institution is displayed. With the above, the upper limit balance notification process ends.

(Lower limit balance notification process) Next, the lower limit balance notification process will be described with reference to FIG. This processing is also executed only for the account identifier for which the lower limit balance is set in the notification condition data 250 after the above-described predicted balance calculation processing is completed.

First, the management computer 21 compares the predicted balance calculated in the predicted balance calculation process with the lower limit balance set by the user (S3-1). In this case, the management computer 21 notifies the notification condition data storage unit 25 of the lower limit balance recorded in association with the account identifier of this managed account.
Extract from. When the predicted balance is equal to or more than the lower limit balance (“No” in step (S3-1)), the management computer 21 ends the lower limit balance notification process.

On the other hand, when the estimated balance of this account is less than the lower limit balance and a shortage occurs (in the case of "Yes" in step (S3-1)), the management computer 21 determines that the other managed account held by this user. The predicted balance of is extracted (S3-2). Specifically, the management computer 21 uses the managed account data storage unit 22 to identify the user identifier associated with the account identifier for this managed account. Next, the account identifier associated with the specified user identifier is extracted from the managed account data storage unit 22.
Then, the management computer 21 extracts the predicted balance associated with the extracted account identifier from the predicted balance data storage unit 26.

In the present embodiment, the expected balance of “A Bank Yotsuya Branch Ordinary 123456” as the first account is “15,0”.
It is assumed that there may be a shortage of "00 yen". Then, it is confirmed whether or not there is an account that can cover the shortfall (S3-3). Specifically, it is checked whether or not there is a managed account with an estimated amount of money that is obtained by subtracting the shortfall amount from the estimated balance of more than the lower limit balance. Then, the managed account having the largest difference between the estimated amount and the lower limit balance estimated balance is used as the transfer source account (second account). Here, "Bank B Akasaka Branch Ordinary 654321" is used as the second account.

If there is an account that can cover the shortfall ("Yes" in step (S3-3)), the management computer 21 sends an electronic mail including a transfer proposal (S3-4). In this case, specifically, the management computer 21 specifies the contact address of this user from the managed account data storage unit 22 and sends an e-mail to this contact address.

User terminal 10 receiving this e-mail
, The display screen 510 shown in FIG. 12 is output. This display screen 510 includes a tag 511 for displaying the balance and a tag 512 for displaying the details of the transfer proposal in the underlined area. Here, the tag 511 includes a URL for displaying a balance list of user-managed accounts, which will be described later. Further, the tag 512 has a URL for displaying a transfer proposal from the financial institution.
Is included.

On the other hand, if there is no account that can cover the shortfall (“No” in step (S3-3)), the management computer 21 notifies that the forecast balance may be less than or equal to the lower limit balance. Is sent by e-mail (S3-5). This display screen 510 includes a tag 511 for displaying the balance. With the above, the lower limit balance notification process ends.

(Proposal Execution Process) Next, the process using the electronic mail received by the user terminal 10 will be described with reference to FIG. The user who has read the e-mail sends various display requests to the account management system 20 using the tags included in the e-mail (S4-1). For example, when the "balance display" tag (501, 511) is clicked, the browser of the user terminal 10 is activated and the account management system 2
Send a balance display request to 0. When the tag (502, 512) related to the proposal from the financial institution is clicked, the user terminal 10 sends a display request for the operation proposal or the transfer proposal to the account management system 20.

Upon receiving this display request, the management computer 21 sends a user authentication screen to the user terminal 10 (S
4-2). This user authentication screen is screen data for allowing the user to transmit the account / aggregation service ID and password. The user terminal 10 receiving this data displays a user authentication screen (S4-
3). Here, the user can
The ID for the aggregation service, the password, etc. are input and transmitted to the account management system 20 (S4-4).

Management computer 2 which received this data
1 executes user authentication (S4-5). If the user authentication is successful, the data requested by the user is transmitted (S4-6). Here, it is assumed that the balance display request is made by clicking the balance display tag included in the electronic mail. In this case, the management computer 21 identifies the account based on the user identifier authenticated by the user, and extracts the current balance and the predicted balance from the deposit / withdrawal history data storage unit 23 and the predicted balance data storage unit 26. Then, the management computer 21 transmits the balance list data created by editing the extracted data to the user terminal 10.

The user terminal 10 receiving this data,
A balance list is displayed (S4-7). For example, in the case of a balance request from the user who has received the upper limit balance notification, the display screen 710 shown in FIG. 14 is output to the user terminal 10.
The display screen 710 includes a list of user-managed accounts. Here, there is a possibility that the predicted balance of the account of Bank A exceeds the upper limit balance (here, “50,000 yen” is assumed). Further, the display screen 710 includes a balance forecast setting button 711 and a proposal display button 712. When the balance forecast setting button 711 is clicked, the display screen 600 is output to the user terminal 10. On the other hand, when the proposal display button 712 is clicked, an introduction screen of various products proposed by the financial institution is displayed.

On the other hand, in the case of the balance request from the user who has received the lower limit balance notification, the display screen 720 shown in FIG. 15 is output to the user terminal 10. The display screen 720 includes a list of accounts managed by the user. Here, it is shown that the predicted balance of the account of Bank A may be lower than the lower limit balance (here, “0 yen” is assumed). Further, the display screen 720 includes a balance forecast setting button 721 and a proposal display button 722. When the balance forecast setting button 721 is clicked, the display screen 600 is output.

Here, it is assumed that the proposal display button 722 is clicked. When the proposal display button 722 is clicked, the user terminal 10 transmits a proposal display request to the account management system 20 (S4-8). The account management system 20 that has received this proposal display request transmits proposal data to the user terminal 10 (S4-9). In this embodiment,
The management computer 21 specifies the management target account in which the difference between the predicted balance and the lower limit balance is greater than or equal to the shortage amount, and the difference is the largest. Then, the management computer 21 generates proposal data for proposing the transfer of the insufficient amount from the specified account. Further, this proposal data includes data for pulling down the account of this user. Then, the management computer 21 sends this proposal data to the user terminal 10
Send to.

On the user terminal 10 receiving this data, the display screen 730 relating to the transfer proposal from the financial institution shown in FIG. 16 is displayed (S4-10). This display screen 73
In 0, a transfer source selection button 731 and a transfer amount input field 73
3 and a transfer execution button 735 are included. By using the transfer source selection button 731, the transfer source account can be selected. The transfer source selection button 731 is a pull-down display type selection button for selecting the account to be managed by this user. In this embodiment, a managed account having the largest difference between the predicted balance and the lower limit balance is set as the initial value. The transfer amount input field 733 is a field for inputting the transfer amount. In this column, the amount of money (deficit) required for compensation is set in advance as an initial value.
The user can change this amount if necessary. Even when the tag 512 shown in FIG. 12 is clicked, this display screen 730 is displayed after user authentication.

When the transfer execution button 735 is clicked, the user terminal 10 sends a transfer request to the account management system 20 (S4-11). For this transfer request,
It includes data on the transfer source account identifier, the transfer destination account identifier, and the transfer amount.

Upon receiving this transfer request, the account management system 20 transmits a transfer instruction to the banking system 30 (S4-12). This transfer instruction is given using the ID or the personal identification number recorded in the managed account data storage unit 22. With the above, the proposal process is completed.

As described above, according to this embodiment, the following effects can be obtained. In the above embodiment, when the predicted balance exceeds the upper limit balance set as the notification condition or becomes lower than the lower limit balance, the management computer 21 notifies the user.
Therefore, the user can grasp the transition of the balance with respect to the scheduled deposit / withdrawal. For example, when the forecast balance exceeds the upper limit balance, it is possible to transfer to a financial product with a more favorable interest rate.

It is also possible to set an upper limit balance as a measure for the payoff system. Here, the payoff system is a system in which, when a financial institution fails in business, the deposit insurance organization, on behalf of the financial institution, guarantees a refund with a principal amount of 10 million yen and the corresponding interest as an upper limit. Therefore, for example, the upper limit balance is set within the guaranteed refund range. Further, the upper limit balance may be set beyond the guaranteed refund range depending on the rating of the financial institution. Then, when the balance exceeds this, the management computer 21 proposes transfer to another deposit account. As a result, the safety of deposits can be improved.

On the other hand, when the balance is insufficient, the financial institution cannot withdraw from the user's deposit account.
When such an inability to withdraw occurs, a loan contract, service provision contract, or the like may be subject to a penalty (demerit) such as payment of late interest or suspension of service provision. The user can prevent such a disadvantage from occurring.

In the above embodiment, the deposit / withdrawal prediction data storage unit 24 records deposit / withdrawal prediction data 240. In the deposit / withdrawal prediction data 240, data relating to an account identifier, a keyword, a deposit / withdrawal prediction function, a scheduled deposit / withdrawal date, and a remark are recorded in association with each other for each managed account. Then, the management computer 21 calculates the forecast balance based on the deposit / withdrawal forecast function. Even if there are regular deposits and withdrawals to and from the account, the amount often fluctuates. Then, this fluctuation varies depending on the type of deposit and withdrawal.
Therefore, the scheduled deposit / withdrawal amount can be calculated by a method according to the type of the regular deposit / withdrawal.

In the above embodiment, the deposit / withdrawal prediction data storage unit 24 records deposit / withdrawal prediction data 240. This deposit / withdrawal prediction data 240 records data relating to the scheduled deposit / withdrawal date for each managed account. Therefore, the management computer 21 can calculate the forecast balance even when the forecast period is long.

In the above embodiment, the deposit / withdrawal prediction data storage unit 24 stores deposit / withdrawal prediction data 240. In the deposit / withdrawal prediction data 240, a keyword is recorded for each managed account. When the management computer 21 calculates the expected deposit / withdrawal amount based on the history of the predetermined period, the deposit / withdrawal history data 230 of the predetermined period is extracted based on the keyword of the managed account. The expected deposit / withdrawal amount is calculated based on the deposit / withdrawal history data 230. Therefore, normally, the deposit / withdrawal history data 230 for efficiently calculating the scheduled deposit / withdrawal amount can be specified by using the summary added to the deposit / withdrawal information.

In the above embodiment, the notification condition data 250 is recorded in the notification condition data storage unit 25.
In this notification condition data 250, data regarding an account identifier, a desired forecast period, an upper limit balance, and a lower limit balance are recorded in association with each other for each managed account. For this reason,
It is possible to set an upper limit balance and a lower limit balance for each managed account. Therefore, the upper limit balance and the lower limit balance can be set individually according to the usage method and type of the account.

In the above embodiment, the account that is the target of the account aggregation service is recorded in the managed account data storage unit 22. Then, when the predicted balance of the specific account is less than or equal to the lower limit balance, the management computer 21 extracts the predicted balance of other managed accounts held by this user. Then, check whether there is an account that can cover the shortfall. Specifically, it is checked whether or not there is another managed account whose amount obtained by subtracting the shortfall amount from the forecast balance is equal to or more than the lower limit balance. If there is an account that can cover the shortfall, the management computer 21 sends an e-mail including a transfer proposal. Therefore, the user can efficiently consider the countermeasure.

In the above embodiment, when the display screen 720 is clicked, the display screen 730 proposed by the financial institution is displayed on the user terminal 10. This display screen 730
The transfer source account and transfer amount are set as initial values. Further, the transfer source selection button 731 on the display screen 730
Is a pull-down display type selection button for selecting the account to be managed by this user. Therefore, the user can efficiently make a transfer request. Therefore, the user can quickly and easily eliminate the possibility of insufficient balance.

The transfer source account set as the initial value is a managed account in which the difference between the predicted balance and the lower limit balance is greater than or equal to the shortfall amount, and the difference is the largest. For this reason,
You can use an account that you can afford as a transfer source account.

In the above embodiment, the “balance display” tag (501, 51) on the display screen 500 or the display screen 510 is displayed.
When 1) is clicked, the user terminal 10 activates the browser and sends a request to display the balance to the account management system 20. Then, after the user authentication, the display screen 710 and the display screen 720 are output to the user terminal 10. For this reason,
The user can list the current balance and forecast balance.

In the above embodiment, the management computer 21 executes the forecast balance calculation processing at a fixed time every day. Then, following this process, the upper limit balance notification process and the lower limit balance notification process are executed. Therefore, the user can receive a notification based on a new deposit / withdrawal status every day. In addition, it is possible to obtain a forecast balance according to the deposit / withdrawal status.

The above embodiment may be modified into the following modes. -In the above-mentioned embodiment, although the notification is performed using a plurality of managed accounts, a single account may be targeted. This also allows the management computer 21 to make a notification regarding the balance.

In the above embodiment, the account aggregator provides an account aggregation service that aggregates accounts of a plurality of financial institutions. Alternatively, an account aggregation service that manages an account opened in one financial institution may be provided. Also, the financial institution itself may provide the account aggregation service. In this case, the account management system 20 is provided in the banking system 30. This allows financial institutions themselves to provide various services.

In the above embodiment, the scheduled deposit / withdrawal date is a scheduled date that is regularly performed every month, such as “10th of every month” or “the end of each month”. In addition to this, bi-monthly scheduled dates or quarterly scheduled dates may be set.

In the above embodiment, various charges, loan repayments and credit repayments are assumed as deposits / withdrawals used for balance prediction. In addition to this, other withdrawals or flat-rate remittances may be used. For example, you may use deposit / withdrawal relating to broadcast reception fee or tax payment.

In the above embodiment, the transfer proposal is made only in the lower limit balance notification process. In addition to this, a transfer proposal may be made in the upper limit balance notification process. For example,
If the predicted balance of the first account exceeds the upper limit balance (first upper limit balance) and surplus money is generated, a proposal is made to transfer the surplus money to the second account. As the second account, an account with a high interest rate is selected from the accounts that do not exceed the upper limit balance (second upper limit balance) of this account even if the surplus is added to the estimated balance of this second account. . As a result, surplus money can be transferred to an account with a relatively high interest rate, and efficient asset management can be performed.

In the above-described embodiment, when the deposit / withdrawal prediction function is a function that depends on the deposit / withdrawal history, the management computer 21 calculates the scheduled deposit / withdrawal amount based on the history of the predetermined period. In this case, the management computer 21 uses the keyword to deposit / withdrawal history data 23 used for deposit / withdrawal prediction.
Extract 0. In addition to this, the management computer 21 may further extract only a periodic deposit / withdrawal history from the extracted data, and use this to perform deposit / withdrawal prediction. In this case, the transaction date included in the deposit / withdrawal history data 230 extracted based on the keyword is used. That is,
This transaction date is compared with the expected deposit / withdrawal date included in the deposit / withdrawal prediction data 240. Then, the deposit / withdrawal prediction is performed using only the deposit / withdrawal history in which the transaction date matches the scheduled deposit / withdrawal date, and the deposit / withdrawal history in which the transaction date is within a predetermined period from the scheduled deposit / withdrawal date. For example, when a supplier name is used as a keyword, the deposit / withdrawal history may include deposit / withdrawal related to regular transactions and irregular transactions. Also in this case, the regular deposit / withdrawal history data 230 can be specified, and the planned deposit / withdrawal amount can be calculated accurately.

In the above embodiment, the expected deposit / withdrawal date and the deposit / withdrawal amount are calculated based on the deposit / withdrawal prediction data 240 recorded in the deposit / withdrawal prediction data storage unit 24. The deposit / withdrawal prediction data 240 is set by the user using the display screen 600. Instead of this, the management computer 21 may set a part of the deposit / withdrawal prediction data 240. The process will be described below.

First, the management computer 21 extracts a summary including a keyword common to each account from the deposit / withdrawal history data storage unit 23. Then, the intervals of transaction days of the extracted deposit / withdrawal history data 230 are calculated. If this interval has regularity, it is determined that the deposit / withdrawal history data 230 has periodicity. In this case, the expected deposit / withdrawal date estimated from this keyword and the periodicity is specified and recorded in the deposit / withdrawal prediction data storage unit 24. Next, the management computer 21 notifies the user and prompts the user to set a method for predicting the expected deposit / withdrawal amount.

Then, when the user sets a forecasting method of the expected deposit / withdrawal amount, this deposit / withdrawal forecast data 240 is used for the deposit / withdrawal forecast. Thereby, the user can efficiently set the deposit / withdrawal prediction data 240. In addition, it is possible to reduce the omission of prediction of regular deposits and withdrawals.

In the above embodiment, when the transfer proposal is made, the managed account having the largest difference from the lower limit balance in the predicted amount obtained by subtracting the shortfall from the predicted balance is used as the transfer source account (second account). Instead of this, it is possible to use the managed account having the lowest interest rate because the difference between the predicted balance and the lower limit balance is equal to or more than the shortfall amount. As a result, the user can efficiently manage the assets. Further, the transfer source account may be set in advance by the customer.

In the above embodiment, the management computer 21 executes the lower limit balance notification process for each managed account.
Instead of this, one user may collectively perform the processing regarding the account of this user. As a result, when the balances of the plurality of managed accounts are lower than the lower limit balance, it is possible to set the priority and make the transfer proposal. For example, a proposal is made to preferentially transfer the one with the earliest scheduled withdrawal date.

In the above embodiment, the management computer 21 separately performs the upper limit balance notification process and the lower limit balance notification process. Alternatively, it may be performed in one process. As a result, it is possible to collectively notify the information regarding the accounts that exceed the upper limit balance or fall below the lower limit balance among the user's managed accounts.

In the above embodiment, the forecast balance after the desired forecast period has been displayed on the display screen 710 and the display screen 720. Instead of this, the transition of the forecast balance may be displayed using a graph or a table. Specifically, the management computer 21 calculates the transition of the balance based on the deposit / withdrawal amount and the scheduled deposit / withdrawal date. This allows the user to grasp the change in the balance in more detail.

In the above embodiment, the management computer 21 performs the balance calculation process, the upper limit balance notification process, and the lower limit balance notification process every day. Therefore, the management computer 21 is notified every day when the predicted balance of the managed account exceeds the upper limit balance or the lower limit balance. Alternatively, when the notification is made once, the notification may not be made for a predetermined period. In this case, the final notification date is recorded in the notification condition data storage unit 25, and the notification is skipped for a predetermined non-notification period (for example, one day) from the final notification date. As a result, it is possible to avoid the annoyance caused by the notification being given multiple times.

The non-notification period may be set for each user or each managed account. In this case, for example, the non-notification period is recorded for each managed account. Then, the management computer 21 performs the notification after the lapse of the date obtained by adding the non-notification period to the final notification date. As a result, various services can be provided according to the situation of the user.

In the above-described embodiment, each data is divided and recorded in each storage unit (22 to 26) in the account management system 20. The data may be recorded in another form as long as they can be associated with each other.

[0128]

As described in detail above, according to the present invention,
It can provide information about future forecast balances for your managed accounts. Furthermore, when targeting a plurality of managed accounts, efficient transfer can be proposed according to changes in the future balance.

[Brief description of drawings]

FIG. 1 is a system schematic diagram of an embodiment of the present invention.

FIG. 2 is an explanatory diagram of data recorded in a managed account data storage unit.

FIG. 3 is an explanatory diagram of data recorded in a deposit / withdrawal history data storage unit.

FIG. 4 is an explanatory diagram of data recorded in a deposit / withdrawal prediction data storage unit.

FIG. 5 is an explanatory diagram of data recorded in a notification condition data storage unit.

FIG. 6 is an explanatory diagram of data recorded in a forecast balance data storage unit.

FIG. 7 is an explanatory diagram of a processing procedure according to the embodiment of the present invention.

FIG. 8 is an explanatory diagram of a processing procedure according to the embodiment of this invention.

FIG. 9 is an explanatory diagram of a processing procedure according to the embodiment of this invention.

FIG. 10 is an explanatory diagram of a processing procedure according to the embodiment of the present invention.

FIG. 11 is an explanatory diagram of a display screen output to the user terminal.

FIG. 12 is an explanatory diagram of a display screen output to the user terminal.

FIG. 13 is an explanatory diagram of a display screen output to a user terminal.

FIG. 14 is an explanatory diagram of a display screen output to a user terminal.

FIG. 15 is an explanatory diagram of a display screen output to the user terminal.

FIG. 16 is an explanatory diagram of a display screen output to the user terminal.

[Explanation of symbols]

20 ... Account management system, 21 ... Scheduled amount calculation means, balance prediction means, management computer as notification means, 24 ...
Deposit / withdrawal prediction data storage section as deposit / withdrawal prediction data storage means, 25 ... Notification condition data storage section as notification condition data storage means.

Claims (18)

[Claims] 1. A deposit / withdrawal prediction data storage unit for recording a deposit / withdrawal prediction function for each deposit / withdrawal type into a user's account, and a notification condition data storage unit for recording a limit balance for notifying the user, A method of providing account information to the user using an account management system having a management computer, wherein the management computer uses a deposit / withdrawal prediction function recorded in the deposit / withdrawal prediction data storage means, An estimated amount calculation step of calculating an estimated deposit / withdrawal amount to the account within a predetermined period; a balance prediction step of calculating a future estimated balance based on the current balance of the account and the estimated deposit / withdrawal amount, A method for providing account information, comprising a notification step of notifying the user when the predicted balance exceeds the limit balance recorded in the notification condition data storage means. 2. The account according to claim 1, wherein the deposit / withdrawal prediction function includes a function for calculating the scheduled deposit / withdrawal amount by using a deposit / withdrawal history of the account for a predetermined period. Information provision method. 3. The account information providing method according to claim 2, wherein the deposit / withdrawal prediction function is a function for calculating an average value of past deposit / withdrawal amounts. 4. The account information providing method according to claim 2, wherein the deposit / withdrawal prediction function is a function for calculating the highest past deposit / withdrawal amount. 5. The account information providing method according to claim 2, wherein the deposit / withdrawal prediction function is a function for calculating a minimum past deposit / withdrawal amount. 6. A transaction-related keyword is set for identifying the deposit / withdrawal type, and the deposit / withdrawal history including the keyword in the abstract is extracted in the scheduled amount calculation step, and the deposit / withdrawal amount of the deposit / withdrawal history is used. 3. The estimated deposit / withdrawal amount is calculated by
5. The account information providing method according to any one of items 5 to 5. 7. The user's account must have at least a first
And a second account, the notification condition data storage means records a first lower limit balance as the limit balance of the first account, and a second lower limit balance as the limit balance of the second account. A lower limit balance is recorded, and in the method for providing account information, the management computer, when the estimated balance of the first account has a shortage amount with respect to the first lower limit balance, the second account. Further comprising a step of comparing an expected amount of money obtained by subtracting the deficiency amount from the estimated balance of the second balance with the second lower limit balance, and if the expected amount of money is equal to or more than the second lower limit balance, to the user. The account information providing method according to any one of claims 1 to 6, wherein the notification of (1) includes a transfer proposal of the shortage amount from the second account to the first account. 8. The user's account must have at least a first
Account and second account, the notification condition data storage means records a first upper limit balance as a limit balance of the first account, and a second limit account as a limit balance of the second account. An upper limit balance is recorded, and in the account information providing method, the management computer, when the estimated balance of the first account causes a surplus amount with respect to the first upper limit balance, the second account. Further comprising a step of comparing an estimated amount of money, which is obtained by adding the surplus amount to the estimated balance of, and the second upper limit balance, and when the estimated amount of money is less than or equal to the second upper limit balance, to the user. The account information providing method according to any one of claims 1 to 6, wherein the notification includes a proposal for transferring the surplus amount from the first account to the second account. 9. The management computer executes a transfer process of the transfer proposal when the user requests a transfer for the transfer proposal of the notification. The account information provision method described. 10. A deposit / withdrawal prediction data storage unit that records a deposit / withdrawal prediction function for each deposit / withdrawal type into a user's account, and a notification condition data storage unit that records a limit balance for notifying the user, A program for providing account information to the user using an account management system having a management computer, wherein the management computer uses a deposit / withdrawal prediction function recorded in the deposit / withdrawal prediction data storage means, An estimated amount calculation means for calculating an estimated deposit / withdrawal amount to the account within a predetermined period; a balance prediction means for calculating a future estimated balance based on the current balance of the account and the estimated deposit / withdrawal amount; A program for providing account information for causing the user to be notified when the predicted balance exceeds the limit balance recorded in the notification condition data storage means. 11. The account according to claim 10, wherein the deposit / withdrawal prediction function includes a function for calculating the scheduled deposit / withdrawal amount by using a deposit / withdrawal history of the account for a predetermined period. Information provision program. 12. The account information providing program according to claim 11, wherein the deposit / withdrawal prediction function is a function for calculating an average value of past deposit / withdrawal amounts. 13. The account information providing program according to claim 11, wherein the deposit / withdrawal prediction function is a function for calculating the highest past deposit / withdrawal amount. 14. The account information providing program according to claim 11, wherein the deposit / withdrawal prediction function is a function for calculating a minimum value of past deposit / withdrawal amounts. 15. A keyword relating to a transaction is set to identify the deposit / withdrawal type, and the estimated amount calculation means extracts a deposit / withdrawal history including the keyword in the abstract, and uses the deposit / withdrawal amount of the deposit / withdrawal history. 2. The estimated deposit / withdrawal amount is calculated according to claim 1.
The account information providing program according to any one of 1 to 14. 16. The user's account includes at least a first account and a second account, and the notification condition data storage means has a first lower limit balance as a limit balance of the first account. Is recorded, and a second lower limit balance is recorded as the limit balance of the second account. The account information providing program causes the management computer to set the predicted balance of the first account to the first lower limit. When a shortfall occurs with respect to the balance, the estimated amount obtained by subtracting the shortfall from the estimated balance of the second account is further functioned as a means for comparing the second lower limit balance, and the estimated amount is 11. When the balance is equal to or more than the second lower limit balance, the notification to the user includes a proposal to transfer the insufficient amount from the second account to the first account. Mouth according to any one of 15 Information providing program. 17. The user's account includes at least a first account and a second account, and the notification condition data storage means has a first upper limit balance as a limit balance of the first account. Is recorded, and a second upper limit balance is recorded as the limit balance of the second account. The account information providing program causes the management computer to set the predicted balance of the first account to the first upper limit. When a surplus amount is generated for the balance, the estimated amount obtained by adding the surplus amount to the estimated balance of the second account is further caused to function as a means for comparing the second upper limit balance, and the estimated amount is 11. When the balance is less than or equal to the second upper limit balance, the notification to the user includes a proposal to transfer the surplus amount from the first account to the second account. The account information described in any one of 15 Providing program. 18. The management computer is caused to function as a means for executing a transfer process for the transfer proposal when the user makes a transfer request for the transfer proposal of the notification. The account information providing program according to Item 16 or 17.