JP2010157137A - Information processing apparatus, information processing method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for determining a financial commodity being introduced according to an attribute of a customer. <P>SOLUTION: An information processing apparatus stores attribute information of a financial commodity indicating a degree of at least one of knowledge related to the financial commodity or purchase experience of the financial commodity needed for the customer so as to sell the financial commodity, inputs the attribute information of the customer indicating the degree of the knowledge related to the financial commodity or the purchase experience of the financial commodity of the customer, determines the financial commodity to be introduced to the customer from the inputted attribute information of the customer and the stored attribute information of the financial commodity, and displays a list of the financial commodities. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information processing apparatus, an information processing method, and a program, and more particularly to a technique for determining a financial product to be introduced to a customer.

  In recent years, due to the amendment of the Financial Instruments and Exchange Law, when selling financial products, it is obliged to explain the details of the products in a document before contracting, and companies have to manage them.

  The process of purchasing financial products is as follows. First of all, the customer must fill out a prior consent form (questionnaire before purchasing financial products) before purchasing the product. Select and explain. The customer side fills in an application form if there is a product that he likes in the explanation of the bank employee, talks to the customer about the characteristics of the product, and the bank staff asks the manager for approval and enters into a contract.

In Patent Literature 1, when a financial product is recommended, in order to confirm whether it can be recommended in consideration of the transaction history, the transaction of the product that matches the product ID (within the same business) requested by the customer is constant. If the same product is not transacted within a certain period of time, the investment target corresponding to the product ID (that is, the target of the requested product) It has been proposed to further check whether a transaction has been made.
JP 2008-217396 A

  However, in the past, users had to select financial products that are allowed to be sold or introduced according to the customer's knowledge and experience of financial products from among many financial products, which was complicated. .

  Further, conventionally, even when a bank clerk (user) does not have a qualification necessary for selling or introducing a predetermined financial product, there is a possibility that the user mistakenly sells or introduces the financial product.

  Furthermore, because the financial products that can be sold or introduced vary depending on the characteristics (customer attributes) such as whether the customer is an individual, a corporation, or a borrower, the user can respond to various customer attributes. The financial product to be selected must be selected from many financial products, and the work is complicated, and there is a risk of introducing or selling an incorrect product.

  An object of the present invention is to provide a mechanism for determining financial products that can be introduced according to customer attributes.

  The information processing apparatus according to the present invention stores attribute information of the financial product indicating the degree of at least one of knowledge about the financial product and purchase experience of the financial product, which is necessary for the customer to sell the financial product. Attribute storage means, input means for inputting the customer attribute information indicating knowledge about the financial product possessed by the customer or the purchase experience of the financial product, customer attribute information input by the input means, From the attribute information of the financial product stored in the attribute storage means, a determination means for determining a financial product to be introduced to the customer, and a display means for displaying a list of financial products determined by the determination means. Features.

  According to the present invention, financial products that can be introduced can be determined according to customer attributes.

<Description of FIG. 1>
FIG. 1 is a diagram illustrating a configuration example of a system according to the present embodiment.

  As shown in FIG. 1, the system according to the present embodiment has a configuration in which a client 101, a client 104, a server 102, and an image processing apparatus 103 are connected to be communicable with each other via a network 105 such as a LAN. It has become.

  The client 101, the client 104, and the server 102 are configured by an information processing apparatus such as a computer.

  The image processing apparatus 103 can read a document such as a form, create an electronic document, and transmit the created electronic document to an information processing apparatus such as the server 102. Further, the image processing apparatus 103 can print (output) in response to a request from an information processing apparatus such as the server 102.

The client 101 is a computer of an applicant who requests approval, and the client 104 is a computer of an approver that determines (examines) whether approval is possible or not in accordance with the approval request. Further, there may be a plurality of clients 101, servers 102, image processing apparatuses 103, and clients 104, respectively.
<Description of FIG. 2>
FIG. 2 is a diagram illustrating a hardware configuration of the client 101, the client 104, and the server 102 illustrated in FIG.

  In FIG. 2, reference numeral 201 denotes a CPU 201 that controls each device and controller connected to the system bus 204 in an integrated manner.

  Further, the ROM 202 or the external memory 211 is necessary for realizing a BIOS (Basic Input / Output System) that is a control program of the CPU 201, an operating system program (hereinafter referred to as OS), and a function executed by the server or each client. Various programs to be described later are stored.

  The RAM 203 functions as a main memory, work area, and the like for the CPU 201.

  The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown).

  A video controller (VC) 206 controls display on the display 210. The display may be a CRT display or a liquid crystal display.

  A memory controller (MC) 207 is a hard disk (HD) or floppy disk that stores a boot program, browser software (hereinafter also referred to as a Web page browsing program), various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a CompactFlash (registered trademark) memory connected to the (registered trademark) disk (FD) or PCMCIA card slot via an adapter.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via the network 105, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the display 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example.

  Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the display 210.

  A program for realizing the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary.

Further, various data and various tables used by the program according to the present invention are stored in the external memory 211, and detailed description thereof will be described later.
<Description of FIG. 3 (Block Diagram)>
Next, the hardware configuration of the controller unit of the image processing apparatus 103 shown in FIG. 1 will be described with reference to FIG.

  FIG. 3 is a block diagram illustrating an example of a hardware configuration of the controller unit of the image processing apparatus 103 illustrated in FIG.

  In FIG. 3, reference numeral 316 denotes a controller unit which is connected to a scanner unit 314 functioning as an image input device and a printer unit 312 functioning as an image output device, while being connected to a LAN (for example, the LAN (network 105) shown in FIG. 1). Or a public line (WAN) (for example, PSTN or ISDN) to input / output image data and device information.

  In the controller unit 316, reference numeral 301 denotes a CPU, which is a processor that controls the entire system. A RAM 302 is a system work memory for the CPU 301 to operate, and is also a program memory for recording a program and an image memory for temporarily recording image data.

  A ROM 303 stores a system boot program and various control programs. An external storage device (hard disk drive (HDD)) 304 stores various programs for controlling the system, image data, and the like.

  An operation unit interface (operation unit I / F) 307 is an interface unit with the operation unit (UI) 308 and outputs image data to be displayed on the operation unit 308 to the operation unit 308. The operation unit I / F 307 serves to transmit the information input by the system user from the operation unit 308 to the CPU 301. Note that the operation unit 308 includes a display unit having a touch panel, and various instructions can be given by a user pressing (touching with a finger or the like) a button displayed on the display unit.

  A network interface (Network I / F) 305 is connected to the network 105 (LAN) and inputs / outputs data. A modem (MODEM) 306 is connected to a public line and inputs / outputs data such as FAX transmission / reception.

  An external interface (external I / F) 318 is an I / F unit that accepts external inputs such as USB, IEEE 1394, printer port, RS-232C, and the like. A card reader 319 for reading an IC card is an external I / F unit. 318 is connected. The above devices are arranged on the system bus 309.

  Reference numeral 320 denotes an image bus interface (IMAGE BUS I / F), which is a bus bridge that connects the system bus 309 and an image bus 315 that transfers image data at high speed and converts the data structure.

  The image bus 315 is configured by a PCI bus or IEEE1394. The following devices are arranged on the image bus 315.

  A raster image processor (RIP) 310 develops vector data such as a PDL code into a bitmap image. A printer interface (printer I / F) 311 connects the printer unit 312 and the controller unit 316 and performs synchronous / asynchronous conversion of image data. A scanner interface (scanner I / F) 313 connects the scanner unit 314 and the controller unit 316 and performs synchronous / asynchronous conversion of image data.

  An image processing unit 317 performs correction, processing, and editing on input image data, and performs printer correction, resolution conversion, and the like on print output image data. In addition to this, the image processing unit 317 performs image data rotation and compression / decompression processing such as PDF, JPEG, and binary image data for JBIG, MMR, and MH for multi-valued image data.

  The scanner unit 314 illuminates an image on paper as a document and scans it with a CCD line sensor, thereby converting it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the apparatus user gives a reading start instruction from the operation unit 308, the CPU 301 gives an instruction to the scanner unit 314, and the feeder feeds the original paper one by one to read the original image. Perform the action.

  The printer unit 312 is a part that converts raster image data into an image on paper. The method is an electrophotographic method using a photosensitive drum or a photosensitive belt, and ink is ejected from a micro nozzle array directly on the paper. There is an inkjet method for printing an image, but any method may be used. The activation of the printing operation is started by an instruction from the CPU 301. The printer unit 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and has a paper cassette corresponding thereto.

  The operation unit 308 has an LCD display unit, and a touch panel sheet is pasted on the LCD. The operation unit 308 displays an operation screen of the system. When a displayed key is pressed, the position information is displayed on the operation unit I / F 307. To the CPU 301 via The operation unit 308 includes, for example, a start key, a stop key, an ID key, a reset key, and the like as various operation keys.

  Here, the start key of the operation unit 308 is used when starting a document image reading operation. At the center of the start key, there are two color LEDs, green and red, which indicate whether or not the start key can be used. Further, the stop key of the operation unit 308 functions to stop the operation in operation. The ID key of the operation unit 308 is used when inputting the user ID of the user. The reset key is used when initializing settings from the operation unit. The card reader 319 reads information stored in the IC card under the control of the CPU 301 and notifies the CPU 301 of the read information via the external I / F 318.

  With the configuration described above, the image processing apparatus 103 transmits image data read from the scanner unit 314 to a LAN (network), and print data received from the LAN (network) is printed out by the printer unit 312. Can do.

Further, the image data read from the scanner unit 314 can be fax-transmitted on the public line by the modem 306, and the image data received by FAX from the public line can be output by the printer unit 312.
<Description of FIG. 4>
FIG. 4 is a module configuration diagram illustrating software configurations of the server 102, the clients 101 and 104, and the image processing apparatus 103 illustrated in FIG.

  As shown in FIG. 4, the server 102 includes a recommended product determination program 401, a character recognition processing program 402, an overlay program 403, and a product data registration program 406.

  The clients 101 and 104 include a WEB page browsing program 404 for browsing a WEB page.

The image processing apparatus 103 includes an image reading control program 405 that reads image data from a paper document into an electronic document.
<Description of FIG. 5>
FIG. 5 is a functional configuration diagram showing a functional configuration of each module of the server 102 shown in FIG.

  As shown in FIG. 5, the recommended product determination program 401 includes functional units of a table reference unit 501, a determination processing unit 502, and a product sort processing unit 503.

  The character recognition processing program 402 includes an electronic document type determination unit 504 that recognizes a form ID from an electronic document and determines the type of the electronic document.

  The overlay program 403 includes an overlay unit 505 that overlays a case number (to be described later) on the form when the form is printed. Here, the form ID is information that can identify the type of a document (including an electronic document).

The product data registration program 406 includes a product data registration processing unit 506 and each function unit 507 of an alerting comment registration processing unit.
<Description of FIG. 6>
FIG. 6 is a flowchart showing an example of the first control process in the present invention.

  This corresponds to the basic flowchart in the system showing the present embodiment. Note that the processing of S601 to S613 in the figure is realized by the CPU 201 of the client 101 loading a program stored in the external memory 211 of the client 101 into the RAM 203 of the client 101 and executing it.

  First, in step S601, the CPU 201 of the client 101 executes menu display processing.

  In this menu display process, the CPU 201 of the client 101 performs an authentication process on the server 102 and then processes names such as a prior consent, a reception process, and a capture confirmation process from the server 102 (pre-consent 701, capture confirmation process). 702, information on the menu screen (FIG. 7) including the reception process 703) is acquired, and the screen is displayed on the display 210 of the client 101.

  Details of the menu display process in step S601 will be described later with reference to FIG. Here, the menu screen will be described.

  FIG. 7 is a schematic diagram illustrating an example of a menu screen in the present embodiment.

  In FIG. 7, a prior consent form output process 701, an import confirmation process 702, a reception process 703 belonging to the menu category, a product data registration process 705, and a warning comment registration process 706 belonging to the maintenance category are not shown by the user. It can be clicked (selected) with the cursor of the pointing device.

  For the courses 704 that can be handled, the CPU 201 of the server 102 refers to the clerk table (FIG. 9) for merchandise that can be handled by the user and products that are banned from handling based on the clerk ID (user ID) of the logged-in user. And displayed on the display 210 of the client.

  That is, in FIG. 9, “◯” indicating that handling (sales) is possible and “X” indicating that handling (sales) is prohibited are set for each product. For products for which “○” is set, “○” is displayed in the courses that can be handled in FIG. 7, and for products for which “×” is set, “x” is displayed for the courses that can be handled in FIG. The

  The maintenance is displayed if “O” (indicating that maintenance is possible) is set in the master maintenance item of FIG. 9 for the user, and is not displayed if “×” (indicating that maintenance is not possible) is set. . That is, the maintenance (705, 706) is displayed to be selectable only when “◯” is set in the master maintenance item of FIG. 9 for the user.

  The end button 707 is for closing the menu screen (FIG. 7) and performing logout processing to the server 102.

  Returning to the flowchart of FIG.

  The CPU 201 of the client 101 performs processing names in the menu on the menu screen (FIG. 7) (pre-consent form output processing 701, import confirmation processing 702, reception processing 703), processing names in maintenance (product data registration processing) 705, when it is detected that the alert comment registration process 706) is selected, the process corresponding to the selected process name is executed (steps S608, S609, S6010, S612, S613), and the process of this flowchart ends. .

  Specifically, when the CPU 201 of the client 101 detects that the prior consent form output process 701 has been selected (pressed) by the user (step S602), the CPU 201 executes the prior consent form output process (step S608). Details of the prior consent form output process in step S608 will be described later with reference to FIG.

  When the CPU 201 of the client 101 detects that the capture confirmation processing 702 has been selected (pressed) by the user (step S603), the CPU 201 executes the capture confirmation processing (step S609). Details of the capture confirmation process in step S609 will be described later with reference to FIG.

  Further, when the CPU 201 of the client 101 detects that the reception process 703 is selected (pressed) by the user (step S604), the CPU 201 executes the reception process (step S610). Details of the reception process in step S610 will be described later with reference to FIG.

  When the CPU 201 of the client 101 detects that the product data registration process 705 is selected (pressed) by the user (step S605), the CPU 201 executes the product data registration process (step S612). Details of the reception process in step S612 will be described later with reference to FIG.

  When the CPU 201 of the client 101 detects that the user has selected (pressed) the alert comment registration process 706, the CPU 201 executes the alert comment registration process (step S613). Details of step S613 will be described later with reference to FIG.

  In addition, when the CPU 201 of the client 101 detects that the user selects (presses) the end button 707 (step S607: Yes), the CPU 201 performs logout processing on the server 102 and ends the processing of this flowchart.

After executing the processing of step S608, step S609, step S610, step S612, and step S613, the processing proceeds to step S607. Then, the menu screen shown in FIG. 7 is displayed until the end button 707 is pressed (step S607: NO).
<Description of FIG. 8>
FIG. 8 is a flowchart showing an example of the second control process in the present invention.

  This corresponds to the menu display process shown in step S601 of FIG. Note that the processing of S801, S802, S806, and S807 in the figure is realized by the CPU 201 of the client 101 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  Also, the processing of S803 to S805 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  The CPU 201 of the client 101 starts a Web page browsing program (browser), acquires a page (login screen information) specified by the URL from the server 102, and displays a login screen (step S801).

  Then, the CPU 201 of the client 101 transmits the employee ID (user ID) and password input by the user to the server 102 (step S802).

  When the CPU 201 of the server 102 receives the employee ID and password (step S803), the CPU 201 searches the employee table (FIG. 9) stored in the external memory 211 to determine whether or not the received employee ID and password are registered. Execute user authentication processing.

  If the received employee ID and password are registered (stored) in the employee table, it is possible to log in. If the login fails, the processing of the flowcharts in FIGS. 8 and 6 is terminated.

  Here, the employee table will be described with reference to FIG.

  FIG. 9 is a diagram illustrating a staffing table according to the present embodiment.

  As shown in FIG. 9, the attendance table includes information (“investment trust”, “government bond”, “foreign currency”, “insurance” indicating the attendee ID (user ID), password, name, and (product) items that can be handled by the attendant. "), Master maintenance, and affiliated store (code (identification information) of the branch to which the employee (user) belongs).

In the employee table shown in FIG. 9, it is indicated that a product for which “◯” is registered can be handled, and a product for which “×” is registered cannot be handled.

  Further, if “◯” is registered in the master maintenance, the product data registration process 705 and the alert comment registration process 706 (hereinafter, these two processes are referred to as “master maintenance process”) can be performed, and “×” is registered. Indicates that the master maintenance process cannot be performed.

  In the example of the employee table shown in FIG. 9, if the employee ID is “02”, “investment trust”, “government bond”, and “foreign currency” products can be handled, and “insurance” products can be handled. This means that the master maintenance process cannot be performed. In addition, the code of the store to which the employee ID belongs is 215.

  Returning to the flowchart of FIG.

  In step S804, the CPU 201 of the server 102 acquires the authority information of the user from FIG. 9 if the employee ID and password received in step S803 are registered (stored) in the employee table. Here, the authority information of the user is “○” and “×” of “investment trust”, “government bond”, “foreign currency”, “insurance”, “master maintenance” registered in FIG. 9 corresponding to the user. Information.

  Information on the menu screen (FIG. 7) is generated from the authority information acquired here, and the generated menu screen information is transmitted to the client 101 (step S805).

  Next, the CPU 201 of the client receives information on the menu screen (FIG. 7) including authority information (step S806).

Next, the CPU 201 of the client displays the menu screen on the display 201 so as to accept the information on the menu screen received in step S806 (step S807), and shifts the processing to step S602.
<Description of FIG. 10>
FIG. 10 is an example of a product data registration screen displayed on the display of the client 101 in the product data registration process in step S612.

Information on the product data registration screen is generated by the product data registration program 406 of the server 102, and the product data registration screen (FIG. 10) is displayed on the display of the client 101 according to the information.
In the product data registration screen in FIG. 10, corresponding to the subject 1001, the product code 1002, and the product name 1003, the knowledge experience 1 to 5 can be handled 1004 to 1008, the investment purpose 1 to 5 can be handled 1009 to 1013, and the asset character 1 -5 can be registered for 1014 to 1018.

  The item 1001 can be selected from “investment trust”, “government bond”, “foreign currency”, and “insurance” by pull-down.

  As for the product code 1002, when a subject is selected by 1001, the CPU 201 of the server 102 refers to the product master table shown in FIG. 12, and the “last product code” is the product code used in the selected subject. “Value obtained by adding 1” is displayed as a product code.

For example, if the last product code number of the investment trust is 01021, it becomes 01022 when the next investment trust product is registered.
(In this example, investment trusts are registered in the 01000 series, government bonds 02000 series, foreign currency 03000 series, and insurance 04000 series.)
The product name 1003 is a text box, and an input of a product name can be accepted by the user.

  Knowledge experiences 1 to 5 each have a knowledge level for purchasing a product. For example, knowledge experience 2 represents a level of “experienced for the first time within one year”.

  Handling possibility (◯, Δ, ×) at the level of knowledge experience 1 to 5 on the product data registration screen (FIG. 10) is selected by pull-downs 1004 to 1008, respectively.

  “○” indicates that the product can be handled (recommended or sold), and “△” indicates that the product can be handled under the explanation of the precautions for the customer. .

  Note that the cautions are explained by displaying a warning comment 3301 described later on the screen (FIG. 33).

  “X” indicates that handling is prohibited (impossible). However, it is possible to sell by inputting a comment 3402 (FIG. 34) described later.

  For example, if the product set at 1001, 1002, and 1003 cannot be sold to a person with knowledge experience level 1 (knowledge experience 1), “x” is selected from the pull-down 1004.

  In addition, if the product set in 1001, 1002, and 1003 can be sold after explaining the precautions to the knowledge experience level 2 (knowledge experience 2), “△” is displayed from the pull-down 1005. Selected.

  In addition, if a product set in 1001, 1002, and 1003 can be sold to knowledge experience levels 3 to 5, “◯” is selected from the pull-down (1006, 1007, 1008). In this way, whether or not the product can be handled can be selected (set) according to the level (level) of the customer's knowledge and experience.

  Similarly, for investment purposes, investment objective levels (1 to 5) for handling products set in 1001, 1002, and 1003 are set, and whether or not each level can be handled (○, Δ, ×) Can be selected (set) by pull-downs 1009 to 1013.

  Similarly, with respect to the asset personality, the level of asset personality for handling the products set in 1001, 1002, and 1003 is set, and the availability (o, △, x) is pulled down for each level. It can be selected (set) by 1018.

  When the selection is made at 1001 to 1018 and the “Register” button 1019 is pressed, the selected data is registered (stored) in the form of a product master table (FIG. 12) and a product selection master table (FIG. 13).

  As described above, the product master table (FIG. 12) and the product (conditions selected in 1004 to 1018) indicating what kind of customers the products set in 1001, 1002, and 1003 can be handled for. It can be registered (stored) in the form of a selection master table (FIG. 13).

  FIG. 12 is a diagram illustrating an example of the product master table. The product master table includes “product code”, “product name”, and “(product) item”, and the values input in 1002, 1003, and 1001 in FIG. 10 are stored for each item. The

  FIG. 13 is a diagram illustrating an example of the product selection master table.

  The product selection master table includes “product code”, “knowledge experience code (level)”, “investment purpose code (level)”, “asset personality code (level)”, “knowledge experience display availability”, “investment objective display availability” ”,“ Asset property display availability ”, and“ Awareness comment ”. In the product code, the value input in 1002 is registered, and all the values set in 1004 to 1018 corresponding to the product code are registered.

  The “knowledge experience code (level)” indicates the level related to the customer's knowledge experience of 1004 to 1008, and the higher the value, the better the knowledge.

  The “investment purpose code (level)” indicates a level related to the investment purpose of the customers 1009 to 1013, and the higher the value, the higher the risk of purchase (higher profitability).

The “asset character code (level)” is a value for identifying the asset character of money invested by 1014 to 1018 customers. In addition, “◯”, “Δ”, and “×” selected in 1004 to 1008 are registered in “Knowledge Experience Display Availability”. In addition, “O”, “Δ”, and “X” selected in 1009 to 1013 are registered in “Investment purpose display availability”. “O”, “Δ”, and “X” selected in 1014 to 1018 are registered in “Asset Property Displayability”.
<Explanation of FIGS. 11 and 38>
FIG. 11 is an example of the alert comment registration screen displayed on the display of the client 101 in the alert comment registration process in step S613.

  Information on the attention comment registration screen is generated by the product data registration program 406 of the server 102, and the attention comment registration screen (FIG. 11) is displayed on the display of the client 101 according to the information.

  Attention comment registration screen (FIG. 11), subject 1101, product code 1102, product name 1103, knowledge experience 1-5 handling possibility 1105, investment purpose 1-5 handling possibility 1106, asset nature 1-5 handling This is a screen for registering a warning comment 1108 corresponding to the availability 1107.

  First, in order to select a product, when the product search button 1104 is pressed by the user, a product search screen (FIG. 38) is displayed to specify the product.

  38, the user selects one of “investment trust”, “government bond”, “foreign currency”, and “insurance” by pull-down, and if the product code is known, the user inputs the product code 4002 When a search button 4003 is pressed, No, a subject, a product code, and a product name are displayed in 4004 as search results.

  When the product name displayed in 4004 is pressed by the user, the screen transitions to FIG. 11 which is a call screen, and the product name, product code, and item pressed in FIG. 38 for the item 1101, the product code 1102, and the product name 1103. Is displayed.

Warning comments are registered when “△” is included in the availability of knowledge experiences 1-5, investment objectives 1-5, and asset characteristics 1-5 (however, “x” is not included) Is done. (A maximum of 125 patterns will be set for each product)
For example, the product registered on the product data registration screen (FIG. 10) includes a product called “Global High Income”, knowledge experience 2: “△”, investment purpose 4: “◯”, asset character 5: “○”. If it is, since “x” is not included and “Δ” is included, a warning comment can be registered.

  By selecting 1 to 5 for the knowledge experience 1105, “◯”, “Δ”, and “×” preset at the time of product data registration are displayed in 1105.

  Similarly, by selecting 1 to 5 for the investment purpose 1106, “◯”, “Δ”, and “×” set in advance at the time of product data registration are displayed in 1106.

  Similarly, by selecting 1 to 5 for the investment purpose 1107, “◯”, “Δ”, and “×” preset at the time of product data registration are displayed in 1107.

When the user inputs a comment in the alert comment 1108 and the registration button 1110 is pressed, the CPU 201 of the server 102 registers data in the alert comment item of the product selection master table (FIG. 13). At this time, the alerting comment input in 1108 is registered in a record corresponding to the product specified in 1101 to 1103 and the values selected in 1105, 1106, and 1107.
<Description of FIG. 14>
Next, the detailed process of step S608 executed when the prior consent form output process on the menu screen (FIG. 7) is pressed will be described with reference to FIG.

  FIG. 14 is a flowchart showing the detailed processing of step S608.

  The processing shown in S1401, S1402, and S1406 to S1412 in FIG. 14 is realized by the CPU 201 of the client 101 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  Also, the processing of S1403 to 1405 and S1413 to 1420 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 to the RAM 203 and executing it.

  Also, the processing of S1421 to S1424 in the figure is realized by the CPU 301 of the image processing apparatus 103 loading the program stored in the HDD 304 into the RAM 302 and executing it.

  When selling financial products, the bank staff must output a prior consent form (FIG. 17 to be described later) and must obtain a predetermined consent from the customer before selling the products. Hereinafter, the prior consent document output process will be described with reference to FIG.

  FIG. 14 is a flowchart showing an example of the third control process in the present invention, and corresponds to the prior consent form output process shown in step S608 of FIG.

  First, the CPU 201 of the client 101 acquires data (customer selection screen (FIG. 15)) for selecting a customer from the server 102, and displays the customer selection screen on the display 210 of the client 101 (step S1401).

  FIG. 15 is a diagram illustrating an example of a customer selection screen in the present embodiment.

  As shown in FIG. 15, a customer number (“20” in the example of FIG. 15) and a customer name (“Irikawa” in the example of FIG. 11) are displayed on the customer selection screen. Then, it is assumed that it is not displayed yet.

  When the CPU 201 of the client 101 recognizes that the “customer number” or “customer name” is input by the user and the search button 1501 is pressed, the input “customer number” or “customer name” is input to the server 102. ”Is sent to instruct the customer search (step S1402).

  When the CPU 201 of the server 102 receives “customer number” or “customer name” (customer search instruction) (step S1403), the CPU 201 of the server 102 stores the received “customer number” or “customer name” in the customer table (FIG. 16) stored in the external memory 211 of the server 102. It is searched whether “customer number” or “customer name” is registered (step S1404).

  FIG. 16 is a diagram illustrating an example of a customer table in the present embodiment.

  If the CPU 201 of the server 102 has registered in the customer table as a result of the search in step S1404, information such as the customer number, customer name, age, financial asset, etc. hit by the search from the customer table (customer information, etc.) ) Is acquired and transmitted to the client 101 (step S1405).

  The CPU 201 of the client 101 receives the customer information as a search result (step S1406), and displays the customer information on the customer selection screen (FIG. 15) (step S1407).

  Then, the CPU 201 of the client 101 waits until the confirmation button 1502 is pressed (step S1408). When the CPU 201 recognizes that the confirmation button 1502 is pressed (step S1408: Yes), the print confirmation screen shown in FIG. 39 is displayed. indicate.

  In the print confirmation screen (FIG. 39), a determination box for instructing “print agent form” is displayed. When printing a prior consent form for an agent, the user enters a determination in this determination box.

  Next, when the CPU 201 of the client 101 detects that the print (OK button) on the print confirmation screen (FIG. 39) displayed in step S1409 has been pressed (step S1409: Yes), the prior consent form for the agent Also, it is determined whether or not printing is instructed by the user (determined based on whether or not it is determined in the determination box) (step S1410). If it is determined that the user has instructed to print the agent's prior consent form (step S1410: YES), the server 102 is instructed to print the agent's prior consent form (step S1411). . Then, the server 102 is instructed to print the prior consent form of the contractor himself (step S1412).

  If it is detected that the cancel button on the print confirmation screen (FIG. 39) displayed in step S1409 has been pressed (step S1409: No), the CPU 201 of the client 101 returns the process to step S1401.

  In step S1410, if the OK button is pressed without being determined as a determination box on the screen of FIG. 39, the agent's prior consent form is not printed, and the process proceeds to S1412.

  If this transaction is a transaction by an agent, it is possible to output two sheets of a prior consent form for the agent and a prior consent form for the contractor by entering a determination.

  Next, when the CPU 201 of the server 102 receives an instruction to print a prior consent form from the client (step S1413), the CPU 201 assigns a case number for identifying the case and the customer (step S1414).

  Here, the case number is a number for identifying the case and the customer. For example, “021” is obtained by combining “customer number: 02” and “1” indicating the case.

  Then, the CPU 201 of the server 102 acquires the document data of the prior consent form from the external memory 211 of the server 102, and prints the case number assigned in step S1414 at a predetermined position of the document data. The document data is overlaid (step S1415). In the document data of the prior consent form, the form ID indicating the prior consent form is in a predetermined area.

  Then, the CPU 201 of the server 102 determines whether or not a printing instruction for the agent is also accepted in step S1413 (step S1416), and if it is for the agent, it is overlaid with the overlaid prior consent form for the agent. If the print instruction of the prior consent form for the contractor himself / herself is not transmitted to the image processing apparatus 103 (steps S1417 and S1418), the print instruction of only the prior consent form for the contractor who has been overlaid is sent to the image processing apparatus 103 Transmit (S1418).

  Thereafter, the CPU 201 of the server 102 generates a record in the matter table (FIG. 40), and in this record, the matter number assigned in step S1414, the employee ID of the logged-in user, and the customer customer who has instructed printing. “Reception” (preliminary consent output completed) is stored as the number, the date of printing in S1418 (acceptance date) (acquired and stored from the system date), and the status (status) (step S1419).

  Then, the CPU 201 of the server 102 updates the corresponding record in the prior consent matter table (FIG. 18) (step S1420).

  Specifically, the case number assigned in step S1414, the employee ID of the logged-in user and the customer number of the customer who issued the print instruction, the date and time when the print instruction was given in S1418 (date of prior consent form output), and status (state ) Is stored as a prior consent form. Further, the form ID included in the prior consent form instructed to be printed is also stored. When the agent's prior consent form is printed, the agent's customer number is stored in the “customer number” of FIG. 18 and the agent's customer is displayed in the “agent category” of the contractor's record. The number is stored.

  Note that the case table and the prior agreement case table are stored in the external memory 211 of the server 102.

  FIG. 40 is a diagram illustrating an example of a matter table in the present embodiment.

  As shown in FIG. 40, the items in the item table include “item number”, “customer number”, “passenger ID”, “acceptance date”, and “status”. Here, for “case number”, the data numbered and stored in step S1412 is stored in the case table, and for “customer number” and “passenger ID”, the data retrieved and stored in step S1404 is stored in the case table. Additional memory is stored. Here, with respect to the “passenger ID”, the data stored in step S805 is stored in the matter table.

  In “Status”, information indicating that a prior consent document has been output (“preliminary consent document has been output”) is registered (stored).

  Returning to the flowchart of FIG.

  When the CPU 201 of the image processing apparatus 103 receives a print instruction for the prior consent form from the server 102 (step S1421), the CPU 201 of the image processing apparatus 103 determines whether there is a print instruction for the agent based on the received print instruction (step S1422). If there is an agent's pre-consent form and the contractor's pre-consent form are printed (steps S1423 and S1424), and the agent's pre-consent form print instruction is not received The prior consent form is printed only for the contractor himself (step S1424).

FIG. 17 is a schematic diagram illustrating an example of a prior consent form in the present embodiment.
The layout is the same for both the agent and the person, and the case ID printed by the overlay is the same. However, the form ID is set differently for identifying the agent and the contractor. The value is printed.
<Description of FIG. 19>
FIG. 19 is a flowchart showing an example of the fourth control process according to the present invention. A form such as a prior consent form or an application form entered by a customer is digitized using the image processing apparatus 103 and entered into the form. This corresponds to the process of registering the registered data in the server 102.

  Note that the processing of S1901 and S1902 in the figure is realized by the CPU 301 of the image processing apparatus 103 executing an image reading control program stored in the ROM 303.

  Also, the processing of S1903 to S1914 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  First, the CPU 301 of the image processing apparatus 103 reads and digitizes the form set in the scanner 314 (step S1901), and the digitized form (also referred to as form read data or form capture data) is set in advance. 102 (provided in the external memory 211) (step S1902).

  When the CPU 201 of the server 102 acquires (receives) the form reading data (step S1903), the CPU 201 of the server 102 activates a character recognition program and performs character recognition processing on a predetermined area of the acquired form reading data. This is executed (step S1904), and the form ID and the case number are acquired from the form reading data (step S1905).

  Then, the CPU 201 of the server 102 determines the type of form corresponding to the acquired form ID (step S1906). Here, the type of the form corresponding to the form ID can be determined by referring to the correspondence table (stored in the external memory of the server) corresponding to the form ID and the form type.

  Further, the CPU 201 of the server 102 specifies a predetermined area for performing the character recognition process according to the determined form type (step S1907), executes the character recognition process for the specified predetermined area, Data (customer name (name), etc.) entered by the customer is acquired from the form reading data (step S1908). Here, the predetermined area represents an area including characters entered by the customer. This area is set by coordinates, and stored in advance in the external memory 211 of the server 102 for each form type (form ID). Accordingly, when the form type is specified from the form ID, the character recognition process can be executed for the area (coordinates) corresponding to the specified form, and the character entered by the customer is acquired as character data. be able to.

  Next, the CPU 201 of the server 102 specifies the customer name from the case number acquired in step S1905 (step S1909). Specifically, the customer number corresponding to the case number registered (stored) in the case table shown in FIG. 40 is specified, and the customer name corresponding to the specified customer number is referred to the customer table (FIG. 16). And get.

  Then, the CPU 201 of the server 102 determines whether or not an entry required item (an item that is required to be entered) is filled in the form (step S1910). In other words, the CPU 201 of the server 102 determines whether or not the required entry items of the form are filled in by determining whether or not data has been acquired from the area set in advance in step S1908. Here, the preset area (coordinates) is also set for each form type (stored in the external memory 211), and the CPU 201 of the server 102 executes the process of step S1910 by referring to this. be able to.

  When the CPU 201 of the server 102 determines that the required entry items are filled in (step S1910: Yes), it is determined whether or not the customer name acquired in step S1909 is the same as the customer name acquired in step S1908. Determination is made (step S1911).

  On the other hand, when the CPU 201 of the server 102 determines that the required entry items are not filled in (step S1910: No) or when it is determined in step S1911 that both customer names are different (step S1911: No). Sends an error notification to the client 101 (step S1914) and ends the process.

  If it is determined in step S1911 that both customer names are the same (step S1911: Yes), the CPU 201 of the server 102 determines whether the form type determined in step S1906 is a prior consent form (step S1912). . Here, the form ID and the form type can be identified from the form ID by referring to the associated information.

  When the CPU 201 of the server 102 determines that the form type determined in step S1906 is a prior consent form (step S1912: Yes), the item table stored in the external memory 211 of the server 102 (FIG. 40). Status (state) ("pre-agreement") and date and time (pre-agreement date) when the pre-agreement was registered are updated (registered) (step S1913). The form image data (form read data) received in step S1903 and the character recognition result (text data) recognized in step S1908 are linked to the employee ID, the case number, and the form ID, and the external memory of the server 102. It is assumed that it is stored in 211.

  If the CPU 201 of the server 102 determines in step S1912 that the read form data is not a prior consent form (step S1912: No), the “prior consent date” in the case table (FIG. 40) is not updated.

Then, the CPU 201 of the server 102 ends the process of this flowchart when the process of step S1913 ends <description of FIG. 20>.
Next, detailed processing in step S609 executed when the import confirmation processing 702 on the menu screen (FIG. 7) is pressed will be described with reference to FIG.

  FIG. 20 is a flowchart showing an example of the fourth control process in the present invention, and corresponds to the capture confirmation process shown in step S609 of FIG.

  This acquisition confirmation process is a process of referring to the text data of the OCR (character recognition process) result of the form registered in the server 102 by the acquisition process shown in FIG. 19 and the image data of the form.

  Note that the processing of S2001, S2005 to S2010, S2014, and S2015 in the figure is realized by the CPU 201 of the client 101 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  Also, the processing of S2002 to S2004 and S2011 to S2013 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  First, the CPU 201 of the client 101 transmits a clerk ID (user ID) input by the user and a request for captured matter information to the server 102 (step S2001).

  When the CPU 201 of the server 102 receives the request for the retrieved matter information and the employee ID (step S2002), the CPU 201 acquires the acquired information from the received employee ID (step S2003).

  Specifically, the CPU 201 of the server 102 acquires the case number, the registered form ID, and the status corresponding to the received employee ID from the prior agreement case table (FIG. 18) (step S2003).

  Then, the CPU 201 of the server 102 sends the case number acquired in step S2003 and the status corresponding to the case number to the client as information that has been captured (step S2004). The customer name corresponding to the customer number may be acquired from the customer table (FIG. 16) and sent to the client 101.

  When the CPU 201 of the client 101 receives the captured information (step S2005), the captured matter list screen (FIG. 41) is displayed on the display 210 of the client 101 based on the received captured information (FIG. 41) (step S2005). Step S2006).

  FIG. 41 is a diagram showing an example of a captured case list screen in the present embodiment.

  Then, the CPU 201 of the client 101 waits until a case number is selected on the captured case list screen by the user (step S2007: No), and detects that the case number is selected by the user (step S2007: Yes). ), A list of all forms corresponding to the selected case number is acquired from the server 102, and a form list screen (FIG. 42) is displayed from the list data of the form (step S2008).

  FIG. 42 is a diagram showing an example of a form list screen in the present embodiment.

  In step S2008, display is performed in such a manner that the read form and the unread form are known.

  For example, the CPU 201 of the client 101 acquires the form ID of the read form and the form ID of the unread form corresponding to the selected case number from the prior agreement case table (FIG. 18) of the server 102, respectively. Then, in order to distinguish from a form that has not been read, “OK” is displayed on the read form (reading column in FIG. 42). Further, by referring to the setting information (not shown) in which the form ID is associated with the form name, the form name can be acquired from the form ID and displayed (form name column in FIG. 42).

  Hereinafter, the description returns to the flowchart of FIG.

  Then, the CPU 201 of the client 101 waits until the form name is selected by the user (step S2009: No). When detecting that the form name is selected by the user (step S2009: Yes), the CPU 201 of the client 101 A request for the character recognition result (text data) and the image data of the selected form is transmitted (S2010). Specifically, the CPU 201 of the client 101 transmits a case number and a form ID corresponding to the selected form name to the server.

  When the CPU 201 of the server 102 receives the form ID and the case number (step S2011), it acquires a character recognition result (text data) specified from the case number and the form ID and image data of the form. (Step S2012).

  Then, the CPU 201 of the server 102 transmits the character recognition result (text data) and the form image data to the client (step S2013).

  Next, the CPU 201 of the client 101 receives the character recognition result (text data) and the form image data (step S2014), and based on the received character recognition result (text data) and the form image data. A reading confirmation screen (FIG. 21) is displayed on the display 210 of the client 101 (step S2015).

  FIG. 21 is a diagram showing an example of a reading confirmation screen in the present embodiment.

  For example, as shown in FIG. 21, on the reading confirmation screen, the character recognition result and the form image data are displayed on the left and right of the screen. By displaying such a reading confirmation screen, the user can determine whether or not the character has been correctly read by the character recognition process.

Then, the user confirms all the forms registered with the case number (case) selected in step S2007.
<Description of FIG. 22>
Next, detailed processing in step S610 executed when the reception processing 703 on the menu screen (FIG. 7) is pressed will be described with reference to FIG.

FIG. 22 is a flowchart showing an example of the fifth control process in the present invention, and corresponds to the reception process shown in step S610 of FIG.
This reception process is a process for displaying a recommended product list for a case for which a prior consent has been taken.

  This is a process of referring to the text data of the OCR (character recognition process) result of the form registered in the server 102 by the capture process shown in FIG. 19 and the image data of the form.

  Note that the processing of S2201, S2205 to S2208, S2215, and S2216 in the figure is realized by the CPU 201 of the client 101 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  Also, the processing of S2202 to S2204 and S2209 to S2214 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  First, the CPU 201 of the client 101 transmits a staff ID (user ID) input by the user and a request for captured matter information to the server 102 (step S2201).

  When the CPU 201 of the server 102 receives the request for the retrieved matter information and the clerk ID (step S2202), the CPU 201 acquires the retrieved information corresponding to the received clerk ID from the prior consent matter table (FIG. 18). (Step S2203). Here, the acquired information is the case number, customer name, and status (state) corresponding to the received employee ID.

  For these pieces of information, the matter table and the customer number are identified from the employee ID by referring to the matter table (FIG. 40), and the customer name can be identified from the customer number by referring to the customer table (FIG. 16). .

  Then, the CPU 201 of the server 102 sends the case number acquired in step S2203 and the status corresponding to the case number to the client as already acquired information (step S2204).

  Upon receiving the captured information (step S2205), the CPU 201 of the client 101 displays a captured item list screen (FIG. 41) on the display 210 of the client 101 based on the received captured information (step S2205). Step S2206).

  Then, the CPU 201 of the client 101 waits until a case number is selected on the captured case list screen by the user (step S2207: No), and detects that the case number is selected by the user (step S2207: Yes). ), The product selection screen information of the selected item is acquired from the server 102, and a request for a list screen of recommended products is transmitted to the server 102 together with the item number of the item selected by the user (step S2208).

When the CPU 201 of the server 102 receives the request for the item number and the recommended product list screen (step S2209), the age determination process (S2210), the recommended product sort process (S2211), and the individual / corporate determination process (S2212). Then, a loan presence / absence determination process (S2213) is performed, information on the recommended product list screen is created according to the list information generated in S2211 to S2213, and transmitted to the client. (S2214)
When receiving the recommended product list screen information from the server (S2215), the CPU 201 of the client 101 displays the recommended product list screen (FIG. 28) according to the recommended product list screen information (S2216).

  If screen expansion (+) (2801) is clicked on with a mouse, products other than recommended products (a product group including Δ and X) are also displayed on the screen (for example, FIG. 29).

After S2216, the client executes the process of S3001 shown in FIG.
<Description of FIG. 23>
Next, the detailed process of step S2210 is demonstrated using FIG.

  FIG. 23 is a flowchart showing an example of the sixth control process in the present invention, and corresponds to the age determination process shown in step S2210 of FIG.

  This age determination process determines whether the customer (contractor or agent) who has filled out the prior consent form is older than a predetermined age, and if it is not older than the predetermined age, the sale of financial products is not permitted. It is processing.

  Note that the processing of S2301 to S2307 in the figure is realized by the CPU 201 of the server 102 loading the program stored in the external memory 211 into the RAM 203 and executing it.

  First, the CPU 201 of the server 102 acquires a record that matches the item number selected in S2207 from the prior agreement item table (FIG. 18) (S2301).

  Here, there is a case where not the contractor himself but an agent of the contractor himself comes to the counter and sells financial products. When the agent comes to the window, he / she fills in the prior consent form for the contractor and the prior consent form for the agent, and the data of both prior consent forms are registered in the prior consent matter table.

  Next, the CPU 201 of the server 102 determines whether or not there are two records (one record in the case of the contractor) obtained from the prior consent form matter table (FIG. 18) in step S2301. If it is determined that there is a record, it is determined whether or not a value is registered in the “agent group” of the prior consent matter table (FIG. 18) (step S2302). Thereby, it can be determined whether or not the customer at the window is an agent.

  When there are two records acquired from the prior consent form matter table (FIG. 18) in step S2301, and a value is registered in the “agent category” of either record (step S2302: YES), the agent The date of birth of the record in which the value of the category is registered in “customer number” is acquired (step S2303). That is, the date of birth of the agent is obtained. Here, for example, in the case of case number = 1000001 in FIG. 18, since there is data of agent classification = 70, the date of birth of the record of case number = 1000001 and customer number = 70 (1962.8.8) Will get.

  On the other hand, if the CPU 201 of the server 102 determines that the number of records acquired in step S2301 is one, that is, if the customer coming to the window is the contractor himself (step S2302: NO), the process proceeds to step S2306. Migrate to

  The CPU 201 of the server 102 calculates the age of the current agent from the acquired date of birth and the server system date (the current date acquired from the OS), and whether the agent's age is less than 20 years old. It is determined whether or not (S2304).

  As a result of the determination, if it is determined that the user is younger than 20 years old, the client 101 is notified that “a“ purchase ”transaction cannot be performed” (S2305). Then, the error screen shown in FIG. 27 is displayed on the display of the client that has received the notification.

  As a result of the determination in S2304, the CPU 201 of the server 102 determines the date of birth of the record of the contractor himself (record different from the agent) from the prior consent form matter table (FIG. 18). Obtain (S2306).

  For example, if the case number = 1000001 shown in FIG. 18, the date of birth of the record with the customer number = 10 is acquired.

  Then, the CPU 201 of the server 102 calculates the current age from the acquired date of birth and the system date of the server, and determines whether the age is less than 20 (S2307).

  As a result of the determination, if it is determined that the user is younger than 20, the process proceeds to S2305, and an error screen (FIG. 27) is notified to the client.

  On the other hand, when the CPU 201 of the server 102 determines that it is not under 20 years old as a result of the determination, the CPU 201 performs a recommended product sorting process (FIG. 24).

When an error screen is notified to the client in step S2305, the recommended product sorting process (FIG. 24) is not executed, and the menu screen (FIG. 7) is displayed on the client.
<Description of FIG. 24>
FIG. 24 is a flowchart relating to recommended product sorting processing.

  The recommended product sorting process (FIG. 24) is the value of “knowledge experience”, “investment purpose”, “asset personality” entered in the prior consent form, and the value set for each product (set in FIG. 10) ) On the screen as a list of recommended products (FIG. 28).

  The CPU 201 of the server 102 first obtains a record from the prior consent form matter table (FIG. 18) using the matter number (case number) as a key in order to determine whether the selected matter is a case by an agent or a case by the principal. To do.

  Then, similarly to step S2302, it is determined whether or not the customer is an agent by determining whether or not there are two records acquired.

That is, since the CPU 201 of the server 102 has two acquisition records at the time of agent processing (when the customer who has come to the window is an agent) (single record in the case of principal reception), a value is assigned to the agent classification. It is determined whether there is a value in the agent category (S2401). If there is a value in the agent category, the knowledge experience code, the investment purpose code, and the asset personality code value of the record having the agent category value as the customer number are acquired. . (S2402)
Further, in the case of a single record at the time of principal processing (when the customer who came to the window is the contractor), the CPU 201 of the server 102 sets the values of the knowledge experience code, investment purpose code, and asset personality code of the record. Obtain (S2403).

  Then, the CPU 201 of the server 102 records each of the acquired knowledge experience code, investment purpose code, and asset personality code value, and the knowledge experience code, investment purpose code, and asset personality code value of the product selection master (FIG. 13). Is acquired for each product, and the product code, knowledge experience display enable / disable, investment purpose display enable / disable, asset property display enable / disable values of the acquired product selection master (FIG. 13) are stored in an array (list) (S2404).

  The CPU 201 of the server 102 sorts the products stored in the array according to the following procedure.

  First, the product code with the values of knowledge experience display availability, investment purpose display availability, asset personality display availability all “○”, knowledge experience display availability, investment purpose display availability, asset personality display availability, the product code in the list, (4 items of knowledge experience display availability, investment purpose display availability, asset property display availability) (S2405).

  The CPU 201 of the server 102 does not include “x” in the values of whether to display knowledge and experience, whether to display the investment purpose, and whether to display the asset personality, and even if one item contains “△” (sort in descending order from the smallest Δ) Is added to another array (list) (four items of product code, knowledge experience display enable / disable, investment purpose display enable / disable, and asset personality display enable / disable) (S2406).

The CPU 201 of the server 102 includes “×” in the values of whether to display knowledge / experience, whether to display the investment purpose, and whether to display the asset personality (sorting in descending order of “x” in descending order, and in descending order of Δ). Are added to another array (list) (4 items of product code, knowledge experience display availability, investment purpose display availability, asset property display availability) (S2407).
<Description of FIG. 25>
FIG. 25 is a flowchart regarding personal / corporate determination.

  The individual / corporate determination (FIG. 25) performed by the determination processing unit described in FIG. 5502 is a process for determining whether the contractor is an individual or a corporation. In order to make it impossible to sell merchandise (individual financial products), the values of whether to display knowledge and experience of the sorted array, whether to display investment purposes, and whether to display asset characteristics are changed to “-”.

  The CPU 201 of the server 102 obtains a record from the prior consent form matter table (FIG. 18) using the matter number as a key for the selected matter (S2501), and determines whether the corporation code item has a value. Thus, it is determined whether or not the customer who has come to the window is a corporation (S2502). Since the agent's personal / corporate attribute is the same attribute as the contractor himself / herself, it is only necessary to determine one record even if there are multiple records in the prior consent form matter table.

  Then, the CPU 201 of the server 102 needs to make “individual government bonds” unsaleable when there is a value in the corporate code item, so that the product master table has a 2-digit product code “02” in the product code. In (JGB), obtain the product code for the product name with the first three letters “individual”.

  If it is determined in step S2501 that it is a legal entity, it is the same as the product code acquired by determining as “individual bonds for individuals”, the knowledge experience display availability of the sorted array, the investment purpose display availability, the asset personality display availability The value is changed to “-” (step S2503), and the original data of the array (list) is deleted and added at the end.

If there is no value in the corporate code item, the CPU 201 of the server 102 ends the determination as it is.
<Description of FIG. 26>
FIG. 26 is a flowchart regarding the presence / absence of insurance at other stores and loan destination determination.

  Other Store Insurance / Loan Existence Determination (Fig. 26) is to determine whether there is insurance contract handling at other stores, and if there is insurance contract handling at other stores, handle "insurance products" at your own store This is a process for disabling, and if the loan is determined by determining whether or not the contractor has a loan, it is a process for disabling the handling of the “life insurance old life” product.

  The CPU 201 of the server 102 first acquires a record from the prior consent form matter table (FIG. 18) using the selected case number as a key. At agent processing, there are two records to be acquired (single record in the case of principal reception), so determine whether there is a value in the agent classification, and enter the customer number value of the record with a value in the agent classification get. In the case of a single record at the time of principal processing, the value of the customer number of the corresponding record is acquired (S2601).

  The CPU 201 of the server 102 acquires the value of the insurance dealer and the loan classification from the customer master table using the acquired customer number value as a key (S2602).

  And since the CPU 201 of the server 102 determines whether there is insurance handling at another store, the employee ID of the employee who is performing this operation is always held in the application. get.

  Then, the acquired value of the affiliated store is compared with the insurance handling store in the customer master table, and if it is different, it is necessary to disable handling of the insurance product.

  For this reason, the CPU 201 of the server 102 indicates whether or not the knowledge / experience display of an item that is a product (insurance) in which the first two digits of the product code are “03” in the sorted array, whether or not to display the investment purpose, and whether or not to display the asset character. Is changed to “-” (S2604), and the other store insurance / loan determination is completed.

  If the comparison result is the same (the store where the customer purchased the insurance is the same as the store where the employee belongs) (step S2603: NO), or if there is no value for the insurance handling store in the customer master table (step S2603) S2603: NO), loan presence / absence determination (S2605) is performed.

  The CPU 201 of the server 102 determines whether or not there is a value of the acquired loan classification in the loan presence / absence determination (S2605).

  If there is, the CPU 201 of the server 102 has a loan, so a product (insurance) in which the first two digits of the product code are “04” in the product master table, and the product name includes “lifetime old age”. In the sorted array, the values of knowledge experience display availability, investment purpose display availability, asset property display availability of the corresponding product code are changed to “-”. (S2606) Then, the process proceeds to step S2215.

  The CPU 201 of the client 101 receives a list screen from the server (S2215) and displays a recommended product list screen (S2216) (FIG. 28).

  If the development (+) on the screen (FIG. 28) is clicked on with a mouse, products other than recommended products (a product group including Δ and X) are also displayed on the screen (FIG. 29).

  Based on the above-mentioned sequence information (list), if the values of knowledge experience display availability, investment purpose display availability, asset personality display availability are all “○”, the recommended item on the recommendation list screen is marked with ☆, Product rows are displayed in blue, and if the mouse is clicked on the screen expansion (+), knowledge experience display on products other than recommended products (product groups including △ and X), investment purpose display For items that contain “x” in the value of availability / non-display of asset personality, recommended product list information is generated and transmitted to the client so that the row of the product can be displayed in gray (S2214).

In addition, as described above, products with values of “-” for knowledge experience display availability, investment purpose display availability, asset personality display availability may not be included in the information of the recommended product list screen to be generated. .
<Description of FIG. 30>
FIG. 30 is a flowchart showing an example of the sixth control process in the present invention, and the solicited product (2901) is selected and the next button (2902) is pressed via the recommended product list screen (FIG. 28 or FIG. 29). The Then, the client transmits a purchase product list screen information request to the server (S3001).

  Then, the server side receives a purchase product list screen information request (S3002).

Then, the CPU 201 of the server 102 determines whether there is a product that includes “-” in the values of the knowledge experience display availability, the investment purpose display availability, and the asset personality display availability of the selected solicitation product. If
・ Because it is a corporation, it cannot handle “Individual JGB” products. ・ Because it has insurance purchase history at other stores, it cannot handle “Insurance” products. Is displayed (if there are a plurality of them), information on the warning screen is generated and transmitted to the client side (S3004).

  The client side receives the warning screen information (S3005), and displays the warning screen (S3006) (FIG. 31).

  The CPU 201 of the server 102 determines whether there is a product that includes “-” in the values of the knowledge experience display availability, the investment purpose display availability, and the asset personality display availability of the selected solicitation product. If not, the information on the purchased product list screen is transmitted to the client (S3007).

  The client receives information on the purchased product list screen (S3008), and displays the purchased product list screen (FIG. 32) according to the information (S3009).

  Then, the client selects the product input link button (3201) of the product by the user, and transmits the information (including whether or not to display the knowledge and experience of the product, whether or not to display the investment purpose, whether or not to display the asset character) to the server (S3010). .

  Then, it is received on the server side (S3011), and it is determined whether or not the selected product includes “△” (× is none) (S3012), and if applicable (when Δ is included), alerts Information on the alert screen (FIG. 33) with the comment added to the purchase merchandise amount input screen (3301) is transmitted to the client. (S3013) Here, a comment corresponding to the product is added and transmitted. The client receives the information (S3014) and displays FIG. 33 (S3015).

  On the other hand, if it is determined in S3012 that Δ is not included, the CPU 201 of the server 102 determines whether “X” is included in the similarly selected product (S3016), and if it is included, A confirmation screen (FIG. 34) as to whether or not to sell the product is transmitted to the client (S3017).

  Then, the client receives the confirmation screen, and displays the purchased product amount input screen (with sales reason input) (FIG. 34) (S3020).

  Then, the client receives a selection as to whether or not to sell the product. (S3021) If the product is not sold, the process returns to S3007.

  When selling, the user inputs the reason for sale (3402). Subsequently, an amount (3401) is input, and when the registration button 3404, the registration button in FIG. 33 or the registration button in FIG. 35 is pressed, the input data is transmitted to be registered in the server (S3023).

  Then, when the server receives the input data from the client, the server determines whether or not the amounts of all the selected products have been input (S3025). And when it determines with the money amount of all the goods not being input, it returns to step S3007. On the other hand, if it is determined that all product amounts have been input, the process proceeds to S3026.

  If it is determined in step S3016 that “x” is not included, an amount input screen (FIG. 35) is transmitted to the client (S3018). The screen transmitted here is received and displayed by the client in step S3014.

  In step S3026, the server acquires the customer's already invested amount and the total amount of financial assets from the already invested amount and financial assets corresponding to the customer in the customer table.

  In step S3027, the server calculates (current investment amount + existing investment amount) / total financial assets, and determines whether the value is 100% or less.

  If the calculated value exceeds 100%, that is, if the current investment amount is larger than the asset (S3027: YES), an error screen (FIG. 36) indicating that the limit amount has been exceeded is transmitted to the client (S3028). . When the client receives the error screen, the client displays the error screen (S3030).

  If the product is not sold, the process returns to S3007 by pressing the return button.

  When selling a product, if the YES check box 3601 on the screen (FIG. 36) is clicked, the product sales reason input screen (FIG. 37) is displayed, the reason for sales (3701) is input, and the application button 3702 is pressed. Then, it sends it to the server to make an approval request for the sale of the product to the superior.

  Then, when receiving the approval request, the server transmits an approval request for selling the product to the superior corresponding to the user.

  When the request (sales request) is approved by the superior, the status is changed and sales are permitted.

  When the application button is pressed and there are courses that cannot be handled by the clerk, an error message “Cannot apply because there are courses that cannot be handled” may be displayed on the screen.

  As described above, financial products that can be introduced can be determined according to customer attributes.

  Although one embodiment of the present invention has been described in detail above, the present invention can take an embodiment as, for example, a system, an apparatus, a method, a program, or a storage medium. You may apply to the system comprised from an apparatus.

  Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, this can also be achieved by reading and executing the program code stored in.

  In this case, the computer-readable program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention. Will do.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (basic system or operating system) running on the computer based on the instruction of the program code. Needless to say, a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion board or function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

It is a figure which shows the structural example of the system which concerns on this embodiment. It is a figure which shows the hardware constitutions of the client 101, the client 104, and the server 102 which were shown in FIG. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a controller unit of the image processing apparatus 103 illustrated in FIG. 1. FIG. 2 is a module configuration diagram illustrating software configurations of a server 102, clients 101 and 104, and an image processing apparatus 103 illustrated in FIG. FIG. 5 is a functional configuration diagram illustrating a functional configuration of each module of the server 102 illustrated in FIG. 4. It is a flowchart which shows an example of the 1st control processing in this invention. It is a schematic diagram which shows an example of the menu screen in this embodiment. It is a flowchart which shows an example of the 2nd control processing in this invention. It is a figure which shows an example of the employee table in this embodiment. It is a figure which shows an example of the goods data registration screen in this embodiment. It is a figure which shows an example of the goods data registration screen in this embodiment. It is a figure which shows an example of the goods master table in this embodiment. It is a figure which shows an example of a table about the goods selection master table in this embodiment. It is a flowchart which shows the detailed process of step S608 in this embodiment. It is a figure which shows an example of the customer selection screen in this embodiment. It is a figure which shows an example of the customer table in this embodiment. It is a schematic diagram which shows an example of the prior consent document in this embodiment. It is a figure which shows an example of the prior consent matter table in this embodiment. It is a flowchart which shows an example of the 4th control processing in this invention. It is a flowchart which shows the detailed process of step S609. It is a figure which shows an example of the reading confirmation screen in this embodiment. It is a flowchart which shows the detailed process of step S610. It is a flowchart which shows an example of the 6th control processing in this invention. It is a flowchart which shows the detailed process of S2211. It is a flowchart which shows the detailed process of S2212. It is a flowchart which shows the detailed process of S2213. It is an example of an error screen displayed on a client's display by S2305. It is a figure which shows an example of the recommended goods list screen (non-development) in this embodiment. It is a figure which shows an example of the recommended product list screen (development) in this embodiment. It is a flowchart which shows an example of the 6th control processing in this invention. It is a figure which shows an example of the warning screen (product selection) in this embodiment. It is a figure which shows an example of the purchase merchandise list screen in this embodiment. It is a figure which shows an example of the alerting screen in this embodiment. It is a figure which shows an example of the sales reason input screen in this embodiment. It is a figure which shows an example of the purchased goods amount input screen in this embodiment. It is a figure which shows an example of the purchase merchandise list (with a financial asset determination error) screen in this embodiment. It is a figure which shows an example of the merchandise sales reason input screen in this embodiment. It is a figure which shows an example of the goods search screen in this embodiment. It is a figure which shows an example of the printing confirmation screen in this embodiment. It is a figure which shows an example of the case table in this embodiment. It is a figure which shows an example of the taken-in case list screen in this embodiment. It is a figure which shows an example of the form list in this embodiment.

Explanation of symbols

101 Client 102 Server 103 Image Processing Device 104 Client 105 Network

Claims (6)

Attribute storage means for storing attribute information of the financial product indicating the degree of at least one of knowledge about the financial product and purchase experience of the financial product, which is necessary for the customer to sell the financial product;
An input means for inputting the customer's attribute information indicating knowledge about the financial product possessed by the customer or the degree of purchase experience of the financial product;
A determination unit that determines a financial product to be introduced to the customer from the attribute information of the customer input by the input unit and the attribute information of the financial product stored in the attribute storage unit;
Display means for displaying a list of financial products determined by the determining means;
An information processing apparatus comprising: Authority storage means for storing authority information in which financial products that can be introduced to customers by the user are set;
Further comprising
The said determination means determines the financial product introduce | transduced to the said customer from the financial products which can be introduced to the customer set in the authority information memorize | stored in the said authority memory | storage means. Information processing device. The input means further inputs identification information for identifying whether the customer is a corporation or an individual,
Determining means for determining whether the customer is a legal entity based on the identification information input by the input means;
If the determination means determines that the customer is a legal entity, the attribute information of the personal financial product stored in the attribute storage means is stored so that the determination means does not determine the personal financial product. An attribute changing means to be changed;
The information processing apparatus according to claim 1, further comprising: Loan storage means for storing the user's loan destination;
A loan destination determination means for determining whether the customer of the attribute information input by the input means is a loan destination stored in the loan destination storage means;
Further comprising
The attribute changing means determines the financial information by the determining means when the loan destination determining means determines that the customer of the attribute information input by the input means is the loan destination stored in the loan destination storage means. 4. The information processing apparatus according to claim 3, wherein the attribute information of the old-age insurance stored in the attribute storage means is changed so that the old-age insurance as a product is not determined. Attribute storage for storing attribute information of the financial product indicating the degree of at least one of knowledge about the financial product and purchase experience of the financial product that the attribute storage means needs for the customer to sell the financial product Process,
An input step in which the input means inputs the customer's attribute information indicating knowledge about the financial product possessed by the customer or the degree of purchase experience of the financial product;
The determination unit determines a financial product to be introduced to the customer from the customer attribute information input in the input step and the financial product attribute information stored in the attribute storage step;
A display step for displaying a list of financial products determined in the determination step;
An information processing method in an information processing apparatus comprising: Information processing device
Attribute storage means for storing attribute information of the financial product indicating the degree of at least one of knowledge about the financial product and purchase experience of the financial product, which is necessary for the customer to sell the financial product;
An input means for inputting the customer's attribute information indicating knowledge about the financial product possessed by the customer or the degree of purchase experience of the financial product;
A determination unit that determines a financial product to be introduced to the customer from the attribute information of the customer input by the input unit and the attribute information of the financial product stored in the attribute storage unit;
Display means for displaying a list of financial products determined by the determining means;
A program characterized by functioning as

Images