JP2008181553A - Financial institution operation support system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a financial institution operation support system for improving operability by linking registration of a daily business report with display of a customer attribute and display of important facts. <P>SOLUTION: The financial institution operation support system for supporting business operations in a financial institution comprises a database 120 which stores the customer attribute that is information related to a customer, including necessity of explanation of important facts in a transaction of financial product, an important fact explanation history showing whether explanation of important facts was performed or not, and a daily business report having a contact content with the customer and including the important fact explanation history in association with each other; a customer attribute display means which displays the customer attribute; an important fact display/registration means which displays important facts based on the customer attribute and registers the important fact explanation history based on the display of the important facts to the database 120; and a daily business report registration means which registers the daily business report to the database 120. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention displays important matters for explaining important matters in transactions of financial products to customers in order to support sales operations in financial institutions, and explains important matters indicating whether or not important matters have been explained. The present invention relates to a financial institution sales support system that creates and registers a daily business report including a history.

  In financial institutions such as securities companies that sell financial products such as investment trusts, customers create system of daily reports that create contact details, store them in the database, and register customer transactions. Systematization of attributes is being promoted.

  On the other hand, when financial institutions sell financial products, there are many cases where explanations about risks are not sufficiently given to customers, which causes troubles. Therefore, in accordance with the Financial Products Sales Act, which came into effect from April 2001, financial institutions are required to explain important matters in transactions of financial products such as characteristics and risks of financial products to customers when selling financial products. Mandatory.

  However, the current situation is that the registration process (memory) of daily business reports and the display of customer attributes are not well linked in operability, including explanation of important matters in the transaction of financial products. The conventional customer attribute system has a function to store and register customer attributes and refer to them, but it is important to indicate whether important matters in the transaction of financial products have been explained to customers. There was no function to manage item explanation history or list display.

  The present invention has been made in view of the above-described problems, and relates to sales support for financial institutions that improves operability by associating business daily reports with important matter explanation histories in financial product transactions, for example, by linking these displays. The purpose is to provide a system.

In order to achieve the above-described object, the present invention is a financial institution sales support system that supports sales operations in a financial institution, and whether or not important matters in transactions of financial products are explained to customers. The history storage means for storing the important matter explanation history to represent, the business daily report storage means for storing the business daily report showing the contact details with the customer, the important matter explanation history stored in the history storage means based on the customer Data association means for associating with the business daily report stored in the business daily report storage means is provided.

  According to such a configuration, for example, the important matter explanation history indicating whether or not the important matter in the transaction of the financial product has been explained can be associated with the daily business report, and the important matter explanation history can be easily managed. Note that the data association means of the present invention can be configured, for example, by providing an identifier for identifying two or more related data, or associating a predetermined storage area in the storage means with each other on an address.

  The financial institution sales support system of the present invention further comprises customer attribute storage means for storing customer attributes including necessity of explanation of important matters in the transaction of financial products, and the data association means further includes the customer attributes Is related to the important matter explanation history and the business daily report based on the customer.

  According to such a configuration, for example, the sales employee can easily determine from the customer attributes whether or not it is necessary to explain important matters about a certain financial product for the customer. It is possible to prevent the occurrence of Moreover, management of important matter explanation histories is easily performed.

  The financial institution sales support system of the present invention is based on customer attribute display means for displaying customer attributes including necessity of explanation of important matters in the transaction of financial products, and customer attributes displayed on the customer attribute display means. Important matter display means for displaying the important matter, history registration means for storing and registering in the history storage means as the important matter explanation history that the important matter has been displayed by the important matter display means, It comprises business daily report display means for displaying a business daily report by reflecting the important matter explanation history registered by the history registration means in the business daily report.

  According to such a configuration, it is possible to manage daily business reports, customer attributes, and important matter explanation histories in transactions of financial products in association with each other, and it is possible to improve the operability of business.

  In the embodiment of the present invention, there is provided a financial institution sales support system for supporting sales operations in a financial institution, which is information about customers and includes customer attributes including necessity of explanation of important matters in financial product transactions. And an important matter explanation history indicating whether or not the important matter has been explained, a database that stores contents related to contact with the customer and a business daily report including the important matter explanation history, and the customer attribute are displayed. A customer attribute display means, an important matter display / registration means for displaying the important matter explanation history based on the display of the important matter and displaying the important matter explanation history based on the important matter display in the database, There is disclosed a financial institution sales support system characterized by comprising business daily report registration means for registration in a database.

  In the embodiment of the present invention, a financial institution sales support server for supporting business operations in a financial institution, which is information related to the customer and includes the necessity for explanation of important matters in transactions of financial products An attribute, an important matter explanation history indicating whether or not the important matter has been explained, and a business daily report that is the content of contact with the customer and includes the important matter explanation history are stored in the database in association with each other, and input from the user and The customer attribute is transmitted to the financial institution sales support client based on the request received from the financial institution sales support client for performing output to the user, and the important attribute received from the financial institution sales support client The item explanation history is registered in the database, and the daily business report received from the financial institution sales support client is stored in the database. Financial institution business support for the server, characterized in that the registration to the database is disclosed.

  Furthermore, in the embodiment of the present invention, the client is a financial institution sales support client that supports sales operations in the financial institution, and is a customer including information on the customer and necessity of explanation of important matters in the transaction of the financial product. In order to obtain the attribute, the request is transmitted to the financial institution sales support server of the present invention, the customer attribute received from the financial institution sales support server is displayed, and the important items registered in advance are set as the customer attribute. The important matter explanation history indicating whether or not the important matter has been explained is transmitted to the financial institution sales support server, and the important matter explanation history is reflected in the daily business report that is the content of contact with the customer. A financial institution sales support client is disclosed that creates the daily business report and transmits the business daily report to the financial institution sales support server. According to such a client, the registration of the daily business report, the display of customer attributes, and the display of important matters are linked to display the screen in accordance with the flow of contact with the actual customer and the sales staff's The operation burden can be reduced, and the sales staff can smoothly carry out sales activities in accordance with the financial product sales law.

As described in detail above, according to the present invention, it is possible to provide a financial institution sales support system that improves operability by associating business daily reports with important matter explanation histories, for example, by linking them together. There is an effect.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the configuration of a financial institution sales support system will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of a financial institution sales support system in the present embodiment. This financial institution sales support system includes a head office 100 and a branch office 200. The head office 100 includes a server 110 and a client 130 connected to the database 120. 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.

  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.

  Next, an outline of the operation of the financial institution 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.

  The database 120 stores daily business reports, customer attributes, important matter explanation histories and the like in association with each other. Here, the business daily report is information in which the content of one contact with a customer is recorded. The customer attributes are basic information about the customer such as name, address and age, and information such as suitability of transactions including investment experience and necessity of explanation of important matters in the transaction of financial products. Important matters in the transaction of financial products are information such as characteristics and risks of the financial products. The important matter explanation history is information indicating whether or not important matters in the transaction of financial products have been explained.

  The clients 130 and 130A display a daily sales report registration screen that functions as a daily sales report registration unit, a customer attribute display screen that functions as a customer attribute display unit, and an important item display screen that functions as an important item display unit. Accepts input. Here, the business daily report registration screen includes, for example, a "daily report save button" for registering a business daily report, an important matter explanation column for checking whether important matters in transactions of financial products have been explained, customer code It is a screen provided with input functions such as the date and time of contact with the customer, the contact method with the customer, the purpose of contact with the customer, and the proposed product. The customer attribute display screen is a screen for displaying customer attributes, and includes, for example, an “important matter explanation button” for displaying an important matter display screen. The important matter display screen is a screen for displaying an explanation of important matters in the transaction of the financial product, and has, for example, a “registration button for daily report” for registering the important matter explanation history in the business daily report. These will be described later with reference to FIGS.

  In response to the access from the clients 130 and 130A, the server 110 transmits the customer attributes and the like stored in the database 120 to the clients 130 and 130A. In addition, the server 110 registers the daily business report and the important matter explanation history received from the clients 130 and 130A in the database 120.

  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.

  Next, details of the operation of the financial institution sales support system will be described with reference to FIGS. FIG. 2 is a flowchart showing an example of the operation of the financial institution sales support system in the present embodiment. Here, explanation will be made assuming that the salesperson of the head office 100 is in contact with the customer by telephone or face-to-face while browsing the screen displayed on the client 130 and performing input using the client 130. Note that the salesperson of the branch 200 can perform the same operation using the client 130A.

  First, the sales employee inputs, for example, a customer code to the client 130 in order to display a customer attribute display screen. The client 130 transmits the customer code to the server 110 via the intranet 300. Receiving the customer code, the server 110 searches the database 120 for a customer attribute corresponding to the customer code, and transmits it to the client 130 via the intranet 300. The client 130 opens a new window and displays the customer attribute display screen (S1).

  FIG. 3 is a diagram illustrating an example of a customer attribute display screen. In the customer attribute display screen shown in FIG. 3, whether or not it is necessary to explain important matters in the transaction of the financial product is displayed in the column below the financial product name. The customer selects in advance whether or not it is necessary to explain important matters for each financial product, and the selected result is registered in advance in the customer attribute. Here, the display of “necessary” indicating whether or not important matters need to be explained also serves as an “important matter explanation required button” for displaying an important matter display screen. In order to explain important matters to the customer, the sales employee presses an “important matter explanation button” corresponding to the financial product for which the important matter display screen is to be displayed. For example, when the sales employee desires to display the important stock display screen of “stock”, the sales representative presses the “important matter explanation required button” 20 in the column under “stock” on the customer attribute display screen shown in FIG.

  Here, the client 130 determines whether or not the salesperson desires to display the important item display screen (S2). If the salesperson does not wish to display the important item display screen (S2, N), the flow proceeds to processing S3.

  On the other hand, when the salesperson desires to display the important item display screen (S2, Y), the client 130 searches for an important item corresponding to the “important item explanation required button” pressed by the salesperson, and opens a new window. The important item display screen is displayed (S11). Here, important matters in the transaction of each financial product may be stored in the database 120 and transmitted from the server 110 to the client 130, or may be stored in the client 130.

  FIG. 4 is a diagram illustrating an example of an important matter display screen. Based on the important matter display screen displayed on the client 130, the sales employee explains important matters in the transaction of the financial product to the customer.

  Next, when the sales employee wishes to end the important matter display screen after registering the important matter explanation history, the salesperson presses the “Register to daily report” button 30 on the important matter display screen shown in FIG. Further, when the sales staff desires to end the important matter display screen without registering the important matter explanation history, the sales employee instructs the end of the important matter display screen on the important matter display screen shown in FIG.

  Here, the client 130 determines whether or not the salesperson wishes to register the important matter explanation history (S12). If the salesperson does not wish to register the important matter explanation history (S12, N), the client 130 closes the window and deletes the important matter explanation history (S13), and the flow returns to the process S3.

  On the other hand, when the sales staff desires to register the important matter explanation history (S12, Y), the client 130 transmits the important matter explanation history to the server 110 via the intranet 300. Receiving the important matter explanation history, the server 110 registers the important matter explanation history in the database 120 (S21), and transmits a daily business report registration screen including the important matter explanation history to the client 130. The client 130 closes the window and deletes the important matter explanation history (S22), and displays the business daily report registration screen including the received important matter explanation history (S23).

  FIG. 5 is a diagram showing an example of the daily business report registration screen. By pressing the “Register to daily report” button 30 on the important item display screen shown in FIG. 4, the important item explanation column of the business daily report registration screen is automatically checked as shown in FIG. Here, the important matter explanation column of the business daily report registration screen can be structured so that it cannot be manually checked.

  Next, the sales employee inputs the date and time of contact with the customer, the contact method with the customer, the purpose of contact with the customer, the proposed product, etc. to the client 130 as a daily business report (S24). When the salesperson wishes to register the daily business report, he presses the “daily report save button” 40 on the business daily report registration screen shown in FIG.

  Here, the client 130 determines whether or not the salesperson wishes to register the daily business report (S25). If the salesperson does not wish to register the daily business report (S25, N), the flow proceeds to processing S27. On the other hand, when the salesperson desires to register the daily business report (S25, Y), the client 130 transmits the business daily report to the server 110 via the intranet 300. The server 110 registers a daily business report in the database 120 (S26).

  When the sales staff desires to end the business daily report registration screen, the sales staff instructs the business daily report registration screen to end on the business daily report registration screen shown in FIG. Here, the client 130 determines whether or not the salesperson wishes to end the business daily report registration screen (S27). If the salesperson does not wish to end the business daily report registration screen (S27, N), the flow returns to step S24. On the other hand, when the salesperson desires to end the business daily report registration screen (S27, Y), the client 130 closes the window and deletes the business daily report registration screen (S28), and the flow returns to the process S3.

  If the salesperson does not want to display the customer attribute display screen (S2, N), or after the important matter display screen is deleted (S13) or after the daily business report registration screen is deleted (S28), the client 130 It is determined whether or not the customer attribute display screen is desired to end (S3). Here, when the sales employee desires to end the customer attribute display screen, the sales employee instructs the customer attribute display screen to end on the customer attribute display screen shown in FIG. If the salesperson does not wish to end the customer attribute display screen (S3, N), the flow returns to the process S2. On the other hand, when the salesperson desires to end the customer attribute display screen (S3, Y), the client 130 closes the window and deletes the customer attribute display screen (S4), and the flow ends.

  As described in detail above, according to the embodiment of the present invention, the screen along the flow of contact with the actual customer is obtained by linking the registration of the daily business report, the display of the customer attribute, and the display of the important matter. Is displayed and the burden on the operations of the sales staff can be reduced, and the sales staff can smoothly carry out the sales activities in accordance with the financial product sales law. Further, by registering a daily business report including an important matter explanation history indicating whether or not an important matter in the transaction of the financial product has been explained, the important matter explanation history can be easily managed. In addition, by linking the display of customer attributes with the display of important matters, sales representatives will not forget to explain important matters when interacting with customers based on the necessity of explanation of important matters in customer attributes. It can be carried out.

It is a block diagram which shows an example of a structure of the financial institution sales support system in this Embodiment. It is a flowchart which shows an example of operation | movement of the financial institution sales support system in this Embodiment. It is a figure which shows an example of a business daily report registration screen. It is a figure which shows an example of a customer attribute display screen. It is a figure which shows an example of an important matter display screen.

Explanation of symbols

  100 head office, 110 server, 120 database, 130, 130A client, 200 branches, 300 intranet.

Claims (3)

  A financial institution sales support system for supporting sales operations in a financial institution, and a history storage means for storing an important matter explanation history indicating whether or not important matters in transactions of financial products are explained to customers; A business daily report storage means for storing a business daily report indicating contact details with the customer, and the important matter explanation history stored in the history storage means is associated with the business daily report stored in the business daily report storage means based on the customer. A financial institution sales support system comprising a data association means.   2. The financial institution sales support system according to claim 1, further comprising customer attribute storage means for storing customer attributes including necessity of explanation of important matters in transactions of financial products, wherein the data association means includes the customer attributes A financial institution sales support system characterized in that, based on a customer, the important matter explanation history and the daily business report are associated with each other.   3. The financial institution sales support system according to claim 1 or 2, wherein customer attribute display means for displaying customer attributes including necessity of explanation of important matters in the transaction of financial products, and displayed on the customer attribute display means. Based on the customer attributes, the important matter display means for displaying the important matter, and the history storage means for storing and registering the important matter display history as the important matter explanation history by the important matter display means A financial institution sales support system comprising: registration means; and business daily report display means for displaying a daily business report by reflecting the important matter explanation history registered by the history registration means in the daily business report .

Images