Program and server
The program and server system addresses the limitations of existing Internet banking systems by enabling seamless financial management and promoting purpose-specific deposits, enhancing user experience from short-term spending to long-term savings.
Patent Information
- Application Number
- JP2024153282
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-05
- Publication Date
- 2024-11-26
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing Internet banking systems, such as those described in Patent Document 1, do not provide seamless support for users' economic activities, including short-term income and expenditure management, long-term asset formation, and future consumption, with a focus on improving user experience and ease of use.
A program and server system that allows users to manage income and expenditure, transfer funds between accounts, and set purpose-specific deposits, integrating with a mobile terminal to provide seamless financial management and content provision, supporting both short-term and long-term financial goals.
Enables users to seamlessly manage their finances from daily spending to long-term savings and consumption, enhancing user convenience and promoting purpose-specific deposits through intuitive interfaces and incentives.
Smart Images

Figure 2024164302000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a program and a server. [Background technology]
[0002] With the recent development of the Internet, various commercial transactions can now be carried out over the Internet. Financial institutions such as banks are also increasingly using the Internet, and users can transfer money and check their account balances by logging into servers managed by financial institutions from their personal computers or smartphones at home. For example, Patent Document 1 discloses a system that provides such Internet banking services. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2002-334210 A Summary of the Invention [Problem to be solved by the invention]
[0004] Patent Document 1 discloses a technology that reflects the results of transactions made by a bank server to an account in household accounting software. This may indeed reduce the effort required for users to keep a household account book. However, today's users want a more consistent and easy-to-use service, so there is still room for improvement.
[0005] The present invention has been made in consideration of these problems, and its purpose is to provide technology that can seamlessly support users' economic activities, from short-term income and expenditure management and information provision to long-term asset formation and subsequent consumption. [Means for solving the problem]
[0006] One aspect of the present invention relates to a program. The program causes a computer that can communicate with a server via a network to perform the following functions: acquire a result of income / expense calculation based on deposit / withdrawal data of a first account of a user; inquire of a user on a display whether or not to transfer funds of an amount based on the acquired result between the first account and a second account of the user different from the first account; display information representing the acquired result and an amount designation reception area for receiving a designation of the amount of funds to be transferred between the first account and the second account on the display in response to the user's inquiry; and transmit a transfer instruction signal including the amount designated in relation to the amount designation reception area to the server when an instruction to transfer funds is received from the user in response to the user's inquiry. When the server receives the transfer instruction signal, it executes a process for transferring the designated amount of funds between the first account and the second account.
[0007] Another aspect of the present invention is also a program that causes a computer to obtain a result of a balance calculation based on deposit and withdrawal data of a first account of a user, and to inquire of a user on a display whether or not to transfer funds, in an amount based on the obtained result, between the first account and a second account of the user different from the first account.
[0008] Another aspect of the present invention is a program, which causes a computer capable of communicating over a network with a server that sorts out the balances of users' accounts to have a first display function for displaying on a display specific information of a group including at least one content specified by a user in association with an area for receiving instructions for creating a sorting unit related to the specific information, and a second display function for displaying on the display, when the area receives the instruction, a purpose input area in which a deposit purpose is input to specify the unit to be created.
[0009] Another aspect of the present invention is a server comprising: an acquisition unit that acquires a balance of a first account of a user and a second account of the user, the second account having a lower degree of freedom in terms of withdrawal than the first account, from another server that manages the second account; and a sorting unit that sorts the balance acquired by the acquisition unit.
[0010] In addition, any combination of the above components, or mutual substitution of the components or expressions of the present invention between an apparatus, a method, a system, a computer program, a recording medium storing a computer program, etc., are also valid aspects of the present invention. Effect of the Invention
[0011] According to the present invention, it is possible to seamlessly support a user's economic activities, from short-term income and expenditure management and information provision to long-term asset formation and subsequent consumption. [Brief description of the drawings]
[0012] [Figure 1] This is an explanatory diagram of two areas in customer consumption behavior. [Diagram 2] 1 is a schematic diagram showing an example of the configuration of an account management system according to an embodiment; [Diagram 3] 3 is a block diagram showing an example of the functions and configuration of the mobile terminal of FIG. 2. [Figure 4] 3 is a block diagram showing an example of the functions and configuration of the support server of FIG. 2. [Diagram 5] 5 is a data structure diagram showing an example of a user information storage unit in FIG. 4. [Figure 6] 5 is a data structure diagram showing an example of a clipboard holding unit in FIG. 4. [Figure 7] 5 is a data structure diagram showing an example of the purpose-specific deposit information holding unit of FIG. 4. [Figure 8] 5 is a data structure diagram showing an example of a coupon information storage unit in FIG. 4. [Figure 9] 3 is a flowchart showing an example of a series of processes in the mobile terminal of FIG. 2. [Figure 10]10(a) to 10(e) are diagrams showing representative screens that are displayed on the display at various steps in a series of processes. [Figure 11] 11(a) and (b) are representative screen diagrams showing screens displayed on the display during the income and expenditure management process. [Figure 12] 12(a) and 12(b) are diagrams showing typical screens that are displayed on the display during the content provision process. [Figure 13] 13(a) to 13(d) are diagrams showing typical screens that are displayed on the display during the content-deposit linking process. [Figure 14] 11 is a data structure diagram illustrating an example of a purpose correspondence relationship storage unit. FIG. [Figure 15] 15(a) to (e) are diagrams showing typical screens that are displayed on the display during the purpose-specific deposit management process. [Figure 16] Figure 16(a) is a representative screen image of the income / expense result screen relating to the modified example, Figure 16(b) shows the allocation setting area when the amount to be allocated to each purpose-specific deposit is shown in numerical value, and Figure 16(c) shows another display form of the amount to be allocated to each purpose-specific deposit. [Figure 17] 17(a) to (d) are diagrams showing representative screens that are displayed on the display during the goal achievement process. [Figure 18] FIG. 13 is a representative screen diagram of an initial registration screen. [Figure 19] 19(a) and (b) are representative screen images that are displayed on the display during the account registration process. [Figure 20] 20(a) to (c) are diagrams showing typical screens that are displayed on the display during the authentication process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, the same or equivalent components, parts, and processes shown in each drawing will be given the same reference numerals, and duplicated explanations will be omitted as appropriate.
[0014] The account management system according to the embodiment provides a service platform for account management using a highly functional mobile terminal such as a smartphone. FIG. 1 is an explanatory diagram of two areas in customer consumption behavior. The account management system provides a seamless service experience that supports lifestyles / life events by connecting the capture of low-amount, high-frequency consumption by debit, etc. (area surrounded by frame 2 in FIG. 1), i.e., daily consumption, with the stimulation of medium-to-high-amount, low-frequency consumption by savings, loans, etc. (area surrounded by frame 4 in FIG. 1), i.e., non-daily consumption, through a customer contact point called a smartphone. Regarding the capture of low-amount, high-frequency consumption, the account management system provides users with a visualization function for daily consumption through monthly income and expenditure management and a transfer function for surplus funds. Regarding the stimulation of medium-to-high-amount, low-frequency consumption, the account management system stimulates non-daily consumption (large consumption) by providing related information content, and supports the achievement of such consumption through purpose-specific deposits. In addition, the account management system recommends products and services related to the purpose of the purpose-specific deposits.
[0015] In particular, in this embodiment, the account management system provides the following functions: (1) Income and expenditure management based on account information (2) Encourage people to save surplus funds (3) Providing information content to encourage users to set up purpose-specific deposits (4) Management of purpose-specific deposits (5) Providing rewards / incentives for specific purpose deposits Therefore, rather than just managing short-term income and expenditures, the system can also help users build up long-term assets by encouraging them to save. In addition, by managing savings according to purpose, the system can more effectively support large-scale consumption that comes after savings.
[0016] Figure 2 is a schematic diagram showing an example of the configuration of account management system 10 according to an embodiment. Account management system 10 comprises a mobile terminal 12, such as a smartphone or tablet terminal, a support server 16, and an accounting server 18. Mobile terminal 12, support server 16, and accounting server 18 are all connected to a network 14, such as the Internet, and communicate via network 14. There is no limit to the number of each element of account management system 10.
[0017] Accounting server 18 is a server included in an accounting system of a financial institution such as a bank. The accounting system manages account balances, calculates interest, processes deposits and withdrawals, transfers, remittances, exchange transactions, and settles funds with other financial institutions. The accounting system may be configured using known technology. The financial institution (hereinafter simply referred to as the financial institution) that manages the accounting system and the support entity that manages support server 16 may be the same or different. In this embodiment, a case where they are different is described.
[0018] A user of mobile terminal 12 downloads (step S30) an account management application program (hereinafter referred to as the management app) 20 from a download site via network 14 to mobile terminal 12 and installs it. Alternatively, management app 20 may be pre-installed on mobile terminal 12. Management app 20 is provided by a support entity. When management app 20 is executed by mobile terminal 12, mobile terminal 12 communicates with support server 16 via network 14 and realizes various functions. Below, functions realized by mobile terminal 12 (a processing unit such as a CPU (Central Processing Unit)) executing management app 20 will be described as functions of mobile terminal 12. These functions are actually functions that management app 20 causes mobile terminal 12 to realize.
[0019] The accounting system server 18 holds information on the ordinary savings account 22 and the savings account 24 of the user of the mobile terminal 12. The ordinary savings account 22 and the savings account 24 are respectively an ordinary savings account and a savings account opened by the user at a financial institution and are managed by the financial institution. It can be said that the ordinary savings account is an account for managing income and expenditure, and the savings account is an account for deposits. The support server 16 acquires deposit and withdrawal data for the ordinary savings account 22 from the accounting system server 18 via the network 14 (step S32), performs income and expenditure calculations, and generates monthly income and expenditure data 26. The mobile terminal 12 acquires the income and expenditure data 26 from the support server 16 via the network 14 (S34). If the income and expenditure calculation result 28 shown in the income and expenditure data 26, i.e., the difference between income and expenditure, is positive, the mobile terminal 12 encourages the user to save an amount corresponding to the difference. When the mobile terminal 12 accepts a saving instruction from the user, it notifies the support server 16 of the designated savings amount. The support server 16 requests the accounting system server 18 to move the notified savings amount from the ordinary deposit account 22 to the savings deposit account 24 (step S36). The accounting system server 18 executes the transfer (or credit) from the ordinary deposit account 22 to the savings deposit account 24.
[0020] The support server 16 virtually sorts the balance of the savings account 24 of the user. Since the support server 16 sorts the balance by the purpose of the deposit, the unit of sorting is specified by the purpose of the deposit. The support server 16 has purpose-specific deposit data 29 that holds the deposit purpose and the amount allocated to the deposit purpose for each user in association with each other. The savings account 24 of the accounting server 18 and the purpose-specific deposit data 29 of the support server 16 are linked, and the total amount of the purpose-specific deposit data 29 including the amount not yet set for the purpose matches the balance of the savings account 24. The user can set the purpose-specific deposit data 29 via the mobile terminal 12 and the network 14. For example, the user who has viewed the information content provided by the support server 16 may set a new deposit purpose. In this case, the purpose-specific deposit data 29 is added with a unit of sorting corresponding to the new deposit purpose that has been set. In the example of FIG. 2, it is assumed that the purpose-specific deposit data 29 originally included a unit specified by the deposit purpose "travel" and a unit specified by the deposit purpose "marriage". When a user is influenced by information content about housing, such as renovations and sales of tower apartments, and sets a new deposit purpose of "Residence", the support server 16 adds the sorting unit 27 specified by the new deposit purpose of "Residence" to the purpose-specific deposit data 29. Since the sorting unit is specified by the deposit purpose, in this specification the sorting unit is referred to as purpose-specific deposit. In this embodiment, account numbers are not assigned to purpose-specific deposits.
[0021] In this way, account management system 10 supports the accumulation of small daily savings by linking income and expenditure management to the transfer of surplus funds, and also guides the accumulated savings into medium and large consumption by linking the provision of information content to the setting of purpose-specific deposits. Therefore, by using account management system 10, users can receive seamless support in almost all phases from savings to consumption.
[0022] Fig. 3 is a block diagram showing an example of the functions and configuration of the mobile terminal 12 in Fig. 2. The mobile terminal 12 may be any terminal capable of installing and executing the management application 20, and may be, for example, a known mobile terminal. The mobile terminal 12 includes a memory 121, a processor 122, a communication interface 123, a display 124, and an input interface 125. Each of these elements is connected to a bus 126 and communicates with each other via the bus 126.
[0023] The memory 121 is a storage area for storing data and programs. The data and programs may be permanently or temporarily stored in the memory 121. In particular, the memory 121 stores the management application 20. The processor 122 executes the programs stored in the memory 121, particularly the management application 20, to realize various functions in the mobile terminal 12. The communication interface 123 is an interface for transmitting and receiving data to and from the outside of the mobile terminal 12. For example, the communication interface 123 includes an interface for accessing a wireless communication network of a mobile phone, an interface for accessing a wireless LAN (Local Area Network), and the like. The communication interface 123 may also include an interface for a wired network such as a USB (Universal Serial Bus). The display 124 is a device for displaying various information, and is, for example, a liquid crystal display or an organic EL (Electroluminescence) display. The input interface 125 is a device for receiving input from a user. The input interface 125 includes, for example, a touch panel provided on the display 124, various input keys, and the like.
[0024] Fig. 4 is a block diagram showing an example of the functions and configuration of the support server 16 of Fig. 2. The support server 16 includes a user authentication unit 102, an income / expense processing unit 104, a content processing unit 106, a purpose-specific deposit creation reception unit 108, a purpose-specific deposit information transmission unit 110, a coupon information transmission unit 112, a coupon usage registration unit 114, a user information storage unit 116, a clipboard storage unit 118, a purpose-specific deposit information storage unit 130, and a coupon information storage unit 132.
[0025] The income / expense processing unit 104 processes income / expenses based on deposit / withdrawal data of the user's ordinary savings account 22. The income / expense processing unit 104 particularly relates to a function that links income / expense management to the transfer of surplus funds to the savings deposit account 24. The income / expense processing unit 104 has an account information acquisition unit 134, an income / expense calculation unit 136, an income / expense information transmission unit 138, and an accounting system linkage unit 140.
[0026] The content processing unit 106 performs processing related to information content. The content processing unit 106 is particularly related to a function that links the provision of information content to the setting of purpose-specific deposits. The content processing unit 106 has a content acquisition unit 142, a content transmission unit 144, a grouping unit 146, and a clipboard transmission unit 148.
[0027] Fig. 5 is a data structure diagram showing an example of the user information storage unit 116 in Fig. 4. The user information storage unit 116 stores a user ID for identifying a user, a password, a regular savings account number opened by the user at a financial institution, a savings account number opened by the user at a financial institution, and a closing date which is a reference timing for calculating income and expenditure set in advance by the user via the mobile terminal 12, in association with each other. The user ID may be the user's email address. The closing date may be selected from the end or beginning of the month, the 25th of each month, etc., or may be freely set by the user.
[0028] FIG. 6 is a data structure diagram showing an example of the clipboard storage unit 118 of FIG. 4. The clipboard storage unit 118 stores a user ID, a group ID that identifies a group of information content, and information content belonging to the group in association with each other. The information content includes a collection of information related to products and services such as travel, cars, marriage, child-rearing, housing, experiences, encounters, and lifestyles. The information content may be digital data such as articles, tweets, and photos. Tags indicating themes, genres, attributes, and characteristics are attached to the information content. Groups are set based on these tags. The clipboard storage unit 118 may store the information content itself, or may store links to the information content.
[0029] FIG. 7 is a data structure diagram showing an example of the purpose-specific deposit information holding unit 130 of FIG. 4. The data held in the purpose-specific deposit information holding unit 130 corresponds to the purpose-specific deposit data 29. The purpose-specific deposit information holding unit 130 holds, in association with each other, a user ID, the balance of the user's savings account identified by the user ID, a deposit purpose including unset, a purpose-specific balance which is the balance of the purpose-specific deposit, a target amount, a monthly savings amount, and a savings execution date. Each entry in the purpose-specific deposit information holding unit 130 corresponds to a purpose-specific deposit. For each user ID, the total balance of the purpose-specific deposits matches the balance of the savings account.
[0030] Fig. 8 is a data structure diagram showing an example of the coupon information storage unit 132 of Fig. 4. The coupon information storage unit 132 stores a deposit purpose, a base amount, the contents of the coupon, and a use-declaring user ID that identifies a user who has declared the use of the coupon, in association with each other. The coupon information storage unit 132 is configured to allow the setting of multiple base amounts for each deposit purpose. A coupon is a form of advertising provided by an entity such as a company that conducts a business related to the corresponding deposit purpose.
[0031] The operation of the account management system 10 configured as above will now be described. Fig. 9 is a flowchart showing an example of a series of processes in the mobile terminal 12 of Fig. 2. Figs. 10(a)-(e) are representative screen diagrams of screens displayed on the display 124 in various steps of a series of processes. Here, it is assumed that the user has already registered an account in the management application 20 and has also registered a regular savings account. That is, a case will be described where the management application 20 is started after initial use registration and account registration have been completed. The processes relating to the initial registration and account registration will be described later.
[0032] When the user taps the icon of the management application 20 displayed on the display 124 of the mobile terminal 12, the mobile terminal 12 starts the management application 20 (S202). The mobile terminal 12 displays an application start-up screen 640 (FIG. 10(a)) on the display 124. The application start-up screen 640 has an initial registration button 642 and a normal start-up button 644. Since the user has completed initial registration in the management application 20, the user taps the normal start-up button 644. When detecting the tap on the normal start-up button 644, the mobile terminal 12 displays a login screen 240 (FIG. 10(b)) for authenticating the user on the display 124 (S204).
[0033] The login screen 240 has an authentication information input area 250 for accepting input of authentication information including a user ID and a password, and a login button 252. The user inputs his / her email address and password in the authentication information input area 250, and taps the login button 252. When the login button 252 is tapped, the mobile terminal 12 transmits the authentication information input in the authentication information input area 250 to the support server 16 via the network 14.
[0034] 9, the user ID / password is not stored in the mobile terminal 12, and authentication is requested from the user each time the user logs in. The timing for requesting input of authentication information is set to the timing for restarting a module in the management application 20 (for example, at intervals of about 24 hours), and input of the user ID / password is requested again at the set timing (that is, the screen transitions to the login screen 240 in response to tapping the normal start button 644). In addition, when the user explicitly stops and starts the management application 20 (for example, after turning off the power of the mobile terminal 12, the management application 20 is started), input of the user ID / password is requested again. However, input of the user ID / password may not be requested between restarts of the module in the management application 20 and the next restart.
[0035] The user authentication unit 102 of the support server 16 performs user authentication based on the received authentication information. If the pair of the user ID and password included in the received authentication information is registered in the user information storage unit 116, the user authentication unit 102 determines that the authentication is successful, and if not, that the authentication is unsuccessful. The user authentication unit 102 transmits the result of the user authentication to the mobile terminal 12 via the network 14.
[0036] When the user authentication unit 102 determines that the authentication is successful, the account information acquisition unit 134 acquires, from the accounting system server 18 via the network 14, deposit and withdrawal data for a predetermined period from the deposit and withdrawal data of the ordinary savings account of the authenticated user. The predetermined period may be one month, three months, six months, or one year. The account information acquisition unit 134 refers to the user information storage unit 116 to identify the number of the ordinary savings account corresponding to the user ID of the authenticated user. The account information acquisition unit 134 generates a deposit and withdrawal data request signal including the identified ordinary savings account number and information specifying the predetermined period, and transmits it to the accounting system server 18 via the network 14. The accounting system server 18 extracts the deposit and withdrawal data for the specified predetermined period from the ordinary savings account specified by the number included in the received deposit and withdrawal data request signal, and transmits it to the support server 16 via the network 14. The account information acquisition unit 134 receives the deposit and withdrawal data for the predetermined period.
[0037] The income / expense calculation unit 136 executes monthly income / expense calculation for the deposit / withdrawal data for a predetermined period acquired by the account information acquisition unit 134. The income / expense calculation unit 136 extracts the closing date corresponding to the user ID of the authenticated user from the user information storage unit 116. For convenience of explanation, the period from today to the day after the most recent closing date will be referred to as the current month, and the period from the most recent closing date to the next closing date will be referred to as the previous month. The income / expense calculation unit 136 extracts deposit / withdrawal data that occurred during the current month and deposit / withdrawal data that occurred during the previous month from the deposit / withdrawal data for a predetermined period as the current month's deposit / withdrawal data and the previous month's deposit / withdrawal data, respectively. For example, it is assumed that the current day is September 16th, the closing date is the 25th of each month, and the deposit / withdrawal data for three months (July 16th to September 16th) has been acquired by the account information acquisition unit 134. The income and expenditure calculation unit 136 acquires the deposit and withdrawal data that occurred during the calculation period from August 26 to September 16 (this month) as this month's deposit and withdrawal data. The income and expenditure calculation unit 136 acquires the deposit and withdrawal data that occurred during the calculation period from July 26 to August 25 as last month's deposit and withdrawal data.
[0038] The income and expenditure calculation unit 136 separates the current month's deposit and withdrawal data into income and expenditure, and further classifies each of the income and expenditure categories into income and expenditure details data for this month. The income and expenditure calculation unit 136 adds up this month's income to obtain this month's total income, and adds up this month's expenditure to obtain this month's total expenditure. The income and expenditure calculation unit 136 obtains the difference between this month's total income and this month's total expenditure as this month's income and expenditure result. The current month's deposit and withdrawal details data, this month's total income, this month's total expenditure, and this month's income and expenditure result constitute this month's income and expenditure data 26. The income and expenditure calculation unit 136 performs similar calculations on last month's deposit and withdrawal data to generate last month's income and expenditure data.
[0039] The income / expense calculation unit 136 may perform similar calculations on the deposit / withdrawal data from the month before last. The income / expense calculation unit 136 may perform calculations in units of other calculation periods, such as weekly or quarterly, instead of monthly. The units may correspond to the length of the predetermined period in the account information acquisition unit 134.
[0040] The balance information transmitting unit 138 transmits the balance data for the previous month and this month generated by the balance calculation unit 136 to the mobile terminal 12 via the network 14. The mobile terminal 12 receives the balance data following the result of user authentication.
[0041] If the received result of the user authentication is a failure (N in S206), the mobile terminal 12 returns the process to step S204. If the received result of the user authentication is a success (Y in S206), the mobile terminal 12 displays the home screen 242 (FIG. 10(c)) on the display 124 (S208).
[0042] The home screen 242 has a menu button 241, an income / expense result display area 254, a points display area 256, a special deals area 258, a My Coupon area 260, a content guidance area 262, a home button 264, a clip button 266, a savings button 268, and a wallet button 270. The income / expense result display area 254 displays the result of the income / expense calculation included in the income / expense data for this month received by the mobile terminal 12. In particular, the income / expense result display area 254 displays the number of the ordinary savings account of the authenticated user, the balance of the account, the total income for this month, the total expenditure for this month, and the income / expense result for this month. The points display area 256 displays the points currently given to the user. These points may be given and managed by the support entity, or may be given and managed by a financial institution. When the mobile terminal 12 detects a tap on the special deals area 258, it displays a special deals display screen (not shown) on the display 124 that displays limited-time coupons and the like. The user's tap on the discount information area 258 is one mode of the user's instruction to display discount information. When the mobile terminal 12 detects a tap on the home button 264, it displays the home screen 242 on the display 124. The my coupon area 260, the content guidance area 262, the clip button 266, the savings button 268, and the wallet button 270 will be described later.
[0043] The mobile terminal 12 determines whether or not closing processing is necessary in accordance with the display of the home screen 242 (S210). The mobile terminal 12 determines that closing processing is necessary when the management app 20 is launched for the first time after the closing date has arrived, and determines that closing processing is not necessary if not. In other words, from the second launch after the closing date has arrived, it is determined that closing processing is not necessary until the next closing date arrives. This is managed by a status flag or the like stored in the memory 121 of the mobile terminal 12. If it is determined that closing processing is not necessary (N in S210), the mobile terminal 12 ends the processing.
[0044] If it is determined that closing processing is necessary (Y in S210), the mobile terminal 12 displays the income and expenditure result screen 244 (FIG. 10(d)) on the display 124 (S212). The income and expenditure result screen 244 may be displayed on the display 124 by, for example, a push notification even when the management app 20 is not running. The income and expenditure result screen 244 displays the income and expenditure of the previous month based on the income and expenditure data of the previous month received by the mobile terminal 12. In this embodiment, a case will be described in which the total income of the previous month exceeds the total expenditure of the previous month, and therefore the income and expenditure result of the previous month is positive.
[0045] The balance result screen 244 allows the user to check the balance of the previous month, and also guides the user to transfer funds of an amount based on the result to the savings account. By displaying the balance result screen 244, the mobile terminal 12 inquires the user on the display 124 whether or not to transfer funds of an amount based on the balance result of the previous month, which is included in the balance data of the previous month, between the ordinary savings account and the savings account. The balance result screen 244 has a difference display area 272, a setting slider 274, a deposit button 276, a not deposit button 278, and a later button 277. The difference display area 272 displays the balance result of the previous month, which is included in the balance data of the previous month. The setting slider 274 accepts the designation of the amount of funds to be moved, i.e., transferred, from the ordinary savings account to the savings account (hereinafter referred to as the transfer amount). By operating the setting slider 274, the user can visually designate the transfer amount within the range of 0 yen to the maximum amount. The maximum amount is set based on the balance result of the previous month, and may be the balance result of the previous month itself, or may be a rounded amount smaller than the balance result of the previous month. Therefore, the display of such a setting slider 274 corresponds to asking the user how much of the funds to transfer within the range of the balance result of the previous month.
[0046] The Deposit button 276 and the Do Not Deposit button 278 are buttons for inquiring of the user as to whether or not to execute the transfer. The Later button 277 is a button for postponing the decision as to whether or not to deposit. When the Later button 277 is tapped, the mobile terminal 12 displays the home screen 242 on the display 124. The mobile terminal 12 prompts the user to make a decision by notifying the user as to whether or not to transfer the surplus funds again after a certain period of time has passed. In this re-notification, a screen similar to the income / expense result screen 244 is displayed.
[0047] When the Deposit button 276 is tapped, the mobile terminal 12 accepts an instruction from the user to execute the transfer. When the Do Not Deposit button 278 is tapped, the mobile terminal 12 accepts an instruction not to execute. More specifically, when the mobile terminal 12 detects a tap on the Do Not Deposit button 278 (N of S214), it ends the process. When the mobile terminal 12 detects a tap on the Deposit button 276 (Y of S214), it transmits a transfer instruction signal including the transfer amount set on the setting slider 274 of the balance result screen 244 to the support server 16 via the network 14.
[0048] The accounting system linkage unit 140 requests the accounting system server 18 to transfer the transfer amount included in the received transfer instruction signal from the user's ordinary savings account to the savings account. The accounting system linkage unit 140 transmits a response signal in response to the receipt of the transfer instruction signal to the mobile terminal 12 via the network 14. The accounting system server 18 transfers the transfer amount from the user's ordinary savings account to the savings account in response to the request. The accounting system linkage unit 140 may generate the response signal after receiving a notification of transfer completion from the accounting system server 18. When the mobile terminal 12 receives the response signal, it displays a deposit completion screen 248 (FIG. 10(e)) on the display 124 (S220). The mobile terminal 12 then ends the process.
[0049] 11(a) and (b) are representative screen diagrams showing screens displayed on the display 124 in the income and expenditure management process. The wallet button 270 on the home screen 242 functions as a guide to the income and expenditure management function. When the mobile terminal 12 detects a tap on the wallet button 270 on the home screen 242, it displays an income and expenditure management screen 292 (FIG. 11(a)) on the display 124. The income and expenditure management screen 292 has a calculation period display area 402, an income and expenditure result display area 404, an income and expenditure status display area 406, and an income and expenditure item display area 408.
[0050] The calculation period display area 402 displays calculation periods for which income and expenditure can be displayed. The calculation period display area 402 highlights the calculation period to be displayed, for example, by highlighting it in inverted color ("06 / 01 to 06 / 30" in FIG. 11(a)). When the mobile terminal 12 detects a tap on a non-highlighted calculation period in the calculation period display area 402 ("05 / 01 to 05 / 31" in FIG. 11(a)), it switches the calculation period to be displayed to the tapped calculation period.
[0051] The income and expenditure result display area 404 displays the number of days remaining until the next closing date and the current month's income and expenditure result contained in the current month's income and expenditure data received by the mobile terminal 12. The income and expenditure status display area 406 visually displays the current month's income and expenditure status. The income and expenditure status display area 406 displays the current month's total income and total expenditure as numerical values and color-coded bar graphs. The income and expenditure item display area 408 displays the income and expenditure items of the current month's deposit and withdrawal detail data in association with the total deposits or withdrawals belonging to those income and expenditure items.
[0052] When the mobile terminal 12 detects a tap on one of the income and expenditure items displayed in the income and expenditure item display area 408, it causes a deposit and withdrawal details screen 410 (FIG. 11(b)) corresponding to the tapped income and expenditure item to be displayed on the display 124. In the example of FIG. 11(b), the income and expenditure item "debit payment" is tapped, and in response, a deposit and withdrawal details screen showing the details of the debit payment is displayed.
[0053] 12(a) and (b) are representative screen diagrams of screens displayed on the display 124 during the content provision process. Prior to the content provision process, the content acquisition unit 142 of the support server 16 acquires information content from the database of a partner company, the Internet, etc. The following describes the case where the information content is a digitized article.
[0054] The content guide area 262 of the home screen 242 functions as a lead to a content providing function. When the mobile terminal 12 detects a tap on the content guide area 262 on the home screen 242, the mobile terminal 12 transmits a content request to the support server 16 via the network 14. In response to the received request, the content transmission unit 144 transmits the article acquired by the content acquisition unit 142 to the mobile terminal 12 via the network 14. The content transmission unit 144 may customize the article to be delivered depending on the requesting user.
[0055] The mobile terminal 12 displays a content top screen 286 (FIG. 12(a)) displaying the received articles on the display 124. The content top screen 286 displays the headlines of multiple different articles received by the mobile terminal 12. In the example of FIG. 12(a), a first headline 412, a second headline 414, and a third headline 416 are displayed on the content top screen 286.
[0056] When the mobile terminal 12 detects a tap on one of the headlines displayed on the content top screen 286, it displays a content details screen 418 ( FIG. 12(b) ) on the display 124, the content details screen 418 displaying details of the article corresponding to the tapped headline. The content details screen 418 has article content 420, a clip button 422, and a tour link 424. When the mobile terminal 12 detects a tap on the tour link 424, it displays a website of a company that provides a tour related to the article content 420 on the display 124. When the mobile terminal 12 detects a tap on the clip button 422, it generates a clip request signal including an article ID that identifies the article displayed on the content details screen 418, and transmits the signal to the support server 16 via the network 14.
[0057] The grouping unit 146 of the support server 16 identifies the tag of the article identified by the article ID included in the received clip request signal. The grouping unit 146 determines the group to which the article should belong based on the identified tag. The grouping unit 146 registers in the clipboard holding unit 118 the user ID of the user who transmitted the clip request signal, the group ID of the determined group, and the article identified by the article ID included in the clip request signal in association with each other.
[0058] 13(a)-(d) are representative screen diagrams of screens displayed on the display 124 in the content-deposit linkage process. The clip button 266 on the home screen 242 functions as a guide to the content-deposit linkage function. When the mobile terminal 12 detects a tap on the clip button 266 on the home screen 242, it requests clipboard information from the support server 16 via the network 14. In response to the request, the clipboard transmission unit 148 of the support server 16 extracts a group ID and an article corresponding to the user ID of the user authenticated by the user authentication unit 102 from the clipboard holding unit 118. The clipboard transmission unit 148 transmits the extracted group ID and article to the mobile terminal 12 via the network 14.
[0059] The mobile terminal 12 displays on the display 124 a clipboard top screen 288 (FIG. 13(a)) that displays the received article. The clipboard top screen 288 has a group information display area that is a display area set for each group. The group information display area corresponds to the group ID received by the mobile terminal 12, and the information displayed there is an article belonging to the group identified by the group ID. In particular, in the example of FIG. 13(a), the clipboard top screen 288 has a first group information display area 426 and a second group information display area 428. The first group information display area 426 has a group name display area 430 in which the name of the group, which is information that identifies the group, is displayed, a budget display area 432, an article image display area 434 in which an image representing an article belonging to the group is displayed, and a fulfill button 436. The name of the group may be a group ID. The second group information display area 428 has a configuration similar to that of the first group information display area 426.
[0060] The budget display area 432 displays the budget for products and services related to the group. This budget may be extracted from a table (not shown) that holds group IDs and estimated costs in association with each other. This table may be provided in the support server 16 or in the mobile terminal 12. The estimated costs in this table may be set by the support entity, or may be set by the support server 16 by performing statistical processing.
[0061] The Fulfill button 436 is an area for accepting an instruction to create a purpose-specific deposit related to a group. When the mobile terminal 12 detects a tap on the Fulfill button 436, the mobile terminal 12 displays a deposit creation inquiry screen 438 (FIG. 13(b)) on the display 124 for inquiring of the user whether or not to create a purpose-specific deposit. The deposit creation inquiry screen 438 has a Save button 440 and a tour link 442 similar to the tour link 424. When the mobile terminal 12 detects a tap on the Save button 440, the mobile terminal 12 displays a purpose-specific deposit creation screen 446 (FIG. 13(c)) on the display 124 for setting each parameter of the purpose-specific deposit. The mobile terminal 12 accepts the parameters of the purpose-specific deposit on the purpose-specific deposit creation screen 446. The purpose-specific deposit creation screen 446 has a deposit purpose input area 448, a target amount input area 450, a monthly savings amount input area 452, a savings execution date input area 454, and a Create button 456.
[0062] The deposit purpose input area 448 accepts input of the deposit purpose. The mobile terminal 12 inputs the deposit purpose corresponding to the group corresponding to the tapped Fulfill button 436 into the deposit purpose input area 448 in advance.
[0063] FIG. 14 is a data structure diagram showing an example of the purpose correspondence holding unit 294. The purpose correspondence holding unit 294 holds the correspondence between the deposit purpose and the group. The purpose correspondence holding unit 294 may be held in the memory 121 of the mobile terminal 12, or may be held in the support server 16. The purpose correspondence holding unit 294 holds the deposit purpose and the group ID in association with each other. In the example of FIG. 14, the "Train travel" group (group ID "traintravel"), the "Cruise travel" group (group ID "cruise"), and the "Overseas travel" group (group ID "overseas") all correspond to the deposit purpose "travel". The correspondence may be set by the support entity, or may be automatically set by the support server 16 or the like.
[0064] Returning to Fig. 13(c), the mobile terminal 12 refers to the purpose correspondence storage unit 294 and identifies the deposit purpose corresponding to the group. The mobile terminal 12 pre-enters the identified deposit purpose in the deposit purpose input area 448. For example, when the fulfill button 436 for the "Travel" group is tapped, the mobile terminal 12 displays the purpose-specific deposit creation screen 446 on the display 124 with "Travel" entered in the deposit purpose input area 448.
[0065] The goal amount input area 450 accepts input of a goal amount for a savings by purpose. The mobile terminal 12 inputs in advance, into the goal amount input area 450, a goal amount according to the budget displayed in the budget display area 432 corresponding to the tapped Fulfill button 436. For example, when the Fulfill button 436 for the "Train travel" group is tapped, the mobile terminal 12 displays the goal-specific savings creation screen 446 on the display 124 with the upper limit of the budget for "Train travel" of 300,000 yen input into the goal amount input area 450.
[0066] When the mobile terminal 12 detects a tap on the deposit purpose input area 448, it displays a purpose selection screen 444 (FIG. 13(d)) on the display 124 for accepting a change to the deposit purpose. A list of settable deposit purposes is displayed on the purpose selection screen 444. When any of the deposit purposes displayed on the purpose selection screen 444 is tapped, the mobile terminal 12 displays a purpose-specific deposit creation screen 446 on the display 124 with the tapped deposit purpose entered in the deposit purpose input area 448. This makes it possible to change the deposit purpose entered in the deposit purpose input area 448. The target amount entered in the target amount input area 450 can be changed in the same way. The monthly savings amount input area 452 and the savings start date input area 454 accept input of the monthly savings amount and the savings start date, respectively.
[0067] When the mobile terminal 12 detects a tap on the create button 456, it generates a purpose-specific deposit creation signal including the information entered in the deposit purpose input area 448, the target amount input area 450, the monthly savings amount input area 452, and the savings start date input area 454, and transmits it to the support server 16 via the network 14. The purpose-specific deposit creation receiving unit 108 of the support server 16 associates the user ID of the user authenticated by the user authentication unit 102 with each piece of information included in the received purpose-specific deposit creation signal, and registers them in the purpose-specific deposit information holding unit 130. The balance of the purpose-specific deposit at the time of registration may be set to 0 yen.
[0068] 15(a)-(e) are representative screen diagrams of screens displayed on the display 124 in the purpose-specific deposit management process. The savings button 268 on the home screen 242 functions as a guide to the purpose-specific deposit management function. When the mobile terminal 12 detects a tap on the savings button 268 on the home screen 242, it transmits a request for purpose-specific deposit information to the support server 16 via the network 14. In response to the received request, the purpose-specific deposit information transmission unit 110 of the support server 16 extracts purpose-specific deposit information corresponding to the user ID of the user authenticated by the user authentication unit 102 from the purpose-specific deposit information holding unit 130. The purpose-specific deposit information includes the balance of the savings deposit account, the deposit purpose, the purpose-specific balance, the target amount, the monthly savings amount, and the savings execution date. The purpose-specific deposit information transmission unit 110 transmits the extracted purpose-specific deposit information to the mobile terminal 12 via the network 14.
[0069] The mobile terminal 12 displays on the display 124 the purpose-specific deposit top screen 290 (FIG. 15(a)), which displays the received information on purpose-specific deposits. The purpose-specific deposit top screen 290 has a savings trend display area 458, an unspecified balance display area 460, and a purpose list display area 462. The savings trend display area 458 displays the user's savings deposit account number, the account balance, and the balance trend. The unspecified balance display area 460 displays the balance of purpose-specific deposits for which the deposit purpose has not been specified. In particular, this balance is obtained by subtracting the total balance of purpose-specific deposits other than the unspecified one from the savings deposit account balance. The purpose list display area 462 displays the purpose-specific balance, the target amount, and a balance setting slider in association with each deposit purpose. The user can freely move funds between purpose-specific deposits by operating the balance setting slider. In particular, when the slider is operated in a direction to decrease the balance, there is no restriction, and the balance in the unset balance display area 460 increases by the amount of the decrease. Conversely, when the slider is operated in a direction to increase the balance, operation is restricted to within the range of the balance in the unset balance display area 460.
[0070] When the mobile terminal 12 detects a tap on one of the multiple purpose-specific deposits displayed in the purpose list display area 462, it causes the display 124 to display a purpose-specific deposit details screen 464 (FIG. 15(b)), which displays details of the tapped purpose-specific deposit. The purpose-specific deposit details screen 464 has an achievement level display area 466, a balance etc. display area 468, a purpose type display area 470, a target amount display area 472, a memo display area 474, and a coupon confirmation button 476. The achievement level display area 466 visually displays the ratio between the purpose-specific balance and the target amount as the achievement level. The balance etc. display area 468 displays the purpose-specific balance and the target amount in association with each other. The purpose type display area 470 displays the purpose of the deposit. The target amount display area 472 displays the target amount. The memo display area 474 displays the user's memo related to the purpose-specific deposit.
[0071] When the mobile terminal 12 detects a tap on the coupon confirmation button 476, it transmits a purpose-specific coupon request including the deposit purpose and purpose-specific balance corresponding to the tapped coupon confirmation button 476 to the support server 16 via the network 14. The coupon information transmission unit 112 of the support server 16 selects information on coupons corresponding to the deposit purpose and the purpose-specific balance included in the received purpose-specific coupon request from the coupon information storage unit 132. The coupon information transmission unit 112 extracts information on coupons corresponding to the deposit purpose whose corresponding base amount is smaller than the purpose-specific balance from the coupon information storage unit 132. To explain using the example of FIG. 8, for the deposit purpose "travel" and the purpose-specific balance "237,000 yen", the coupon information transmission unit 112 extracts five coupons, "5% off all products of C tour", "10% off package tour of A-B travel", "10% off all products of A-B tour", "10% off all products of ABC tour", and "10% off all products of A-B travel tour". For the deposit purpose "travel" and the purpose-specific balance "150,000 yen", the coupon information transmission unit 112 extracts only one coupon, "5% off all products on Tour C". The coupon information transmission unit 112 transmits the extracted coupon information to the mobile terminal 12 via the network 14.
[0072] The mobile terminal 12 displays on the display 124 a coupon-by-purpose screen 478 ( FIG. 15(c) ) that displays the received coupons. The received coupons are displayed in a list format on the coupon-by-purpose screen 478. When the mobile terminal 12 detects a tap on one of the coupons displayed on the coupon-by-purpose screen 478, it displays on the display 124 a coupon use confirmation screen 480 for inquiring whether or not to use the tapped coupon. On the coupon use confirmation screen 480, a use button 482 and a do not use button 484 are displayed. When the mobile terminal 12 detects a tap on the do not use button 484, it displays on the display 124 the coupon-by-purpose screen 478 again.
[0073] When the mobile terminal 12 detects a tap on the Use button 482, it transmits a coupon registration request including coupon identification information that identifies the tapped coupon to the support server 16 via the network 14. The coupon use registration unit 114 of the support server 16 registers the user ID of the authenticated user (i.e., the user who transmitted the coupon) as a use declaration user ID in the coupon information storage unit 132, in association with the coupon identified by the coupon identification information included in the received coupon registration request. The coupon use registration unit 114 transmits a response signal to the received coupon registration request to the mobile terminal 12 via the network 14. When the mobile terminal 12 receives the response signal, it causes a coupon acceptance completion screen 486 ( FIG. 15(e) ) to be displayed on the display 124.
[0074] After the coupon usage is accepted, the coupon benefit is automatically provided when the user uses a specific payment method (debit / credit) at the applicable store. This is realized by matching the usage declaration user ID stored in the coupon information storage unit 132 with the user's payment history.
[0075] When the mobile terminal 12 detects a tap on the My Coupons area 260 of the home screen 242, it displays the My Coupons screen on the display 124. The My Coupons screen has a similar configuration to the purpose-specific coupon screen 478.
[0076] In the above-mentioned embodiment, examples of the storage unit are a hard disk and a semiconductor memory. Furthermore, based on the description in this specification, it will be understood by those skilled in the art who have read this specification that each unit can be realized by a CPU (not shown), an installed application program module, a system program module, a semiconductor memory that temporarily stores the contents of data read from a hard disk, or the like.
[0077] According to the account management system 10 of this embodiment, the balance result screen 244 provides a deposit button 276 as a guide to a transfer. Therefore, after notifying the user that the balance result of the previous month was in the black, the user can be prompted to make a transfer on the spot. Moreover, such a transfer can be realized with a single tap. As a result, the user can make the transfer smoothly without forgetting.
[0078] Furthermore, in the account management system 10 according to this embodiment, the user can set the transfer amount by operating the setting slider 274 on the balance result screen 244. Therefore, when the user does not wish to transfer the entire amount of the previous month's balance result, it is possible to improve the user's convenience in setting the transfer amount. In particular, since the user can check the previous month's balance result, set the transfer amount, and give instructions for the transfer on a single screen, a user interface with less operational stress is provided.
[0079] Furthermore, in the account management system 10 according to this embodiment, the information displayed in the group information display area of the clipboard top screen 288 corresponds to groups of articles that the user has collected up to that point. By grouping the articles collected by the user, the user's latent preferences, hobbies, needs, and wishes can be made apparent. In other words, the groups can correspond to preferences that the user probably has. For example, a group called "Train Travel" is generated in the clipboard of a user who has collected many articles about trains and train window views, and it is presumed that the user wants to take a train trip.
[0080] The group information display area provides a "Fulfillment" button 436 that guides users to set up purpose-specific savings in accordance with the group information. This allows users who have become aware of their own potential preferences and desires through the group information display area to be prompted to set up purpose-specific savings to fulfill those preferences on the spot. As a result, once a user becomes aware of their own preferences and desires, they can seamlessly start purpose-specific savings to fulfill them. Furthermore, setting up purpose-specific savings stimulates consumption that corresponds to the purpose of the savings.
[0081] Furthermore, in the account management system 10 according to this embodiment, the budget required to realize preferences and wishes is displayed in the budget display area 432 of the group information display area. This provides the user with an indicator for determining whether or not to set up purpose-specific deposits without requiring any further user operation. As a result, user convenience is improved.
[0082] Furthermore, in the account management system 10 according to this embodiment, values specified by the group corresponding to the tapped Fulfill button 436 are pre-entered in the deposit purpose input area 448 and the target amount input area 450 of the purpose-specific deposit creation screen 446. This eliminates the need for user input operations, improving user convenience.
[0083] Furthermore, in the account management system 10 according to the present embodiment, coupons corresponding to the deposit purpose are displayed on the purpose-specific coupon screen 478. This makes it possible to provide benefits to the user and promote the conversion from purpose-specific deposits to consumption.
[0084] In addition, in the account management system 10 according to this embodiment, income and expenditure calculations are performed based on the deposit and withdrawal data of the ordinary savings account. The income and expenditure result calculated in this way corresponds to the actual increase in the balance of the ordinary savings account. Therefore, it is possible to reduce the probability of a situation occurring in which the balance of the ordinary savings account from which the transfer is made is less than the transfer amount when a transfer instruction is received from the user. Also, compared to the case where the balance is always saved if the income and expenditure result is positive, that is, without inquiring of the user, in this embodiment, an option not to transfer (no deposit button 278) is provided, so that it is possible to create purpose-specific deposits in a form that is in line with the user's situation and wishes.
[0085] The above describes the configuration and operation of the account management system 10 according to the embodiment. This embodiment is merely an example, and it will be understood by those skilled in the art that various modifications are possible in the combination of each component and each process, and that such modifications are also within the scope of the present invention.
[0086] In the embodiment, the case where management application 20 is installed in mobile terminal 12 has been described, but the present invention is not limited to this, and an application having the same functions as management application 20 may be installed in a stationary terminal such as a desktop PC. Also, in the embodiment, the case where management application 20 is an installable application installed in mobile terminal 12 has been described, but the present invention is not limited to this, and for example, management application 20 may be realized as a Web application used in a mobile terminal or a stationary terminal via the Internet.
[0087] In the embodiment, a case where funds are transferred between a normal deposit account and a savings deposit account, and the balance of the savings deposit account is divided for deposit purposes has been described, but this is not limited thereto. For example, a current deposit account may be used instead of a normal deposit account, and a fixed term deposit account may be used instead of a savings deposit account. More generally, an accounting system server manages a first account of a user and a second account of the user, which has a lower degree of freedom in withdrawal than the first account. The support server acquires the balance of the second account from the accounting system server, and virtually divides the acquired balance for deposit purposes. This reduces the likelihood that the balance of the second account will decrease for reasons other than the use of purpose-specific deposits. If a purpose-specific deposit is set in the first account, the balance of the first account will easily decrease due to debit settlement, withdrawal, withdrawal, etc., regardless of the purpose-specific deposit, so the total amount of the purpose-specific deposit and the actual balance will frequently not match. Each time this happens, it is necessary to reset the purpose-specific balance, which is troublesome. Therefore, by setting up purpose-specific deposits in the second account, such hassle can be reduced and user convenience can be improved.
[0088] In addition, if the financial institution that manages the accounting server and the support entity are allowed to be different, for example, an information provider that is not so closely related to finance can also be the support entity. Therefore, it is possible to provide users with a wider range of flexible services that are not limited to the financial framework.
[0089] In the present embodiment, the case where the total income of the previous month exceeds the total expenditure of the previous month has been described, but the present invention is not limited to this. For example, in the opposite case, that is, in the case where the total expenditure of the previous month exceeds the total income of the previous month, the mobile terminal 12 may inquire whether or not at least a part of the income and expenditure result of the previous month, which is the difference between the total expenditure of the previous month and the total income of the previous month, should be transferred from the savings account to the regular savings account. That is, the operation of compensating for the deficit from the savings account may be realized with one tap on the income and expenditure result screen. In this case, the setting slider accepts the setting of the compensation amount. Also, the income and expenditure result screen may be displayed on the display 124 in a different manner depending on whether the income and expenditure result of the previous month is positive or negative. For example, in the case where the income and expenditure result of the previous month is positive, that is, the total income of the previous month exceeds the total expenditure of the previous month, the background of the income and expenditure result screen may be blue, and in the case where the income and expenditure result of the previous month is negative, that is, the total expenditure of the previous month exceeds the total income of the previous month, the background of the income and expenditure result screen may be red. This improves the visibility of the income and expenditure result.
[0090] In this embodiment, the unit of sorting is a purpose-specific deposit, i.e. a virtual unit, and no account number is assigned, but this is not limited to this, and the unit of sorting may be a so-called virtual account or an actual account, etc., to which an account number is assigned.
[0091] In this embodiment, as part of the income and expenditure management, if the planned expenditure amount based on expenditures scheduled to occur by the next closing date or expenditures derived from the expenditure history is larger than the current balance, the support server may notify the user of the insufficient balance by push notification, etc. In this case, the user's wasteful spending can be reduced.
[0092] In this embodiment, if a purpose-specific deposit corresponding to the group information display area has already been set, the mobile terminal may provide an area for displaying information on purpose-specific deposits, such as purpose-specific balances, instead of the button in the group information display area.
[0093] In this embodiment, the purpose-specific deposit creation screen may have an area for displaying a planned achievement date calculated backwards from the target amount and the monthly savings amount.
[0094] In this embodiment, when the deposit button 276 on the income / expense result screen 244 is tapped, an instruction to transfer funds of the transfer amount set on the setting slider 274 from the ordinary deposit account to the savings deposit account is transmitted from the mobile terminal 12 to the support server 16. The funds transferred in accordance with the instruction are first reflected in the balance for which a deposit purpose is not set, which is displayed in the unset balance display area 460 on the purpose-specific deposit top screen 290. However, this is not limited to this, and for example, the income / expense result screen may be configured so that the user can specify how to allocate the transferred funds to purpose-specific deposits.
[0095] Fig. 16(a) is a representative screen diagram of an income / expense result screen 502 according to a modified example. The income / expense result screen 502 has a difference display area 504 corresponding to the difference display area 272 in Fig. 10(d), an allocation setting area 506, a deposit button 508 corresponding to the deposit button 276 in Fig. 10(d), and a do not deposit button 510 corresponding to the do not deposit button 278 in Fig. 10(d). The allocation setting area 506 has a first object 512 for receiving the designation of the total transfer amount, a second object 514 and a third object 516 for designating how much of the transfer amount designated by the first object 512 should be allocated to each purpose-specific deposit, and a transfer amount display area 518 for displaying the transfer amount corresponding to the current position of the first object 512 in numerical form.
[0096] The user can specify the transfer amount by sliding the first object 512 along the slider bar 520. The user can freely set the amount to be allocated to each purpose-specific deposit by sliding the second object 514 and the third object 516. The first segment 522 from the left end of the slider bar 520 to the third object 516 corresponds to the purpose-specific deposit specified by the deposit purpose "travel". The second segment 524 from the third object 516 to the second object 514 corresponds to the purpose-specific deposit specified by the deposit purpose "marriage". The third segment 526 from the second object 514 to the first object 512 corresponds to the purpose-specific deposit specified by the deposit purpose "residence". In order to visually show the correspondence between the segments and the deposit purposes, the allocation setting area 506 has a deposit purpose display area 530 that displays the deposit purpose corresponding to each segment in association with that segment. It should be noted that a fourth segment 528 from the first object 512 to the right end of the slider bar 520 corresponds to the amount of the previous month's balance result displayed in the difference display area 504 that cannot be transferred.
[0097] The allocation setting area 506 visually displays the total transfer amount and the amount allocated to each purpose-specific deposit. In particular, the ratio of the length of the portion other than the fourth segment 528 to the total length of the slider bar 520 represents the ratio of the total transfer amount to the last month's income and expenditure result. The ratio of the length of the first segment 522 to the length of the second segment 524 to the length of the third segment 526 represents the ratio of the amount allocated to each purpose-specific deposit, "travel", "marriage", and "housing". FIG. 16(b) shows an allocation setting area in which the amount allocated to each purpose-specific deposit is shown as a numerical value. FIG. 16(c) shows another display mode of the amount allocated to the purpose-specific deposit. When the user taps the desired deposit purpose, the mobile terminal 12 displays the amount allocated to the purpose-specific deposit specified by the tap in a pop-up 532.
[0098] Before displaying the balance screen 502 on the display 124, the mobile terminal 12 acquires information on purpose-specific deposits stored in the purpose-specific deposit information storage unit 130 from the support server 16 via the network 14. The mobile terminal 12 sets the display mode of the allocation setting area 506 based on the deposit purpose and monthly savings amount contained in the acquired information. If three deposit purposes are set, the mobile terminal 12 places three objects on the slider bar 520 and divides the slider bar 520 into four segments, including one corresponding to the amount not to be transferred. At that time, the default length of each segment is set according to the ratio of the monthly savings amount. Alternatively, the user may be allowed to register a default allocation ratio in advance, and the default segment length may be set according to the registered ratio.
[0099] When the mobile terminal 12 detects a tap on the deposit button 508, it generates a transfer request signal including allocation information specifying the allocation set in the allocation setting area 506 and the total transfer amount, and transmits it to the support server 16 via the network 14. The support server 16 transmits a request to the accounting server 18 to transfer the total transfer amount from the user's ordinary deposit account to the savings deposit account. At the same time, the support server 16 sorts the transfer amount according to the allocation amount for each deposit purpose specified in the allocation information. In particular, the support server 16 performs a process of adding the amount specified in the allocation information included in the transfer request signal to the purpose-specific balance of each purpose-specific deposit.
[0100] According to this modification, not only is there a seamless transition from the display of the balance result to the transfer, but the transfer amount can also be allocated on the spot. Therefore, the user does not need to open the purpose-specific deposit top screen 290 separately after the transfer and individually allocate the amount, improving user convenience. In addition, the user can be reminded of the purpose of the deposit at the balance result display stage, which promotes continued savings activities.
[0101] In an embodiment, the mobile terminal 12 may execute a goal achievement process when the goal amount of the purpose-specific deposit is achieved. The goal achievement process includes a process of displaying an achievement notification screen 602 on the display 124 to notify the user of the achievement of the goal, and a process of prompting the user to transfer the achieved goal amount from the savings account to the ordinary savings account.
[0102] 17(a)-(d) are representative screen diagrams of screens displayed on the display in the goal achievement process. FIG. 17(a) is a representative screen diagram of an achievement notification screen 602. The achievement notification screen 602 has text 606 and visual effects 608 indicating that the goal amount has been achieved, a coupon confirmation button 604 for prompting confirmation of a coupon, and a delete button 610. When the mobile terminal 12 detects a tap on a purpose-specific deposit for which the goal amount has been achieved among a plurality of purpose-specific deposits displayed in the purpose list display area 462 (FIG. 15(a)), the mobile terminal 12 displays the achievement notification screen 602 corresponding to the tapped purpose-specific deposit on the display 124. Alternatively, the mobile terminal 12 may display the achievement notification screen 602 on the display 124 at the timing when the goal amount is achieved. When the mobile terminal 12 detects a tap on the coupon confirmation button 604, the mobile terminal 12 displays a coupon screen having a configuration similar to that of the purpose-specific coupon screen 478 on the display 124. In this way, by encouraging users who have achieved their target amount to use a coupon related to the goal in conjunction with the achievement of the goal, the coupon usage rate can be increased.
[0103] When the mobile terminal 12 detects a tap on the delete button 610, it displays an achieved deposit details screen 612 (FIG. 17(b)) having a similar configuration to the purpose-specific deposit details screen 464 on the display 124. The main difference between the achieved deposit details screen 612 and the purpose-specific deposit details screen 464 is that the achieved deposit details screen 612 has a transfer button 614 for prompting the user to transfer the achieved goal amount of funds from the savings account to the regular savings account. In other words, when the balance of a purpose-specific deposit reaches the goal amount, the mobile terminal 12 starts displaying the transfer button on the corresponding purpose-specific deposit details screen. When the mobile terminal 12 detects a tap on the transfer button 614, it displays a transfer processing screen 616 (FIG. 17(c)) on the display 124. The transfer processing screen 616 has a transfer source information display area 618 , a transfer destination information display area 620 , a transfer amount setting area 622 , a transfer execution button 624 , a numeric input button 626 , and a cancel button 628 .
[0104] The transfer process on the transfer process screen 616 is basically limited to the transfer of an amount within the range of the achieved target amount from the savings account to the regular savings account. The transfer source information display area 618 displays the balance of the savings account as the transfer source. The transfer destination information display area 620 displays the balance of the regular savings account as the transfer destination. The transfer amount setting area 622 accepts the designation of the amount of funds to be transferred from the savings account to the regular savings account. The transfer amount setting area 622 is configured similarly to the setting slider 274, and in particular, the maximum amount that can be transferred is set to the achieved target amount. The numeric input button 626 is a button for setting the amount of funds to be transferred by directly inputting numbers. When the numeric input button 626 is tapped, the mobile terminal 12 launches an interface for accepting the direct input of numbers. When the mobile terminal 12 detects a tap on the cancel button 628, it cancels the transfer process.
[0105] When the mobile terminal 12 detects a tap on the transfer execution button 624, it performs processing to transfer funds of the amount set in the transfer amount setting area 622 from the savings account to the regular savings account. This processing is similar to the processing performed when a tap on the deposit button 276 on the income / expense result screen 244 is detected. When the transfer processing is completed, the mobile terminal 12 displays a transfer completion screen 630 (FIG. 17(d)) on the display 124. The transfer completion screen 630 displays text indicating that the transfer has been completed and the transferred amount.
[0106] In this way, by providing a lead from the purpose-specific deposit details screen where the target amount has been achieved to a screen for performing transfer processing, the effort required for the user to transfer funds from a savings account to a regular savings account can be reduced. Normally, the use of funds from a savings account is restricted, so even if a user achieves a target amount for a certain purpose, they often cannot use the funds unless they first transfer the amount to a regular savings account. In contrast, in this embodiment, the transfer processing screen 616 can be displayed with one tap from the goal achievement by pressing the transfer button 614, thereby reducing the effort required for such transfers and improving user convenience.
[0107] Furthermore, according to this embodiment, an interface is provided that allows the user to roughly and quickly and intuitively specify the amount to be transferred using the setting slider 274 and transfer amount setting area 622. When inputting the amount to be transferred using the numeric input buttons 626 or the like, the user can specify the amount precisely, even to the nearest decimal point, but this makes the input operation cumbersome and can take a long time to complete, particularly on mobile devices that are not suited to numeric input. In contrast, this embodiment allows the user to visually set the amount using the slider, making it possible to quickly complete the input in situations where it is sufficient to roughly set the amount.
[0108] In FIG. 9 of the embodiment, a case where the user has already completed initial registration to the management application 20 has been described. The process of initial registration to the management application 20 will be described. FIG. 18 is a representative screen diagram of an initial registration screen 680. When a tap on the initial registration button 642 on the application launch screen 640 shown in FIG. 10(a) is detected, the mobile terminal 12 displays the initial registration screen 680 on the display 124. The initial registration screen 680 has a user information input area 682, a password input / confirmation area 684, and a start button 686. A user who is about to start using the management application 20 inputs a desired user name and his / her own email address in the user information input area 682. The user inputs a desired password in the password input / confirmation area 684, and inputs the same password for confirmation. When the mobile terminal 12 detects a tap on the start button 686, it generates an initial registration request including the initial registration user information input in the user information input area 682 and the initial registration password input in the password input / confirmation area 684, and transmits the request to the support server 16 via the network 14. The user authentication unit 102 of the support server 16 registers the information included in the received initial registration request as new user information in the user information storage unit 116. When the registration is completed, the user authentication unit 102 transmits a registration completion notification to the mobile terminal 12 via the network 14. When the mobile terminal 12 receives the registration completion notification, it displays the home screen 242 on the display 124.
[0109] In FIG. 9 of the embodiment, a case where the user's account has already been registered has been described. The process of registering an account in the management application 20 will be described. FIGS. 19(a) and 19(b) are representative screen diagrams of screens displayed on the display 124 in the account registration process. FIG. 19(a) is a representative screen diagram of a home screen 690 displayed to a user who has not yet registered an account. The difference between the home screen 690 in FIG. 19(a) and the home screen 242 in FIG. 10(c) is that the former displays an account registration notification area 692 instead of the latter's balance result display area 254. When the mobile terminal 12 detects a tap on the account registration notification area 692, it displays an account registration screen 694 (FIG. 19(b)) on the display 124. The account registration screen 694 has an account information input area 696 that accepts input of account authentication information used for authentication in the accounting system server 18, and a register button 698.
[0110] The user inputs information on an already opened ordinary savings account and authentication information such as the PIN number in the account information input area 696. When the mobile terminal 12 detects a tap on the register button 698, it generates an account registration request including the account authentication information input in the account information input area 696, and transmits it to the support server 16 via the network 14. The account system linkage unit 140 of the support server 16 starts authentication related to the account system based on the received account authentication information. The account system linkage unit 140 may transmit the received account authentication information as is to the account system server 18, and authentication may be performed by the account system server 18. Alternatively, the account system linkage unit 140 may perform authentication instead of the account system server 18. If the result of the authentication is authentication failure, the account system linkage unit 140 notifies the mobile terminal 12 of that effect via the network 14. The mobile terminal 12 performs authentication failure processing such as displaying the account registration screen 694 on the display 124 again. If the result of the authentication is successful, the accounting system linkage unit 140 registers information about the ordinary savings account related to the successful authentication in the user information storage unit 116 in association with the user ID. When the registration is completed, the accounting system linkage unit 140 transmits a registration completion notice to the mobile terminal 12 via the network 14. When the mobile terminal 12 receives the registration completion notice, it displays the home screen 242 on the display 124.
[0111] After the initial account registration through the account registration screen 694, authentication is no longer required to use the financial functions related to the savings button 268 and the wallet button 270. In other words, after logging in to the management application 20, the financial functions become available without authentication of the accounting system. However, after a predetermined period of time (one month, six months, one year, etc.) has passed, or if an irregular event such as a change in the mobile terminal 12 occurs, authentication of the accounting system to use the financial functions may be performed again.
[0112] In the embodiment, a case has been described in which the user is prompted to input authentication information via the login screen 240, and the input authentication information is used to perform user authentication in the support server 16, but this is not limiting. For example, user authentication may be performed using a passcode or fingerprint authentication function provided by the operating system of the mobile terminal 12.
[0113] 20(a) to (c) are representative screen diagrams of screens displayed on the display in the authentication process. When detecting a tap on the menu button 241 of the home screen 242 shown in FIG. 10(c), the mobile terminal 12 displays a list of menus (not shown) including "Settings" on the display 124. When detecting a tap on "Settings", the mobile terminal 12 displays a setting screen 650 (FIG. 20(a)) on the display 124. The setting screen 650 has an account setting area 652, a passcode setting area 654, a notification setting area 656, and an income / expenditure management setting area 658.
[0114] When the mobile terminal 12 detects a tap on the passcode setting area 654, it displays a passcode setting screen 660 ( FIG. 20(b) ) on the display 124. The passcode setting screen 660 has a passcode availability setting area 662, a passcode change area 664, and a fingerprint authentication availability setting area 666. The passcode availability setting area 662 has a toggle switch, and accepts a setting of whether or not a passcode can be used by operating the switch. When the toggle switch is turned ON, the use of a passcode is activated, and when the toggle switch is turned OFF, the use of the passcode is deactivated. When the passcode change area 664 is tapped, a screen (not shown) for changing the passcode is displayed on the display 124. The fingerprint authentication availability setting area 666 has a toggle switch, and accepts a setting of whether or not fingerprint authentication can be used by operating the switch. When the toggle switch is turned ON, the use of fingerprint authentication is activated, and when the toggle switch is turned OFF, the use of the fingerprint authentication is deactivated.
[0115] When the use of a passcode is activated in the passcode availability setting area 662 and the use of fingerprint authentication is activated in the fingerprint authentication availability setting area 666, a passcode / fingerprint authentication screen 670 (FIG. 20(c)) is displayed on the display 124 instead of the login screen 240 when the management application 20 is started next time or later. In the passcode / fingerprint authentication screen 670, the mobile terminal 12 performs user authentication using a preset passcode or fingerprint authentication, or both. In the example of FIG. 20(c), fingerprint authentication is performed first, and if the fingerprint authentication is passed, the input of a passcode (for example, a four-digit number) is requested. Note that the passcode authentication and fingerprint authentication may be performed at any time when the screen of the management application 20 is displayed on the display 124. The mobile terminal 12 activates key information that manages the login state by this passcode / fingerprint authentication and performs authentication. Since the key information that manages the login state has an expiration date, when the expiration date expires and the key information expires, the user is requested to input a user ID / password. [Explanation of symbols]
[0116] 10 account management system, 12 mobile terminal, 14 network, 16 support server, 18 accounting server.
Claims
1. A computer that can communicate with the server via a network A function for obtaining the results of a calculation of income and expenditure based on the deposit and withdrawal data of the user's first account; a function of asking the user on a display whether or not to transfer funds between the first account and a second account of the user different from the first account, the amount of the funds being based on the obtained result; a function of displaying on the display information indicating the obtained result in response to the inquiry from the user, and an amount designation receiving area for receiving designation of the amount of funds to be transferred between the first account and the second account; when an instruction to transfer is received from the user in response to an inquiry to the user, a transfer instruction signal including an amount specified in the amount specification reception area is transmitted to the server; The program, wherein the server executes a process for transferring a specified amount of funds between the first account and the second account when the server receives the transfer instruction signal.
2. 2. The program according to claim 1, wherein the amount designation reception area includes a slide bar for designating the amount of funds to be transferred, and an upper limit of the amount that can be designated by the slide bar is set based on the difference between income and expenditure.
3. The second account has a lower degree of freedom in withdrawal than the first account, the server separates the balance of the second account into multiple deposit purposes; When income exceeds expenses, the slide bar visibly indicates the amount of the transferred funds that is allocated to each deposit purpose; said transfer instruction signal includes an allocation amount for each deposit objective designated in association with said slide bar; 3. The program according to claim 2, wherein said server, upon receiving said transfer instruction signal, executes sorting of the funds to be transferred according to the allocation amounts for each designated deposit purpose.
4. 4. The program according to claim 2 or 3, wherein the slide bar is configured to accept modification of the amount allocated to each of the plurality of deposit purposes.
5. A program as claimed in any one of claims 1 to 4, characterized in that the computer is made to realize a function of displaying information representing the obtained results on the display in different manners depending on whether income exceeds expenses or expenses exceed income.
6. The second account has a lower degree of freedom in withdrawal than the first account, the server separates the balance of the second account into multiple deposit purposes; The program further includes: a function of displaying on the display, in association with specific information of a group including at least one content designated by the user, an area for receiving an instruction to create a sorting unit related to the specific information, and a budget area showing a budget related to the specific information; The program according to any one of claims 1 to 5, characterized in that when the reception area receives an instruction, the program causes the display to display a purpose input area in which a deposit purpose is input to identify the unit to be created, and a target amount input area in which a target amount for the unit to be created is input.
7. A function of inputting a deposit purpose corresponding to the specific information in advance in the purpose input area; 7. The program according to claim 6, further comprising a function of inputting a target amount corresponding to a budget shown in the budget area into the target amount input area in advance.
8. 8. The program according to claim 6 or 7, wherein the balance in said second account is virtually divided for said multiple deposit purposes.
9. The program according to any one of claims 6 to 8, further comprising a function for causing the computer to display on the display information on coupons selected for the created sorting unit based on the deposit purpose and balance of the unit.
10. A function for accepting authentication information for user authentication; The program according to any one of claims 1 to 9, further comprising a function for causing the computer to realize a display area on the display including the balance and income / expense status of the first account of the authenticated user.
11. 11. The program according to claim 1, further comprising causing the computer to realize a function of displaying, on the display, a point display area including points given to the user.
12. A function of displaying on the display a detailed screen of deposits by purpose including the deposit purpose and the balance of the created classification unit; When the balance reaches the target amount, a function to start displaying the transfer instruction reception area on the purpose-specific deposit details screen; The program described in any one of claims 6 to 9, further comprising a function for causing the computer to realize, when a transfer instruction acceptance area is specified, a transfer processing screen on the display including a designation area that accepts designation of the amount of funds to be transferred from the second account to the first account within the range of an achieved target amount.
13. A function for obtaining the results of a calculation of income and expenditure based on the deposit and withdrawal data of the user's first account; and a function of asking the user on a display whether or not to transfer funds, an amount based on the obtained result, between the first account and a second account of the user that is different from the first account.
14. A computer that can communicate with a server that sorts user account balances via a network, a function of displaying on a display the specific information of a group including at least one content designated by the user in association with an area for receiving an instruction to create a sorting unit related to the specific information; A program characterized by realizing a function of displaying, when the reception area receives an instruction, a purpose input area on the display in which a deposit purpose is input to specify the unit to be created.
15. A means for calculating income and expenditure based on deposit and withdrawal data of a first account of a user; means for transmitting the result of said balance calculation to said user's computer via a network; means for receiving, via the network, a transfer instruction signal indicating that funds should be transferred, the signal being generated by the computer in response to an inquiry as to whether or not funds in an amount based on the transmitted result should be transferred between the first account and a second account of the user different from the first account; a means for executing a process for transferring funds between the first account and the second account upon receiving the transfer instruction signal; and means for dividing the balance in said second account into a plurality of deposit purposes.
16. an acquisition unit that acquires the balance of a first account of a user and a second account of the user, the second account having a lower degree of freedom for withdrawal than the first account, from another server that manages the second account; A server comprising: a sorting unit that sorts the balance acquired by the acquisition unit.
17. 17. The server according to claim 16, wherein the server is managed by a different entity than a financial institution that manages the other server.
Citation Information
Patent Citations
Apparatus, method and program for displaying deposits and savings, server, method and program for providing deposits and savings information, storage medium, and apparatus, method, program and server for managing asset
JP2003030449A
Secondarily linked spending accounts and savings accounts
JP2010521741A
Client terminal equipment, storage medium, bank server device, information transmission method, information transmission program and information transmission / reception program
JP2002334210A
