JP5614754B2 - Event transfer management device, system and program - Google Patents

Description

  The present invention relates to an event transfer management device, a system, and a program for securely managing transfer of events such as ceremonial occasions and celebrations.

  In my life, I have more opportunities to participate in various ceremonial occasions in order to facilitate socializing. In particular, if you have children and grandchildren as well as your children and grandchildren as well as your children and grandchildren at a number of ceremonial occasions, such as marriage, childbirth celebration, birthday celebration, Shichigosan celebration, admission / A series of events related to children and grandchildren, such as entrance celebrations, graduation celebrations, adult celebrations, and employment celebrations, occur regularly and continuously. The number of such events related to children increases as you get older, but the older you get, the more difficult it is to remember who and when to celebrate such events. Become.

  Therefore, for example, in Patent Document 1, life event information regarding the return time and return partner at birth, Shichigosan, entrance ceremony, adult ceremony, wedding ceremony, etc. is registered. A life event management program for notifying the user of the other party and time is disclosed.

  However, the method described in the above-mentioned Patent Document 1 is intended to reduce the burden of arranging a return item from the recipient side when a life event has occurred on the giver side who has given a celebration in the past. And it was n’t on the side of the celebration. The prior notification is triggered only when a gift is received. In the first place, when you give a congratulation to your child, grandchild, great-grandchild, etc., you do not expect a return, and the recipient is not likely to give back to their parents or grandparents. The older you are, the more you worry about forgetting the party and the time you are celebrating than the worry of giving it back. Even if you remember it, it would be hard to prepare cash for each event and hand it over or send it back.

JP-A-2005-208844

  The present invention has been made in view of the problems as described above, and notifies users, especially elderly users, of the occurrence of numerous events such as ceremonial occasions and provides congratulations, etc. The purpose is to provide a mechanism to ensure delivery.

In order to solve the above problems, the present invention provides an event transfer management device having the following functions.
An event registration unit that receives event registration information from the user's terminal, and an event management table creation unit that creates an event management table that stores the occurrence date of the event for each destination that is the target of the event based on the event registration information Based on the event management table, the amount specified by the user is deducted from the savings account held by the user, and the reserved time deposit that expires before the date of occurrence of the event with the specified amount as a reserve Information on events that occur after the maturity notice date and before the next maturity notice date is added to the reserve term deposit creation section created for each event and the maturity notice that notifies the user of the maturity date of the reserve time deposit in advance. And a maturity information notifying unit.

  According to the above invention, the event transfer management device of the present invention obtains event registration information (for example, information on the name, date of birth, sex, etc.) of a child or grandchild who is the subject of celebration at the event from the user's terminal. Upon receipt, a typical event that occurs thereafter is determined from the registered information, and an event management table is created that stores the event occurrence date for each target party. For example, the date of occurrence of an event such as birthday, New Year's Day, Shichigosan, admission / entry, etc. is obtained from the date of birth and gender. Next, based on the created event management table, the amount specified by the user is deducted from the savings account held by the user, and the reserved time deposit that expires before the event occurrence date with the specified amount as reserve Create for each event. Information on events that occur after the maturity notification date and before the next maturity notification date is added to the maturity notification that notifies the user of the maturity date of the accumulated time deposit. In this way, the user simply inputs the event registration information, and the event transfer management device determines the date of the subsequent event occurrence, creates an accumulated time deposit according to the event occurrence date, and provides congratulatory money, etc. Will make you ready. In addition, since the event information is notified in accordance with the expiration notification, it is not necessary for the user to remember each event occurrence date and the destination.

The event transfer management device of the present invention can also have the following functions.
The event registration information includes a start date and an end date of a time for sending a celebration or non-congratulation for the event.

  According to the above invention, it is possible to set the first date and the last date to give a congratulation or non-congratulation (congratulations etc.). By doing this, for example, the first birthday celebration for an event that occurs every year, such as a birthday (usually the birthday of the next year after birth), and the child's growth will soon be When there is no longer a need for a celebration, a date that ends with a birthday celebration can be set. Therefore, it is possible to prevent giving birth celebrations forever. In addition, a one-time event can be registered by setting the start date and end date to the same date.

The event transfer management device of the present invention can also have the following functions.
The event transfer management device includes a savings deposit transfer unit, and the savings deposit transfer unit transfers the maturity amount from the accumulated time deposit account to a specified savings account in advance before the date of occurrence of the event. It is characterized by.

  According to the above invention, the event transfer management device not only notifies the event information in accordance with the maturity notification, but also automatically transfers the maturity of the accumulated account to a predetermined account. In this way, by transferring the maturity money to your savings account, you can use it as a source for the next funded time deposit.

The event transfer management device of the present invention can also have the following functions.
The pre-designated savings account is the account of the target party of the event.

  According to the above invention, the maturity can be transferred directly to the account of the other party. In this way, it is possible to save the trouble of withdrawing a congratulatory money from one's own account and handing it over to the other party.

The event transfer management device of the present invention can also have the following functions.
The reserve time deposit creation unit temporarily increases the amount of the reserve when it determines that the maturity amount of the created reserve deposit is less than the amount designated as a celebration or non-congratulation for the event. And

  According to the above invention, when the amount designated as a celebration or non-congratulation (congratulations, etc.) is insufficient for the maturity of the accumulated time deposit, the event transfer management device temporarily increases the accumulated amount of the accumulated fund. Create a funding period. By doing in this way, it is possible to cover a congratulatory money, etc. only with the maturity of the funding period. In other words, when there is a shortage, it is possible to save the trouble of transferring money from the user's ordinary deposit.

The event transfer management device of the present invention can also have the following functions.
The funded time deposit creation unit temporarily adjusts the maturity date of the funded time deposit when the maturity date of the created funded deposit comes after the event occurrence date.

  According to the above invention, even when an event occurs before the maturity date of the accumulation period, the event transfer management device adjusts the maturity date to be before the event occurrence date. A funding maturity can be allocated to money.

  In addition, the present invention can be regarded as a bank system including an event transfer management device as described below, or a computer program that allows a computer to function as an event transfer management device, and has the same effects as the above-described invention. Can do.

  A bank system in which a user terminal and an event transfer management device are connected via a network, wherein the user terminal accepts event registration information and transmits the event registration information to the event transfer management device. An event management table creation unit for creating an event management table for storing the date of occurrence of the event for each partner to be an event based on the received event registration information, and the user based on the event management table Withdrawing the amount specified by the user from the savings account held by the user, and using the specified amount as a reserve, a reserve time deposit creation unit that creates a reserve time deposit that expires before the event occurrence date for each event; and The maturity notice for notifying the user in advance of the maturity date of the funded time deposit is after the maturity notice date. Banking system characterized in that it comprises, and maturity information notification unit for adding information of events that occur before the next expiration notification date Te.

  A computer program for receiving event registration information from a user's terminal and managing the event, the computer storing the occurrence date of the event for each destination to be an event based on the event registration information Based on the event management table creation unit for creating an event management table and the event management table, the amount designated by the user is deducted from the ordinary savings account held by the user, and the designated amount is used as a reserve. A reserve time deposit creation unit that creates a reserve term deposit that expires before the occurrence date for each event, and a maturity notice that notifies the user of the maturity date of the reserve time deposit in advance after the maturity notice date. Functions as a maturity information notification unit that adds information about events that occur before the maturity notification date A computer program that characterized the door.

  According to the above invention, it is possible to reliably notify the user of the occurrence of an event such as a ceremonial occasion so that a congratulatory money or the like can be reliably delivered.

1 is a diagram illustrating an overall configuration of a bank system 1 according to an embodiment of the present invention. It is a figure which shows the event management table 43 which concerns on embodiment of this invention. It is a figure for demonstrating the general mechanism of a reserve time deposit. It is a figure for demonstrating in detail the structure of the deposit account which concerns on embodiment of this invention using a specific example. It is a flowchart which shows the process sequence of the event registration reception part 11 which concerns on embodiment of this invention. It is a figure which shows the process sequence of the reserve time deposit preparation part 13 and the maturity information notification part 14 which concern on embodiment of this invention. It is a figure which shows the whole structure of the bank system 1 at the time of adding the ordinary deposit transfer part 17 which concerns on embodiment of this invention. It is a figure which shows an example of a process when a maturity amount is insufficient with respect to the designated holiday etc. by the process which concerns on embodiment of this invention. It is a flowchart which shows the process sequence for avoiding the shortage of congratulations etc. of the reserve time deposit preparation part 13 and the maturity information notification part 14 which concern on embodiment of this invention. It is a figure which shows the event management service registration screen which concerns on embodiment of this invention. It is a figure which shows the content of the maturity notice of the accumulation time deposit which concerns on embodiment of this invention.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described in detail with reference to the accompanying drawings. Note that the same number is assigned to the same element throughout the description of the embodiment.

  FIG. 1 is a diagram showing an overall configuration of a bank system 1 according to an embodiment of the present invention. In the bank system 1, the event transfer management device 10 which is a core in the embodiment of the present invention is connected to a bank host system 20 via a network in the bank, and connected to a user terminal via a network such as the Internet. Tied.

  In the bank system 1 of the present embodiment, as a back end, an account host computer that is the host system 20 reads and writes data on a daily basis using the account DB 22 and the transaction information DB 23 for each daily transaction. To process. The event transfer management device 10 includes an event registration receiving unit 11, an event management table creating unit 12, a funded time deposit creating unit 13, and a maturity information notifying unit 14 as function units, and a database (DB; Data Base) as an event. An information DB 15 and a funded account information DB 16 are provided.

  The event registration receiving unit 11 receives event registration information 41 that is information for registering an event in the event transfer management device 10 from a user's terminal, and delivers it to the event management table creation unit 12. The event registration information 41 includes the name, date of birth, gender, relationship between the user and the other party (children, children, gifts, etc.). Grandchildren, cousins, siblings, children's sons, etc.), user's savings account information, and bank account information of the other party to send congratulations. There are many cases in which events such as celebrations are determined from the date of birth and do not need to be entered individually. The other party's bank account information is necessary when transferring a congratulatory money by bank transfer, but is not necessary when handing out a congratulatory money or gift by hand. The event registration information 41 may include information unique to the event in addition to the above information. For example, an event-specific date that is not required from the date of birth, such as a wedding anniversary. The terminal for inputting the event registration information 41 is typically an arbitrary information processing terminal as long as it can be connected to the event transfer management apparatus 10 via a network, such as a PC (Personal Computer) or a mobile phone owned by the user. However, for a user who cannot operate the terminal, a terminal that a store clerk inputs from a store such as a bank based on a user request may be used.

  Based on the input event registration information 41, the event management table creation unit 12 calculates an occurrence date of an event that periodically occurs according to the attribute of the other party, and creates an event management table 43 to be described later. The event management table 43 is stored in the event information DB 15 and is managed for each user. The occurrence date of the event that occurs periodically is automatically set in the event transfer management device 10 based on the date of birth. For example, if the grandchild's date of birth is October 3, 2010, the first seventy-five is set to November 15, 2013. For events that occur irregularly, the event occurrence date entered in the event registration information 41 is used.

  The funded time deposit creation unit 13 refers to the user event management table 43 from the event information DB 15 and creates the user's funded time deposit according to the date of occurrence of each event stored in the table. For example, if the current birthday is February 1 and your grandson's next birthday is May 5, create a short-term funding deposit with a three-month funding period so that the maturity date will come before May 5 To do. Of course, the maturity date may come on May 5th. As will be described later, even if an event occurs and some events occur before the maturity date, the event can be dealt with.

  It is also possible to withdraw a designated reserve amount from a savings account designated by the user at the start of accumulation and transfer the amount to the reserve account. In this manner, a funded time deposit account in which each event occurrence date and maturity date are associated is created. The information on the created reserve deposit is stored in the reserve account information DB 16, and information on the event corresponding to the maturity notice date and the event corresponding to the maturity date, maturity date, maturity amount, and interest are simultaneously recorded.

  The maturity information notification unit 14 always refers to the accumulated account information DB 16 and notifies the user of the maturity date on a predetermined date (for example, one month before). Although the maturity date notification itself is also performed by a regular time deposit or the like, in this system, related event information (event message) is added to the maturity notification. For example, a message such as “The next birthday of OO-chan (grandchild's name) is May 5, 2011” is added to the maturity notification.

  The customer notification distribution means 30 is an arbitrary means for notifying a maturity notification such as a time deposit. In this system, the maturity information notifying unit 14 created by the maturity information notifying unit 14 finally plays a role of sending a maturity notice to the user. The means for sending may be notified by telephone or the like, in addition to mail, by e-mail and / or a message added to the expiration notification.

  The functional configuration of the event transfer management device 10 described above is merely an example, and one functional unit may be further divided, or a plurality of functional units may be configured as one functional unit. Typically, each functional unit reads a computer program stored in a memory (RAM: Random Access Memory, ROM: Read Only Memory) or a storage device, and a CPU (Central Processing Unit) built in the device. The necessary program reads and writes necessary data from a DB (Data Base) stored in a storage device, and in some cases controls other related hardware (for example, input / output devices and communication interface devices) It is realized by doing. In addition, the database (DB) in the embodiment of the present invention may be a commercial database, but it simply means a collection of tables and files, and the internal structure of the database itself does not matter.

  FIG. 2 is a diagram illustrating the event management table 43 according to the embodiment of the present invention. The event management table 43 is created by the event management table creation unit 12 based on the event registration information 41 in an arbitrary format. As shown in the figure, the event management table 43 includes a name, a bank account number, a relationship with the user, the basic information on the date of birth of the recipient 301, the date of birth, for each recipient to whom a gift is given. If there is an anniversary that cannot be specified from the date, the anniversary information 301A that is the type of the anniversary and the event, and information 302A, 302B, 302C,.

  A unique event ID is set for each event. In order to simplify the notation in the figure, it seems that the events of three destinations are linked to one event ID, but the event IDs of the three destinations are managed separately. The event management table creation unit 12 automatically calculates and sets the date of occurrence of each event that can be specified from the date of birth and gender. For example, birthday, Shichigosan, entrance to school, entrance. In the case of Shichigosan, the date of the event is set on November 15th, which is 3 and 5 years old for boys and 3 and 7 years for girls. Admission and admission are automatically requested from the date of birth. Each event stores at least a congratulatory money (amount of congratulations, etc.), a start date, a next date, and an end date. For events that occur every year, such as birthdays, Christmas, and New Year's cards, the event management table shows the start date of the celebration, the next date (the date of the next celebration), and the end date of the celebration 43, and the event transfer management device 10 updates the next date every time a day of celebration or the like passes every year. If the end date is undecided, 9999/99/99 is set for the time being. The event transfer management device 10 ends the processing of the event at that time only when the next celebration day is the end date.

  For events that cannot be determined from the date of birth, such as the wedding anniversary of a son or daughter, the user enters the event occurrence date (anniversary) and its type in the event registration information 41. Can be registered in the event management table 43. Thereafter, the anniversary celebration may continue every year. Even if it is an event such as a birthday or New Year's card that occurs every year, it does not necessarily have to be set as a celebration event every year, but only in the year specified by the user, such as the 5th and 10th years. May be. You can also register an event that ends only once, such as a celebration for winning a soccer tournament or a celebration for winning an award. In that case, the start date and the end date are simply matched. The event registration accepting unit 11 provides a means for the user to update the event management table 43 at any time.

  The above example has mainly focused on events for grandchildren and children, but of course the same applies to events for adults. Items that can be specified by date of birth include celebrations for the ceremony of the adults and 60th birthday, and items that cannot be specified by the date of birth include employment celebrations, wedding celebrations, housewarming celebrations, moving celebrations, discharge celebrations, etc. Of course, the same applies not only to celebrations, but also to non-celebration events such as legal matters.

  FIG. 3 is a diagram for explaining a general mechanism of a funded time deposit. A funded time deposit is a deposit that is automatically transferred from a savings account in the name of the user. Deposit a certain amount every month (funded amount) and start a funding period in a predetermined operation period. Then, as shown in the figure, “details” (details 1 to 6) are created for each deposit amount, and the maturity date is determined by the specified operation period for each detail, and after this maturity date, it is automatically updated for each detail. Is done. In addition to the monthly reserve, it is also possible to make a temporary deposit. In that case, a separate statement is made for the temporary reserve. All these details will be collected to make a single fixed term deposit contract.

  In the embodiment of the present invention, by using this funded time deposit mechanism, a funded time account that becomes a maturity date before the event occurrence date or before the event occurrence date is automatically created so that the necessary holidays for each event can be accumulated. To do. Before a predetermined period of maturity date, the user is sent a maturity notice. If there is a recent event, the account will be canceled without automatic renewal, and the maturity amount (principal + interest- Transfer the transfer fee) to the specified savings account. The predetermined saving account may be a user account or a counterpart account.

  FIG. 4 is a diagram for explaining the reserve deposit mechanism according to the embodiment of the present invention in more detail using a specific example. The system operation for the user is shown on the left side of the figure, and the event occurrence date is shown on the right side of the figure.

  For example, if the user starts 10,000 yen every even month according to the payment of the pension, and the funding period starts on October 15 in the operation period of 3 months, the maturity date of the first funding period is the following year On January 15th, the maturity notice is usually issued one month ago, so it will be December 15th. As for this user, it is assumed that Christmas, New Year's Day, Birthday, and Shichigosan are registered as events for grandchild A and grandchild B, respectively, and wedding anniversary is registered for daughters. And

  In this case, since the most recent event as seen from the first expiration notification 200 is Christmas 100A, 100B, information indicating that the target is the grandchild A and the grandchild B on the event occurrence date of December 24 as events corresponding to Christmas 100A, 100B. (Message) is added to the expiration notification 200. Further, the system checks the date of occurrence of the next event, and if it detects that the next event is the New Year's cards 101A and 101B for the grandchild A and the grandchild B on January 1, the following year, January 1 will be reserved for this time. It is determined whether it is before or after the expiration notice 200 of the time deposit and the next expiration notice 201. If it is after the maturity notification 200 and before the next maturity notification 201, information on the New Year's event is also added to the maturity notification 200. If it is after the next maturity notice 201, information on the New Year's event will be added to the next maturity notice 201 on February 15. In the example shown in the figure, the current maturity notification date is December 15 and is before January 1 of the new year, so the new year event information 101A, 101B is added to the maturity notification 200. The most recent event for the second expiration notice 201 is the birthday 102 of the grandchild A, but since it is before the third expiration notice 202, the birthday 102 is associated with the expiration notice 201 in this case. Thereafter, by repeating the same processing, the system notifies the user of who and what event, and the time of occurrence of the event, by the latest expiration notification before the event occurrence date. In addition to simply notifying the maturity, only the accumulated deposit corresponding to the event is canceled before the maturity date, and the amount determined in advance in the event registration information 41 is transferred as a congratulatory payment to the counterparty's (congratulatory) savings account. You may make it. This can be easily realized by adding an ordinary deposit transfer unit 17 to be described later to the event transfer management device 10. It should be noted that an accumulation period that does not have an event corresponding to the maturity date may be automatically extended or canceled on the maturity date.

  By doing in this way, the user can determine whether the event occurrence date and a predetermined holiday necessary for the event can be covered by the maturity amount when the maturity notification is received. If the amount of maturity is greater than the total amount of congratulations for the event, you can set the system to automatically transfer it to the other party's account. Further, the difference between the maturity amount and the congratulatory money may be set to be transferred to the user's savings account. Of course, it is also possible to transfer all of the congratulatory money etc. to one's ordinary savings account without automatically transferring it to the counterparty account, and withdrawing the cash from the account and handing it to the counterparty. Further, when the maturity amount is smaller than the total amount of congratulations for the event, the shortage amount may be drawn from the user's savings account and automatically transferred to the partner account together with the maturity amount. Note that if the maturity amount is insufficient, another process can be performed, which will be described later.

  FIG. 5 is a flowchart showing a processing procedure of the event registration receiving unit 11 according to the embodiment of the present invention. First, the event registration receiving unit 11 waits until there is an event registration request in step S10. When the event registration request is received, it is checked whether the event is a new registration (step S11). If it is a new event, a registration information new input screen is transmitted to prompt input of event registration information 41 (step S12). If it is determined in step S11 that it is not new registration, the registration information is read out, and a registration information update screen is transmitted to prompt input (step S14). In either case, if the input data is OK (step S15; Yes), in the case of update, the data is sorted in the order of occurrence date of events to be registered (step S16). Finally, the event registration information 41 is stored in the event information DB 15 (step S17). The registered event registration information 41 is stored separately from the event management table for later verification. If the registration is an update, the event management table creation unit 12 is called, and the event management table 43 is also updated based on the update registration information (not shown).

  FIG. 6 is a flowchart showing processing procedures of the funded time deposit creation unit 13 and the maturity information notification unit 14 according to the embodiment of the present invention. Note that the processing details of the event management table creation unit 12 are clear in the above description, and thus the flowchart is omitted.

  First, the reserve time deposit creation unit 13 reads the user's reserve account information from the reserve account information DB 16 in step S20. The accumulated account information includes all the information of the created user's accumulated time deposit accounts (accumulated amount, interest rate, operation period, maturity date, maturity notification date, maturity amount, etc.). Next, if the current date is the accumulation period creation date (step S21; Yes), the accumulation period deposit creation unit 13 creates an accumulation period creation account (step S22). Specifically, the funds are transferred from the specified user's savings account to the reserved fixed account based on the specified reserve amount and operation period. Note that the funding periodic creation date may not be the maturity date, but may be a predetermined date such as the previous day or the day before.

  Next, in step S23, the maturity information notification unit 14 checks, for each user, whether there is a funded periodic account that needs to be notified of maturity. If there is an account that requires a maturity notice, the user's event management table 43 is read (step S24), and if there is an event between the current maturity notice date and the next maturity notice date (step S25; Yes), A message related to the event is created (step S26), and the message is added to the current maturity notification and transmitted to the customer notification delivery means 30 (step S27). If there is no event between the current maturity notification date and the next maturity notification date (step S25; No), the process ends without doing anything. Here, the message related to the event is information including at least the type of event, the date of occurrence, and the target person, and may be a notification sentence created or selected by the user himself / herself.

  FIG. 7 is a diagram showing the overall configuration of the bank system 1 when the ordinary deposit transfer unit 17 according to the embodiment of the present invention is added. The ordinary deposit transfer unit 17 is added to the event transfer management device 10A of this embodiment, but is basically the same as the event transfer management device 10, and therefore only different parts will be described.

  The ordinary deposit transfer unit 17 plays a role of transferring the maturity amount to the counterparty's ordinary deposit account designated by the user from the accumulation period that has expired. The maturity amount is usually transferred to the user's savings account, but when transferring directly to the savings account of the other party, the maturity amount is insufficient due to a shortage of the maturity, etc., or an interest rate. However, there are many cases where this is not necessarily the intended celebration, etc., so that processing is necessary. Therefore, the ordinary deposit transfer unit 17 is provided separately from the maturity information notification unit 14. When the transfer destination is another bank account, the transfer is performed by connecting to the other bank system 50 through the Zengin Network.

  FIG. 8 is a diagram illustrating an example of processing in the case where the maturity amount is insufficient with respect to the designated holiday or the like in the processing according to the embodiment of the present invention. Here, as in the case of FIG. 4, it is assumed that the accumulation period starts on October 15 with an investment period of 3 months, and 10,000 yen every even month according to the payment of the pension. However, in this case, it is assumed that it is set to transfer directly to the other party's account on the maturity date as well as the maturity notice.

In this example, the first expiry notice 200 is December 15th and the next expiry notice 201 is February 15th, during which Christmas and New Year's cards exist, but the congratulatory gift is grandchild A, grandchildren at Christmas. If you set 3000 yen for B and 5000 yen for each year, the first maturity notice 200 (December 15th) will give you a total of 16000 yen for Christmas and New Years. It can be seen that the maturity (10,000 yen + interest) of the reserve deposit that matures on January 15 is not in time and the amount is not sufficient. In such a case, as a processing method,
1) It is determined at the time of event registration that such a situation occurs, and if there is a shortage, the user is prompted to adjust the amount of the congratulations in advance.
2) In this case, the transfer from the funding period is only 6,000 yen for Christmas, and 10,000 yen, which is not in time and the maturity is insufficient, is transferred from the user's ordinary deposit.
3) Temporarily change the amount of the reserve and the maturity date.
There are three possible methods. The method 1) is less preferred because it depends on the user's accumulation start time and the amount of money, and from the other party's side, it seems that the reason will increase or decrease without knowing the reason. Therefore, in this system, the method 2) or 3) is recommended, but the shortage amount is the same in 2) and 3) in that the shortage amount is withdrawn from the user's ordinary deposit. However, the required amount shall be in the user's ordinary account.

  In the embodiment of FIG. 8, a case where the method 3) is adopted is shown. In other words, at the stage of creating the funding period, the funding period deposit creation unit 13 temporarily changes the accumulated amount and the maturity date. In this example, the initial reserve amount is increased from 10,000 yen to 16000 yen, and the maturity date is set to December 15 by one month earlier. Then, the maturity notification date is November 15 (maturity notification 200), and it is possible to cover Christmas (1001A, 100B) on December 24 and New Year's coins (101A, 101B) on January 1st. When the method 2) is adopted, the maturity information notification unit 14 checks the shortage amount at the stage of creating the maturity notification, and the congratulations for the event with the shortage amount on the maturity date and the event that the maturity date is not in time, The ordinary deposit transfer unit 17 is instructed to transfer from the user's ordinary deposit to the counterparty account, not from the accumulation period.

  FIG. 9 is a flowchart showing a processing procedure for avoiding a shortage of congratulations and the like of the reserve term deposit creation unit 13 and the maturity information notification unit 14 according to the embodiment of the present invention. In FIG. 9, the processing from step S30 to S32 is substantially the same as the processing from S20 to S22 in FIG.

  In step S33, the funded time deposit creation unit 13 checks whether there is an unprocessed event before the maturity date of the funded term created this time. An unprocessed event is an event that has not been associated with the funding period (the scheduled transfer amount is greater than the maturity or the event occurrence date is before the maturity date). If there is no unprocessed event (step S33; No), the process is passed to the maturity information notification unit 14. The maturity information notification unit 14 performs normal maturity notification processing in steps S35 to S37. However, in step S36, the number of events for creating a message is not limited to one, and if a plurality of events are associated with the funded time deposit created by the funded time deposit creating unit 13 in advance, these messages are notified of maturity. Include everything in

  If there is an unprocessed event (step S33; Yes), it is checked whether or not the total transfer amount scheduled to be transferred on the maturity date exceeds the maturity amount created this time (step S38). If not exceeded (step S38; No), the event is also instructed to the maturity information notifying unit 14 (not shown) as an event related to the accumulated time deposit created this time, and the process returns to step S33. If the total amount of money to be transferred on the maturity date exceeds the maturity amount of the funded time deposit created this time (step S38; Yes), the funded time deposit creation unit 13 will use the amount of the shortage of the user only this time. Transfer from savings account to funded account and add to funded amount. In addition, the maturity date is shortened (adjusted) in time for the event (step S39).

  FIG. 10 is a diagram showing an event management service registration screen according to the embodiment of the present invention. The event management service registration screen is a screen for a user to register an event managed by this system.

  When the user logs in to the system and presses the event registration menu, a screen as shown in FIG. 10 is displayed on the user's terminal and prompted for input. First, the user, as the basic user information 300, includes a name, a savings account number, a reserve amount, a reserve date (month and date selected from every month, even month, odd month, etc.), operation period, and maturity notification date. Enter. If the user does not have a savings account at the bank, it must be created in advance. The operation period of the funding period is usually 3 months to 3 years, but it is desirable for users with many events throughout the year to choose the shortest possible period. In addition, it is desirable to set the maturity notification date usually about one month before.

  When the basic user information 300 has been entered, this time, as the recipient information, the name of the recipient to be registered, the bank account information 311 (financial institution name, account number, and account holder), date of birth, user Enter the relationship and gender. A transfer account is a user's account or a partner's account. The other party's name and account holder may be different.

  When the input of the partner basic information 301 is completed, the event information 302 is input for each event for which a congratulatory gift or the like is to be given to the partner. In the event information 302, an event type, start date, and scheduled end date are input. General event types are registered by the system, and are selected from them. If it is not in the menu, select “Other”. The start date is the date of occurrence of the first event that gives a congratulation, and the scheduled end date is the date of the last event that ends the congratulation. For example, if you give a birthday celebration from 1 to 20 years old to your grandchild who was born on May 5, 2010, the start date is May 5, 2011 and the end date is May 5, 2030. Become.

  In the event information 302, in addition to designating the initial transfer amount (such as a congratulatory money), if you want to increase (or decrease) the transfer amount with age, the amount of the increase and the update frequency Can be specified in the input area 312. In this way, the user inputs all the event information 302 to all of the destinations, but the user needs to present a table of general events in the system for each destination. You may make it correct only a part.

  FIG. 11 is a diagram showing the contents of the maturity notice of the funded time deposit according to the embodiment of the present invention. The notice of the maturity date of the accumulated time deposit is sent to the user before the predetermined date of the maturity date, but this system uses this maturity notice to notify the user of the event occurrence information. Notice.

  In the upper part 400 of FIG. 11, maturity information, that is, maturity date, accumulated account number, monthly reserve, interest, and maturity are described, and “transfer to ordinary deposit” is designated as the handling after maturity. The user's savings account number is indicated.

  In this system, in addition to the above-mentioned maturity information, the latest event information (event message) is added as in the middle 401 in the figure. This event information includes the date, type, destination name, amount of congratulations, and bank account. If this transfer account is designated, the amount of congratulations will be transferred directly to the transfer account. In this case, the difference between the maturity and the amount of congratulation is transferred to the user's savings account described in 400. When there are a plurality of destinations in the same event, a plurality of the destinations are also displayed. Although not specifically illustrated, a list in which the maturity date and the scheduled maturity amount of the created funded time deposit may be attached may be attached.

  In the lower part 402 of the figure, the amount of congratulations that the user has transferred so far and the history of the other party are displayed. This history table is displayed in order of event date, but may be displayed for each type of event or for each destination.

  As is apparent from the above description, in the present system, event information that is about to occur is notified to the user in a timely manner using the expiration notice of the accumulated time deposit for the information about the occurrence of the most recent event. By doing this, the user can automatically transfer a lot of congratulatory money to the other party without having to remember many events such as ceremonial occasions. You are free from the hassle of remittance, such as gifts. Obviously, this system can easily handle events other than ceremonial occasions.

  As mentioned above, although this invention was demonstrated using embodiment, it cannot be overemphasized that the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiments. Further, it is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Bank system 10 Event transfer management apparatus 11 Event registration reception part 12 Event management table preparation part 13 Reserve fixed deposit preparation part 14 Maturity information notification part 15 Event information DB
16 Accumulated account information DB
17 Savings Transfer Department 20 Host System 21 Account Host Computer 22 Account DB
23 Transaction Information DB
30 Customer notice delivery means 41 Event registration information 42 Maturity information with message 43 Event management table 50 Other bank system 100, 101, ... Event 200, 201, ... Maturity notice 300 User basic information 301 Other party basic information 301A Anniversary information 302, 302A, 302B Event information 400 Maturity information 401 Event information 402 Usage history

Claims (8)

An event registration unit that accepts event registration information from the user's terminal;
Based on the event registration information, an event management table creation unit that creates an event management table that stores the date of occurrence of the event for each destination that is the target of the event;
Based on the event management table, the amount designated by the user is deducted from the savings account held by the user, and the reserved time deposit that expires before the event occurrence date with the designated amount as a reserve A reserve time deposit creation section to be created for each;
A maturity information notifying unit for adding information on an event that occurs after the maturity notification date and before the next maturity notification date to the maturity notification that notifies the user in advance of the maturity date of the accumulated time deposit,
An event transfer management device comprising:   The event transfer management device according to claim 1, wherein the event registration information includes a start date and an end date of a time when a celebration or non-congratulation is sent for the event. The event transfer management device includes an ordinary deposit transfer unit,
The savings deposit transfer part transfers the maturity amount from the funded fixed deposit account to a specified savings account prior to the date of occurrence of the event,
The event transfer management device according to claim 1 or 2, characterized by the above.   4. The event transfer management device according to claim 3, wherein the pre-designated savings account is an account of a target party of the event.   The reserve time deposit creation unit temporarily increases the amount of the reserve when it determines that the maturity amount of the created reserve deposit is less than the amount designated as a celebration or non-congratulation for the event. The event transfer management device according to claim 1.   6. The funded time deposit creation unit temporarily adjusts the maturity date of the funded time deposit when the maturity date of the created funded deposit is after the event occurrence date. The event transfer management device described. A bank system in which a user terminal and an event transfer management device are connected via a network,
The terminal of the user accepts event registration information and transmits it to the event transfer management device,
The event transfer management device
Based on the received event registration information, an event management table creation unit that creates an event management table that stores the date of occurrence of the event for each destination that is the target of the event;
Based on the event management table, the amount designated by the user is deducted from the savings account held by the user, and the reserved time deposit that expires before the event occurrence date with the designated amount as a reserve A reserve time deposit creation section to be created for each;
A maturity information notifying unit for adding information on an event that occurs after the maturity notification date and before the next maturity notification date to the maturity notification that notifies the user in advance of the maturity date of the accumulated time deposit,
A bank system characterized by comprising: A computer program for receiving event registration information from a user's terminal and managing the event,
Computer
Based on the event registration information, an event management table creation unit that creates an event management table that stores the date of occurrence of the event for each destination that is the target of the event;
Based on the event management table, the amount designated by the user is deducted from the savings account held by the user, and the reserved time deposit that expires before the event occurrence date with the designated amount as a reserve A reserve time deposit creation section to be created for each;
As a maturity information notification unit for adding information on events that occur after the maturity notification date and before the next maturity notification date to the maturity notification that notifies the user of the maturity date of the accumulated time deposit in advance,
A computer program characterized by functioning.

Images