JP4675007B2 - Financial product sales support system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a financial product sales support system that manages a history of prospectus delivery results including, for example, a receipt of confirmation for prospectus delivery, in order to support sales operations of financial products.
[0002]
[Prior art]
In recent years, it has become possible for banks to sell financial products such as investment trusts. In such financial products with the risk of a loss of principal, there are many cases where the explanation about the risk is not sufficiently given to the customer, which causes trouble. Financial institutions such as securities companies and banks are obliged to issue prospectuses of financial products to customers when selling financial products. According to the Financial Products Sales Act, which came into effect in April 2001, The responsibility of the seller becomes increasingly severe. For this reason, an increasing number of financial institutions require customers to confirm their prospectus for issuing prospectuses as self-defense means on the selling side.
[0003]
On the other hand, systematization of information related to transactions has been promoted at financial institutions. For example, according to “electronic transaction system and electronic transaction method” disclosed in Japanese Patent Laid-Open No. 2001-125959, transaction history information can be stored and retrieved electronically.
[0004]
[Problems to be solved by the invention]
However, there are few systems that support the current sales operation of financial products, even if there is a function for registering the prospectus delivery, it is possible to manage the prospectus delivery as a history. There was no function to manage until receipt.
[0005]
The present invention has been made in view of the above-described problems, and is capable of managing a history of prospectus delivery results including a receipt history of a confirmation letter with respect to a prospectus delivery, and displaying a history of prospectus delivery results. An object is to provide a product sales support system.
[0006]
[Means for Solving the Problems]
In order to achieve the above-described object, the present invention is a financial product sales support system that supports sales operations of financial products, registers the prospectus delivery results for a customer, and stores the customer with respect to the prospectus. Prospectus issuance record registration means to include the receipt record in the prospectus delivery record when the confirmation letter is received from the prospectus, and management of the prospectus delivery record registered in the prospectus grant record registration means for each customer The data management means is provided.
[0007]
According to such a configuration, by managing the receipt of confirmations for the prospectus delivery, it is possible to prevent the sales of the financial product when the confirmation is not received from the customer. It can be avoided. In addition, by managing the history of the prospectus issuance results, it is possible to avoid duplication of prospectuses. The data management means of the present invention provides a storage area for the prospectus delivery results for each customer in storage means such as a database.
[0008]
The financial product sales support system of the present invention is characterized by comprising a prospectus delivery history display means for displaying a history of delivery results of the prospectus registered in the prospectus delivery history registration means. is there.
[0009]
According to such a configuration, the transaction trend of the customer can be grasped by displaying the history of the prospectus delivery results.
[0010]
Further, in the financial product sales support system of the present invention, the prospectus issue record registration means erases the receipt record when the prospective document delivery date is newly registered.
[0011]
According to such a configuration, the confirmation receipt for the new prospectus is automatically deleted, so that the confirmation receipt for the new prospectus can be registered without forgetting. it can.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the configuration of the financial product sales support system will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the financial product sales support system in the present embodiment. This financial product sales support system includes a head office 100 and a branch office 200. The head office 100 includes a server 110 connected to the database 120 and a client 130. The branch 200 is composed of a client 130A. The client 130 and the client 130A perform the same operation. Further, there may be a plurality of clients 130 and clients 130A. The server 110 and the clients 130 and 130A are connected by an intranet 300.
[0013]
Note that the database 120 may be provided in the server 110, and the server 110 and the client 130 may be integrated, and is not limited to the form shown in FIG.
[0014]
Next, an outline of the operation of the financial product sales support system will be described with reference to FIG. A salesperson at the head office 100 accesses the server 110 from the client 130 via the intranet 300. A sales employee in the branch 200 accesses the server 110 via the intranet 300 from the client 130A.
[0015]
The database 120 stores the prospectus delivery results and the like for each customer. Prospectus issuance results are information about prospectuses issued to customers, confirmation date indicating prospectus delivery date, delivery method such as mailing or handing over, product name such as fund name, prospectus date or edition number, and receipt record It consists of the date of receipt of the letter. Here, the confirmation document indicates receipt of the prospectus, and is requested to the customer when the financial institution issues the prospectus.
[0016]
Since the database 120 holds all the prospectus delivery results as a history, the database 120 holds the prospectus delivery results in a dedicated table different from the customer attributes that do not manage the history. Customer attributes are basic information about customers such as name, address, and age, and information such as investment experience.
[0017]
The clients 130 and 130A display a prospectus issue history display screen that functions as a prospectus issue history display means and a prospectus issue history registration screen that functions as a prospectus issue history registration means, as well as input by a salesperson. Accept.
[0018]
The prospectus issue history display screen includes a function for displaying a prospectus issue history for a specified customer and a function for narrowing and searching for a prospectus issue history. This screen includes a narrowing search condition input area, a “search button” 10 for performing a search search for a prospectus history, a “new button” 20 for performing a new input of a prospectus delivery record, This is a screen provided with an “edit button” 30 for performing a correction input of a prospectus issue result and an input of a confirmation receipt date. The prospectus issuance record registration screen is a screen provided with an input area for the prospectus issuance record and a “save button” 40 for saving the inputted prospectus record. These will be described later with reference to FIGS.
[0019]
The server 110 registers the prospectus issue results received from the clients 130 and 130A in the prospectus issue result table of the database 120 for each customer. Further, the server 110 transmits the prospectus delivery history, etc. stored in the prospectus delivery record table of the database 120 to the clients 130, 130A in response to the access from the clients 130, 130A.
[0020]
Here, all the operations in the server 110 and the clients 130 and 130A are realized by software. This software may be in the form of a Web application, for example.
[0021]
Next, details of the operation of the financial product sales support system will be described with reference to FIGS. FIG. 2 is a flowchart showing an example of the operation of the financial product sales support system in the present embodiment. Here, description will be made on the assumption that the salesperson of the main store 100 browses the screen displayed on the client 130 and performs input using the client 130. Note that the salesperson of the branch 200 can perform the same operation using the client 130A.
[0022]
First, in order to display the prospectus issue history display screen, the salesperson inputs, for example, the display order of the customer code and the prospectus issue results to the client 130. Here, for example, the display order of the prospectus delivery results is specified in the order of delivery date. The client 130 transmits a prospectus history record request corresponding to the customer code to the server 110 via the intranet 300. Receiving the history request, the server 110 searches the prospectus grant record table in the database 120 and transmits the retrieved prospectus grant record history to the client 130 via the intranet 300. The client 130 opens a new window, displays the prospectus issue history display screen (S1), and displays the entire history of the received prospectus issue history (S2).
[0023]
FIG. 3 is a diagram illustrating an example of a prospectus issue history display screen. As shown in FIG. 3, on the prospectus issue history display screen, the entire history of the prospectus issue results of the designated customer is displayed in the order of issue date. When there are a large number of displayed prospectus delivery results histories, the salesperson can perform a narrowing search on the prospectus delivery results history based on conditions such as delivery date and product name. In FIG. 3, as an example, a condition input area in the case of narrowing down by delivery date is added.
[0024]
Here, the client 130 determines whether or not the salesperson desires a narrowing search of the history of the prospectus grant results (S3). If the salesperson does not wish to search for a prospectus history, the flow proceeds to step S4.
[0025]
On the other hand, when the salesperson wishes to narrow the search for the history of the prospectus delivery results (S3, Y), the salesperson inputs the narrowing search conditions (S11). For example, there is a “search date” shown in FIG. “Search date” is an option for designating a search period retroactively from the present. For example, if the salesperson wants to narrow down the prospectus history for two weeks from the present, search for “two weeks” in the “search date” on the prospectus history display screen shown in FIG. After clicking, the “search button” 10 is pressed.
[0026]
The client 130 displays, on the prospectus issue history display screen, the results that match the conditions of the refinement search among the entire history of the prospectus issue results as a refinement result (S12), and the flow proceeds to process S4.
[0027]
Next, when the salesperson desires to newly register the prospectus issue record, the “new button” 20 is pressed on the prospectus issue history display screen shown in FIG. Here, the client 130 determines whether or not the salesperson wishes to newly register the prospectus delivery result (S4). If the salesperson does not wish to register a new prospectus grant record (S4, N), the flow proceeds to step S5.
[0028]
On the other hand, when the sales staff wishes to newly register the prospectus delivery result (S4, Y), the client 130 opens a new window and displays the prospectus grant result registration screen (S21). FIG. 4 is a diagram illustrating an example of a prospectus issue record registration screen. The sales employee performs a new entry of the prospectus grant record on the prospectus grant record registration screen shown in FIG. 4 (S22).
[0029]
Next, when the salesperson wishes to end the prospectus grant achievement registration screen after saving the input prospectus grant achievement record, the “sales button” 40 is clicked on the prospectus grant achievement registration screen shown in FIG. Press. In addition, when the sales staff wishes to exit the prospectus issuance record registration screen without saving the input prospectus issuance record, the prospectus issuance record registration screen shown in FIG. Instruct the end. This is performed, for example, by pressing an end button (not shown).
[0030]
Here, the client 130 determines whether or not the salesperson wishes to save the prospectus grant record (S23). If the salesperson does not wish to save the prospectus issue result (S23, N), the flow proceeds to processing S25.
[0031]
On the other hand, when the sales staff wishes to save the prospectus delivery results (S23, Y), the client 130 transmits the prospectus grant results to the server 110 via the intranet 300. The server 110 registers the received prospectus grant record in the prospectus grant record table of the database 120 for each customer (S24), and the client 130 closes the window and deletes the prospectus grant record screen (S25). The flow proceeds to process S5.
[0032]
Next, when the sales staff wishes to update the registered prospectus delivery history, the prospectus to be updated from the prospectus delivery history displayed on the prospectus delivery history display screen shown in FIG. After selecting the delivery result, the “edit button” 30 is pressed. The client 130 determines whether or not the salesperson desires to update the prospectus issue result (S5). If the salesperson does not wish to update the prospectus delivery results (S5, N), this flow ends.
[0033]
On the other hand, when the salesperson desires to update the prospectus delivery results (S5, Y), the client 130 creates and displays the prospectus grant results registration screen using the prospectus delivery results selected by the salesperson. (S31).
[0034]
In the prospectus issue achievement registration screen shown in FIG. 4, the registered prospectus issue achievements are displayed in the input area of each item. The sales employee inputs a prospectus grant achievement correction input or a confirmation receipt date on the prospectus grant achievement registration screen shown in FIG. 4 (S32).
[0035]
When a sales employee issues a prospectus with a new date (version) for the same product, the salesperson corrects the prospectus date to a new date. Here, the client 130 determines whether or not the salesperson has corrected the prospectus date in the correction input of the prospectus delivery result (S33), and the salesperson has not corrected the prospectus date ( (S33, N), the flow proceeds to processing S35. On the other hand, when the salesperson corrects the prospectus date (S33, Y), the client 130 automatically deletes the confirmation receipt date (S34).
[0036]
Next, when the salesperson wishes to end the prospectus grant achievement registration screen after saving the input prospectus grant achievement record, the “sales button” 40 is clicked on the prospectus grant achievement registration screen shown in FIG. Press. In addition, when the sales staff wishes to exit the prospectus issuance record registration screen without saving the input prospectus issuance record, the prospectus issuance record registration screen shown in FIG. Instruct the end. This is performed, for example, by pressing an end button (not shown).
[0037]
Here, the client 130 determines whether or not the salesperson wishes to save the prospectus grant record (S35). When the salesperson does not wish to save the prospectus issue result (S35, N), the flow proceeds to processing S37.
[0038]
On the other hand, when the salesperson desires to save the prospectus grant record (S35, Y), the client 130 transmits the prospectus grant record to the server 110 via the intranet 300. The server 110 that has received the prospectus grant record updates the prospectus grant record registered in the prospectus grant record table of the database 120 (S36), and the client 130 closes the window and registers the prospectus grant record. Is deleted (S37), and this flow ends.
[0039]
According to the embodiment of the present invention, it is possible to prevent the sale of the financial product when the confirmation is not received from the customer by managing the receipt record of the confirmation for the issuance of the prospectus, Trouble can be avoided. Further, by managing the history of the prospectus delivery results, the sales staff can avoid the redundant dispatch of the prospectus. Further, by displaying the history of the prospectus delivery results, the sales staff can grasp the customer's transaction trend. In addition, by automatically erasing the confirmation receipt for the previous prospectus, the confirmation receipt for the new prospectus can be registered without forgetting.
[0040]
【The invention's effect】
As described above in detail, according to the present invention, the financial product sales that can manage the history of prospectus delivery results including the receipt of confirmation documents for the prospectus delivery and display the history of prospectus delivery results There is an effect that a support system can be provided.
[Brief description of the drawings]
FIG. 1 is a block diagram showing an example of a configuration of a financial product sales support system in the present embodiment.
FIG. 2 is a flowchart showing an example of the operation of the financial product sales support system in the present embodiment.
FIG. 3 is a diagram illustrating an example of a prospectus issue history display screen.
FIG. 4 is a diagram illustrating an example of a prospectus issue record registration screen.
[Explanation of symbols]
100 head office, 110 server, 120 database, 130, 130A client, 200 branches, 300 intranet.

Claims (1)

A financial product sales support system for supporting sales operations of financial products,
For each customer, a server having a database that stores information on prospectuses issued to customers, including prospectus delivery date, prospectus date or edition number , and prospectus delivery results including confirmation receipt date indicating receipt results When,
A client having a prospectus delivery history display means configured by a prospectus delivery history display screen, and a prospectus delivery results registration means configured by a prospectus delivery history registration screen;
The server
Storing the prospectus delivery results received from the client in the database as a history for each customer;
In response to the history request from the client, the prospectus issuance history stored in the database is transmitted to the client,
The client
Prospectus issuance history display means,
Receives an input of the prospectus delivery history request including the customer code from the user and transmits it to the server, displays the prospectus delivery history received from the server, and displays the prospectus delivery history history from the user. We accept selection of prospectus grant results from the inside,
By means of registering prospectus delivery results,
The prospectus issuance result is received from the user and transmitted to the server, and the items included in the prospectus issuance result selected by the user in the prospectus issuance history display means are displayed, and the displayed prospectus issuance result is displayed. Among the included items, if the prospectus date or revision of the prospectus is accepted from the user, the prospectus acceptance date is deleted from the prospectus delivery results, the prospectus date or edition number is revised, and the confirmation letter acceptance date Send the prospectus grant record with deleted to the server,
This is a financial product sales support system.

Images