JP2004118832A - Method and system for processing information for allocation of business results of insurance or sale commission - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allocate a sales commission to the sales persons concerned of an insurance, with a proper mode. <P>SOLUTION: When a data of indicating an insurance contract collaborated by a sales partner (SP) and an agency is included in an insurance contract data, a step is executed to determine an allocation ratio of the sales commission or business results for the SP and the agency at least based on attribute of the insurance contract. Alternatively, when the data of indicating the insurance contract collaborated by the sales partner (SP) and the agency is included in the insurance contract data, a step is executed to specify a contribution condition as to conclusion of the insurance contract at least in one of the SP and the agency, and a step is also executed to determine an allocation ratio of the sales commission or business results for the SP and the agency at least based on a data related to the contribution condition. <P>COPYRIGHT: (C)2004,JPO

Description

(4) The present invention relates to information processing technology relating to calculation and distribution of performance or sales commission in insurance sales. Note that, in the present application, the operating result or the result refers to a performance evaluation value for insurance sales. As the achievement, for example, a one-time insurance premium for an insurance contract, an annual insurance premium, an insurance amount (for example, a compensation amount), or an amount obtained by multiplying them by a predetermined coefficient is used.

In recent years, insurance sales patterns have become diversified. For example, in addition to the direct sales method using the Internet or the like, sales of agents or direct sales through referrals from the insurance premium calculation site established on the Internet, as well as sales of agents (including intermediaries, intermediaries, etc.) and insurance A form of tie-up with a sales representative of a company (hereinafter, referred to as SP (meaning sales partner) in the present application) has also arisen. In addition, there are cases where agencies and SPs are affiliated.

When multiple parties are involved in the sale of insurance in this way, it is necessary to fairly and appropriately distribute the performance and sales commissions in the insurance sales to those persons (also referred to as sales participants). . In addition, it is necessary to consider the above alliance in managing the performance of each department of the insurance company to which the sales involvement belongs (for example, the sales office to which the agency or the SP belongs or the department in charge of managing the SP). .

Accordingly, it is an object of the present invention to provide an information processing technique for implementing an achievement or distribution of a sales commission to insurance sales participants in an appropriate manner.

Another object of the present invention is to provide an information processing technique for appropriately managing the performance of insurance sales when a plurality of persons are involved in insurance sales.

An information processing method according to a first aspect of the present invention includes a step of acquiring insurance contract data and storing the insurance contract data in a storage device, and a step of acquiring the insurance contract data with a first sales person (for example, SP). When data indicating that the insurance contract is an insurance contract in cooperation with a sales associate (for example, an agency) is included, the first sales associate and the second sales associate may be based on at least the attributes of the insurance contract. And determining a distribution ratio of a result or a sales commission to the storage device, and storing data on the distribution ratio in a storage device.

For example, the allocation ratio is determined based on information on insurance policyholders, which are attributes of insurance contracts (for example, information on the classification of corporations and individuals, insurance performance, and the position of insurance policyholders). This is because, for example, the size of an insurance contract often differs greatly between a corporation and an individual.

An information processing method according to a second aspect of the present invention includes a step of acquiring insurance contract data and storing the insurance contract data in a storage device, wherein the acquired insurance contract data includes a first sales participant and a second sales participant. Identifies the contribution status of at least one of the first sales entrant and / or the second sales entrant to the conclusion of the insurance contract, if the data includes data indicating that the contract is an insurance contract based on the alliance. Storing the data on the contribution status in the storage device, and determining the distribution ratio of the result or the sales commission to the first and second sales participants based on at least the data on the contribution status, A distribution ratio determining step of storing data on the distribution ratio in a storage device.

For example, depending on the contribution status of the insurance contract conclusion, such as who took the first appointment, the agent accompanied the first time, or the insurance design, the time and contribution to the SP or the agent greatly differed That's why.

Further, in the above-mentioned allocation ratio determining step, the allocation ratio of the performance or sales commission to the first and second sales participants is determined based on the data on the attributes and the contribution status of the insurance contract. Configuration may be used. This is a combination of the first embodiment and the second embodiment.

Further, in the first and second information processing methods of the present invention, the method further includes a step of acquiring charge setting data on future management of an insurance contract and storing the same in a storage device. Further, a configuration may be employed in which the results of sales or the distribution ratio of sales commissions to the first sales participant and the second sales participant are determined based on the setting data on the future management of the insurance contract. . For example, it is for distributing a large number of achievements or sales commissions to persons involved in maintenance after concluding an insurance contract, such as responding to an accident.

Further, in the above-mentioned distribution ratio determining step, the distribution ratio of the result or the sales commission to the first sales participants and the second sales participants is further determined based on the attributes of the first sales participants. Such a configuration may be used. For example, based on the qualification of SPs, it is to allocate more to excellent SPs.

Further, when the allocation ratio determining step described above receives information indicating consent from the terminal of the first sales entrant and the terminal of the second sales entrant regarding the allocation ratio, the allocation ratio for which consent has been obtained is obtained. May be configured to include a step of registering data on the insurance contract in accordance with the insurance contract. This is to use the distribution ratio with the consent of both parties.

Further, in the first and second aspects of the present invention, when information indicating consent is received from the terminal of the first sales entrant and the terminal of the second sales entrant regarding the distribution ratio, the insurance contract data is used. It may be configured to further include a step of executing the accounting process.

Further, the above-described distribution ratio determining step includes a step of receiving information for determining a distribution ratio from at least one of the terminal of the first sales entrant and the terminal of the second sales entrant. And transmitting a notification requesting consent to the distribution ratio to at least one of the terminal of the first sales entrant and the terminal of the second sales entrant. For example, when the information for determining the distribution ratio is received from the terminal of the first sales entrant, a notification requesting consent for the distribution ratio is transmitted to the terminal of the second sales entrant.

Further, in the first and second aspects of the present invention, the sales commission of the first sales participant is based on information including at least the distribution ratio of the first sales participant and the attribute of the first sales participant. And calculating the sales commission of the second sales participant based on information including at least the sales percentage of the second sales participant and the attributes of the second sales participant. Configuration may be used. For example, a method of deciding one sales commission amount and allocating it can be considered. However, not only this, but also giving the sales commission for the first sales entrant to the first sales entrant based on the distribution ratio. Then, similarly, a mode is adopted in which the sales commission for the second sales entrant is given to the second sales entrant based on the distribution ratio. However, the sales commission for the first sales entrant is granted to the first sales entrant taking into account the results determined based on the distribution ratio, and the sales commission for the second sales entrant is assigned to the distribution quota. May be given to the second sales-related participant in consideration of the result determined on the basis of.

Further, in the first and second aspects of the present invention, the first sales participant and the second sales participant are listed based on the attributes of the insurance contract group made in relation to the second sales participant. It may be configured to further include a step of changing the distribution ratio of the achievements. For example, this corresponds to a case where the allocation ratio to agents involved in a group of insurance contracts having a high accident rate or churn rate is changed to be low.

Further, in the first and second aspects of the present invention, the method further includes a step of adding the result of the first sales participant to the result of the department related to the first sales participant according to the distribution ratio. Such a configuration may be used. As a result, it is possible to appropriately manage the business results.

Further, in the first and second aspects of the present invention, when a contact is received from an insurance policyholder, the contact information is set based on data on the status of contribution to the conclusion of the insurance contract or on data set in charge of future management of the insurance contract. May be further included. This is because if an accident response is explicitly set, the person is contacted, and if not, a person who has a high degree of contribution and is deeply involved in the insurance contract.

Further, in the first and second aspects of the present invention, the result of the first sales participant and the second sales participant are calculated based on at least the distribution ratio, and the data of the result is stored in the storage device. It may be configured to further include a result calculation step.

It is also possible to create a program for causing a computer to execute the information processing method according to the present invention, and the program includes, for example, a storage medium such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk. Alternatively, it is stored in a storage device. Also, it may be distributed via a network. The data being processed is temporarily stored in the memory of the computer.

As described above, according to the present invention, distribution of sales commissions and achievements to insurance sales participants can be implemented in an appropriate manner.

In addition, when multiple persons are involved in insurance sales, it is possible to appropriately manage business results.

FIG. 1 shows a schematic diagram of a system according to an embodiment of the present invention. For example, a network operated by an agent is provided on a network 1 that is a VPN (Virtual Private Network) via a LAN (Local Area Network) of the insurance company, the Internet, or the like, a dedicated line, or another communication line that can ensure security. One or more agent terminals 7 that are personal computers, one or more SP terminals 3 that are personal computers operated by an SP, for example, and one or more agent terminals 7 operated by a call center operator managed and operated by an insurance company. The call center terminal 9 and the server 5 that performs the main processing in the present embodiment are connected.

The server 5 includes a contract DB 51 for storing insurance contract data, a result DB 53 for storing result data for each business unit, agency, and SP, and sales to be paid to the agency and SP. It manages a fee management DB 55 for storing data on fees, and a parameter DB 57 for storing various parameters used in calculating the distribution ratio of sales results, sales fees, and the like. Although not shown, the server 5 includes a control unit, a communication unit, and a database management unit. The database management unit manages extraction of data from databases such as the contract DB 51, the achievement DB 53, the commission management DB 55, and the parameter DB 57, and recording of data in the database. The communication unit performs communication processing with the agent terminal 7, the SP terminal 3, the call center terminal 9, and the like. The control unit controls processes of the communication unit, the database management unit, and the like, and also controls a series of processes related to distribution in the present system. Here, though not shown, it is also assumed that a sales participant database that records attribute data such as the location of sales participants (such as agents and SPs) is also connected to the server 5.

FIG. 2 shows an example of a contract data table stored in the contract DB 51. In the example of the contract data table shown in FIG. 2, a column 201 of the application form number (or security number), a column 202 of the contractor name, a column 203 of the monthly premium (or annual premium), A column 204 of the store code, a column 205 of the SP code in charge, a column 206 of a secretary code of a secretary who performs post-contract management work, and a column 207 of a maintainer code performing maintenance work are included. Although not shown, various attribute data relating to the contract is registered in the contract data table. Although not shown, a column for recording a type code for recognizing a type of the contractor such as whether the contractor is a corporation or an individual is provided in correspondence with the information in the column 202 of the contractor name. I have. For example, data such as a corporation when the contractor type is 0 and an individual when the contractor type is 1 is stored in the contract DB 51. With this contract data table, it is possible to acquire data such as the attributes of the insurance contract, the attributes of the contractor, the agency in charge, the SP in charge, the secretary, and the maintenance, using the application form number as a key.

FIG. 3 shows an example of the distribution ratio data table stored in the contract DB 51. The example of the distribution ratio data table shown in FIG. 3 includes a column 211 of the application form number (or security number), a column 212 of the SP distribution ratio, and a column 213 of the agency distribution ratio. In this distribution ratio data table, data on distribution ratios of sales commissions with the consent of both the SP and the agency is registered for each insurance contract (for each application form number).

(4) The contract DB 51 may further register data serving as the basis of the distribution ratio data registered in the distribution ratio data table. In the present embodiment, it is assumed that an allocation ratio determination element data table for registering allocation ratio determination elements in contract DB 51 is also registered. FIG. 4 shows an example of the distribution ratio determining element data table for the application form number A000001. In the example of FIG. 4, the application form number, classification of corporation / individual, number of visits, visit place, agency appointment, agency first visit, customer needs grasp, security diagnosis, insurance design, presentation, closing, application, diagnosis Includes arrangements, accounting, secretary and conservation. These include, for example, insurance contract attribute data (application form number, corporate / individual, visit location), contribution status data for insurance contract conclusion (number of visits, agency appointment execution, agency first visit, customer needs Comprehension, securities diagnosis, insurance design, presentation, closing, application, diagnosis arrangement, accounting), maintenance setting data after concluding an insurance contract (secretary, maintenance), etc. As described above, regarding the distinction between a corporation and an individual, 0 represents a corporation and 1 represents an individual. As for the number of visits, 0 represents up to three visits, and 1 represents four or more visits. The number is an example. Regarding the visiting place, 0 represents the distance of 5 km or less between the SP sales base and the customer, and 1 represents the distance exceeding 5 km. 5 km is an example. Regarding the execution of the agency appointment, 1 indicates that the agent has performed the appointment, and 0 indicates that the agent has not performed the appointment. Regarding the agent's first visit, the case where the agent accompanied the first visit is represented by 1, and the case where the agent did not accompany is represented by 0. In the same manner, the case where the agent performs or takes charge is represented by 1, and the case where the agent does not carry out or takes charge is represented by 0. Among these data, the data such as the application form number and the type of corporation / individual are read from the contract DB 51 by using the application form number as a key, and the server 5 records the data corresponding to the distribution ratio determination element data table. I do. In addition, the database management unit determines the distribution ratio for each combination of sales representatives (simply referred to as “participants”) such as the agency code 204 and the SP code 205 included in the contract DB 51 (which may be each agency or each SP). The initial data of the element data table is generated and stored in the contract DB 51. For example, in the case of a combination of a certain agency and SP, initial values are set for the contribution status data for concluding an insurance contract and the maintenance setting data after concluding an insurance contract, excluding the attribute data of the insurance contract. For example, initial values are set in advance for items other than the items of “individual / corporate” and “visit place” in FIG. This initial value may be set based on an input from the agency terminal 7, the SP terminal 3, or the call center terminal 9, or the server 5 sets a uniform initial value common to all sales participants. You may make it. The database management unit stores the distribution ratio determination element data table in which the initial value is set in the contract DB 51. As for the attribute data of the insurance contract, the database management unit uses predetermined data from the contract data table of FIG. 2 (for example, identification data indicating whether the contractor is a corporation or an individual, or the distance between the contractor address and the agency address). And the like) are extracted, and the data is recorded in the allocation ratio determination element data table. Here, for the visit place, the database management unit extracts the address of the contractor recorded in the contract data table and the location of the sales participant recorded in the sales participant database relating to the attributes of the sales participant (not shown). The control unit calculates the distance between the contractor's address and the sales associate (for example, calculates the distance from the latitude and longitude information indicating the location of both parties), and based on the data, the database management unit Determine the data to be set. Thus, the database management unit sets all the initial values of the allocation ratio determination element data table.

FIG. 5 shows an example of the result data table stored in the result DB 53. In the example of the result data table shown in FIG. 5, a column 501 of business units including sales offices, sales departments, agents, SPs, and the like, a column 502 of results of the current month (for example, August 2002), And a column 503 of the results (for example, 2002). The amount registered in this table is, for example, a one-time insurance premium for an insurance contract, an annual insurance premium, an insurance amount (for example, a compensation amount), or an amount obtained by multiplying them by a predetermined coefficient. Further, the data included in this table is merely an example, and data for a longer period may be accumulated.

FIG. 6 shows an example of the result data table stored in the result DB 53 for each application form number. In the result data table for each application form number shown in FIG. 6, a column 601 of the application form number, a column 602 of the total result, a column 603 of the ID of the first participant, and a first participant Column 604 of the first participant, column 605 of the result of the first participant, column 606 of the ID of the second participant, column 607 of the distribution ratio of the second participant, and second participation Column 608 of the person's achievements; . . Is included. By multiplying the amount of the result of the insurance contract corresponding to each application form number by the distribution ratio of each participant, the result of each of the agency and the SP is determined, and is stored in the result DB 53. That is, the amount of the performance related to the insurance contract (for example, a one-time insurance premium of the insurance contract, an annual insurance premium, an insurance amount (for example, a compensation amount), or an amount obtained by multiplying them by a predetermined coefficient, etc.) is added to the agency The amount obtained by multiplying the distribution ratio of each SP is registered as the achievement of each participant. In FIG. 6, for the contract with the application number A000001, the total achievement is 1,000,000 yen, which is 35% of the agent (agent code D00001) of 350,000 yen, and the SP (SP code) SP001), 65% of 655,000 yen was allocated. Note that, in the performance data table for each application form number, not only a contract in which the SP and the agency cooperate, but also performance data on insurance sold by the SP alone or the agency alone are registered.

FIGS. 7A and 7B show distribution ratio setting tables stored in the parameter DB 57. FIG. FIG. 7A shows an example of a distribution ratio setting table based on the attributes of the insurance contract (particularly, the attributes of the insurance contractor), the contribution status to the conclusion of the insurance contract, and the management setting after the conclusion of the insurance contract. In the example of FIG. 7A, the basic allocation ratio when the insurance policyholder is a corporation or an individual, and the adjusted allocation ratio when the number of visits is 3 or less or 4 or more for each of the SP and the agent. , Adjustment distribution ratio when the visiting place is within 5 km or more than 5 km from the SP sales base, Adjustment distribution ratio when the agent makes or does not make the first appointment, The agent accompanies the first customer Adjusted allocation ratio in the case where the agent did or did not do it, adjusted allocation ratio in the case where the agency did or did not understand the needs, adjusted allocation ratio in the case where the agent performed or did not perform the securities diagnosis, Adjusted allocation ratio when the agent did or did not design the insurance, adjusted allocation ratio when the agent did or did not make the insurance presentation, Closin Adjustment distribution ratio when the agent performs or does not perform, the adjustment allocation ratio when the agency performs or does not perform the application processing, and when the agent performs or does not arrange the health checkup Adjusted allocation ratio, Adjusted allocation ratio when the agent performs or does not execute the accounting process, Agent is the secretary (Representative of insurance contract handling, responsible for processing in the event that the contractor has an accident ) Or the secretary, and the adjusted distribution ratio when the agency performs or does not perform maintenance (procedure for changing the contract contents). Note that these initial settings are also registered, and the meanings of the values in the column of initial values are the same as in the case of the distribution ratio determination element data table shown in FIG.

FIG. 7B shows an example of a distribution ratio setting table based on SP attributes. In the example of FIG. 7B, data of the adjusted distribution ratio of the agent and the SP when the SP is at the A level, when the SP is at the B level, and when the SP is at the C level, are included. How to set the level and the number of levels are arbitrary. In addition, data of the adjustment distribution ratio may be included.

7A and 7B are provided for each agency or SP. Although not shown in FIG. 7, the agency code and / or the SP code for specifying the agency and / or the SP are also recorded.

FIG. 8 shows an example of a sales commission calculation table of the agency stored in the parameter DB 57. The sales commission calculation table shown in FIG. 8 includes a column 701 of insurance types, a column 702 of payment periods, and a column 703 of sales commission rates for each agency type classified into special grade, advanced, and ordinary. Have been. The number of ranks of the agency, the setting factor of the commission rate, and the setting value are arbitrary. By multiplying the applicable sales commission rate (%) registered in the agency type column 703 by, for example, the annual insurance premium, the sales commission for the insurance contract of the agency is calculated.

FIG. 9 shows an example of an SP sales commission calculation table stored in the parameter DB 57. The sales commission calculation table shown in FIG. 9 includes a column 801 of insurance type, a column 802 of payment period, and a column 803 of SP sales commission rate. Similarly to the calculation of the sales commission of the agency, when the applicable sales commission rate (%) registered in the column 803 of the SP sales commission rate is multiplied by, for example, the annual insurance premium, the sales commission for the insurance contract of the SP is calculated. You. It should be noted that a grade may be provided for the SP to change the commission rate. The setting factor and setting value of the SP commission rate can also be arbitrarily determined.

FIG. 10A shows an example of a sales commission table for SPs stored in the commission management DB 55, and FIG. 10B shows an example of a sales commission table for agents stored in the commission management DB 55. Here, the application form number and the sales commission amount calculated by the method described below are registered as a pair. Although not shown in FIGS. 10A and 10B, more detailed information may be registered in the sales commission table.

Next, the operation of the system shown in FIG. 1 will be described with reference to FIGS. 11 to 17, the case where the SP performs the accounting process will be described. The SP operates the SP terminal 3 to input application form data including the application form number, the agency code, the SP code, and the like. Alternatively, data or a code indicating that the contract is an alliance between the agency and the SP may be separately input. Note that the application data that has already been input may be read, and necessary correction input or the like may be performed. The SP terminal 3 receives input of application form data from the SP, and transmits application form data including an SP code or the like to the server 5 according to the instruction of the SP (step S1). The control unit of the server 5 (in the following description, the process of the control unit is simply displayed as the process by the server 5) receives the application data including the SP code and the like from the SP terminal 3 via the communication unit (step S3). ), The application data including the SP code and the like is registered in the contract DB 51 (FIG. 2) (step S5). At this time, a type code indicating whether the contractor is a corporation or an individual is also registered. However, in this state, the registration is still temporary. In the case where application data that does not include the SP code, that is, receives application form data that is not a contract based on an alliance between the agency and the SP, this is a normal process, and a description thereof will be omitted. That is, in step S3, it is determined whether or not the application form data including the SP code has been received.

Next, the control unit of the server 5 (hereinafter similarly omitted) searches the parameter DB 57 (FIG. 7) using the agency code included in the application form data, and retrieves the distribution ratio setting table of the agency. Identify. Then, the allocation ratio setting initial data (initial value) included in the allocation ratio setting table is read (step S7). At this time, the server 5 sets an initial value related to the basic allocation ratio using a type code indicating whether the contractor is a corporation or an individual among the application data registered in the contract DB 51, and further sets an application. An initial value related to the visiting place is set from the contractor address in the document data and the data on the location of the sales participant extracted from the sales participant database by instructing the database management unit. As other initial values, initial values set in advance are used, and the server 5 generates distribution ratio setting registration page data (data for screen display) using the distribution ratio setting initial data. Then, the data is transmitted to the SP terminal 3 via the communication unit (step S9). The SP terminal 3 receives the distribution ratio setting registration page data and displays it on the display device (step S11).

For example, a screen as shown in FIG. 12 is displayed. The distribution ratio setting registration page of FIG. 12 includes a column 1101 of setting items, a radio button group 1102 for each setting item, a distribution ratio display column 1103, a registration button 1104, and an initialization button 1105. . The setting item column 1101 lists all items in the allocation ratio setting table (FIG. 7) except for the distinction between corporation and individual from the application form data. However, not all items need to be listed. For example, when the visiting place is specified by the linear distance between the SP business base and the customer address or the distance that is obtained by referring to a map information database (not shown), a database or the like in which the address information is associated with the latitude / longitude information or the like is used. Since the determination can be made automatically by preparing, the input by the SP on the distribution ratio setting registration page does not have to be required. The radio button group 1102 is initially set based on the distribution ratio initial data. In the distribution ratio display column 1103, only the distribution ratio based on the initial data read in step S7 may be displayed, but the numerical value can be changed and displayed based on the set value of each setting item (the selection status of the radio button). You may do it. When the user clicks the radio button to set a correct value for each setting item of the insurance contract, the user clicks the registration button 1104. To restart the input from the beginning, the user clicks the initialization button 1105.

Here, it is assumed that the SP operates the SP terminal 3 to set a correct value for each setting item and clicks the registration button. Then, the SP terminal 3 receives the distribution ratio setting input from the SP, and stores the distribution ratio setting input data (for example, a value of “0” or “1” corresponding to each item as shown in FIG. 4) of the server 5. The data is transmitted to the server 5 via the communication unit (step S13). At this time, the data to be transmitted includes the terminal identification code of the SP. The server 5 receives the distribution ratio setting input data from the SP terminal 3 and temporarily stores the data in the storage device (step S15). Then, a distribution ratio determination process is performed using the received distribution ratio setting input data and the distribution ratio setting table (FIG. 7) (step S17). For example, in the case of the initial value, 50% is allocated to the SP and 50% to the agency because the contract is for a corporation. Since the number of visits is 3 or less and the place of visit is 5 km or less from the SP sales base, the adjustment for these is 0. In addition, since the agency carries out the first appointment and accompanies the first visit, the adjustment for these is also zero. In addition, the SP performs needs grasping, securities diagnosis, design, presentation, closing, application, diagnosis arrangement, and accounting processing, so the SP is further allocated 9% (= 1 + 1 + 1 + 1 + 1 + 1 + 1 + 1 + 2), and the agency is reduced by 9% accordingly. Can be Therefore, the SP is 59%, and the agency has a distribution ratio of 41%. Further, the server 5 uses the terminal identification code of the SP acquired earlier to associate a terminal identification code (not shown) with a code number of the SP (or agent), and a terminal identification code / salesman code association table. , The SP that has transmitted the distribution ratio setting data is specified. In other words, by performing such processing, it is possible to determine whether the distribution ratio setting data has been transmitted from the SP or from the agency. After specifying the SP (or agency) that has transmitted the allocation ratio setting data, the server 5 transmits data for requesting approval to the corresponding agency (or). This processing will be described later.

In some cases, the adjustment may be performed according to the distribution ratio setting table based on the SP attribute shown in FIG. 7B. That is, in the example of FIG. 7B, if the attribute of the SP responsible for the insurance contract is A, the distribution ratio of the SP is added by 5%, and conversely, the distribution ratio of the agency is reduced by 5%. If the attribute of the SP is B, the distribution ratio of the SP and the agent is not changed. If the attribute of the SP is C, the distribution ratio of the SP is reduced by 5%, and conversely, the distribution ratio of the agency is added by 5%. For example, if the attribute table of the SP is stored in the parameter DB 57, the attribute value can be obtained from the SP code. Further, as described above, the sales person database may be provided to register the data of the sales persons. In this case, the server 5 instructs the database management unit to specify the code of the sales participant registered in the contract DB 51 using the application form number as a key. Then, using the code of the specified sales associate, the database management unit specifies the attribute of the SP by referring to a sales associate database (not shown). For example, it specifies whether the SP has a higher business processing capacity (A rank), a middle class (B rank), or a lower level (C rank). The distribution ratio between the agency and the SP is adjusted according to the specified rank as shown in FIG. This adjustment can be made at the time of initial value setting.

Furthermore, the distribution ratio may be adjusted according to the attributes of the customer group of the agency. For example, if the churn rate or the accident rate (loss rate) in the past one year is equal to or higher than a predetermined rate, an adjustment is made to reduce the base allocation rate by, for example, 5% in the next year. For example, this can be realized by adjusting the numerical value of another distribution ratio of the corporation and the individual in the distribution ratio setting table of FIG. 7A by 5%. However, when calculating the distribution ratio for each insurance contract, it may be adjusted by 5%. In this case, the contract DB 51 registers the contracts (including the contract period) handled by each SP and the agency and the amount of the insurance money (including the payment date) paid based on the contract, and the SP code and the agency code are used. The insurance amount and the insurance amount of the handled contract group are totaled. The server 5 instructs the database management unit to extract the data that requires the data of the contract DB 51, and refers to the extracted data to, for example, once a year (at the end of the fiscal year or the like) each SP or agency. Calculate the loss ratio of each handling contract group. The calculated loss ratio is temporarily stored in a predetermined storage area (for example, a salesperson database). The server 5 sets the distribution rate by using the recorded loss rate in advance and corresponding to the loss rate, applying a distribution adjustment rate stored in a table and stored in the parameter DB 57, for example. The adjustment of the distribution according to the attribute of the contract group can also be performed at the time of setting the initial value.

(4) When the distribution ratios of SPs and agents are determined from the above viewpoints, the data of the calculated distribution ratios are temporarily stored in the storage device.

The server 5 sends an allocation ratio confirmation request to the agent corresponding to the SP that has transmitted the allocation ratio setting data, in order to check the allocation ratio calculated according to the content input by the SP. 7 or to the agency (step S21). The server 5 specifies the SP code by referring to the terminal identification code / salesman code association table using the terminal identification code included in the distribution ratio setting data transmitted via the communication unit. The relative agency included in the setting data is specified, and the distribution ratio setting data transmitted to the agency is transmitted. The agency operates the agency terminal 7 to receive the distribution ratio confirmation request, and causes the agency terminal 7 to transmit the distribution ratio confirmation data request to the server 3 (step S23). Upon receiving the distribution ratio confirmation data request from the agency terminal 7 via the communication unit, the server 5 transmits the distribution ratio confirmation data including the distribution ratio data calculated in step S17 via the communication unit. (Step S25). The agency terminal 7 receives the distribution ratio confirmation data from the server 5, and displays the data on the display device (step S27).

For example, a display as shown in FIG. 13 is made. In the example of FIG. 13, a column 1201 of setting items, a radio button group 1202 for each setting item, a distribution ratio display column 1203, a confirmation button 1204, and a radio button are clicked when the input contents by SP are corrected. Button 1205, SP distribution ratio input field 1206 when the distribution ratio is corrected by numerical input, agency distribution ratio input column 1207, and numerical correction button 1208 for notifying server 5 of the numerical correction. Are provided. The agency looks at the selection value of each setting item and the distribution ratio display field 1203 and determines whether or not appropriate setting registration has been performed by the SP. If it is determined that the radio button is inappropriate, the user clicks on a part of the radio button group 1202 that is deemed appropriate, and clicks the correction button 1205. Alternatively, the user inputs a value considered appropriate in the SP distribution ratio input column 1206 or the distributor distribution ratio input column 1207, and clicks a numerical value correction button 1208. In the distribution ratio display field 1203, when the selection state of the radio button group 1202 is changed, the numerical value may be changed. Also, when a numerical value is entered in the SP distribution ratio input field 1206, the numerical value is automatically displayed in the distribution ratio input column 1207 of the agency, or conversely, the numerical value is displayed in the distribution ratio input column 1207 of the agency. Is input, a numerical value may be automatically displayed in the SP distribution ratio input field 1206 in some cases.

After the screen shown in FIG. 12 is displayed, the SP thinks that the secretary of the 13 setting items and the charge of maintenance of the 14 should be the SP, not the agency, and clicks the radio button on the SP side of each item, A registration button 1104 was clicked. For this reason, the secretary and maintenance items that were assigned to the agency in FIG. 12 are displayed so that the SP is assigned in FIG. Along with that, 2% each is added to the SP according to the setting of the allocation ratio setting table (Fig. 7) by the change of the secretary and the person in charge of maintenance, and the allocation ratio is corrected to 63% of the SP and 37% of the agency Have been.

In any case, the agency terminal 7 receives the confirmation response data input by the agency and transmits it to the server 5 (step S29). The confirmation response data (also referred to as correction instruction data when a correction instruction is included) includes the identification code of the agency terminal 7. In addition, the code number of each of the agency and the SP that are involved in the sales is also included. The server 5 receives the acknowledgment response data from the agency terminal 7 via the communication unit (step S31), and confirms whether or not a correction has been instructed based on the content (step S33). If selection data (for example, data as shown in FIG. 4) for each setting item is received by clicking the correction button 1205, or SP and agent (or its If any of the numerical data of the distribution ratio is received (the click of these correction buttons 1205 and the click information of the numerical correction button 1208 are included in the acknowledgment data as cookie information, for example, and transmitted to the server 5). ), It is determined that the correction has been instructed (step S33: Yes route), and the processing shifts to a step S47 in FIG. On the other hand, if it is determined that the confirmation button 1204 has been clicked from the content of the received data (step S33: No route), the server 5 determines that the SP and the agency have agreed on the distribution ratios. The final registration, that is, the application form data including the data of the final SP and the distribution ratio of the agency (step S35). As shown in FIG. 3, the server 5 instructs the database management unit to store the data of the distribution ratio of the SP and the distribution ratio of the agency, for which the agreement has been obtained, in accordance with the application form number. Register in the distribution ratio data table. As shown in FIG. 4, selection data for final registration of allocation ratio setting (and other data of insurance contractor corporations and individuals) is also registered in contract DB 51. Also, since the secretary is determined to be either the SP or the agent, the information is also registered in the contract data table shown in FIG. Further, in the result data table (FIG. 6) for each application form number in the achievement DB 53, the total result value, the ID of the agency, the distribution ratio of the agency, and the The result value, SP ID, SP distribution ratio, and SP result value are registered. Thereafter, the processing shifts to the step S37 in FIG.

Next, FIG. 14 will be described. The server 5 performs a calculation process of the agency commission and the SP commission (Step S37). In this calculation process, the sales commission calculation table of the agency shown in FIG. 8 and the sales commission calculation table of the SP shown in FIG. 9 are used. In the case of agents, special, advanced and ordinary types are assigned to each agent, so the information, the type of this insurance contract (lifetime or regular, or other types), and the insurance payment period Specifies the commission rate. Thus, for example, by multiplying the annual premium by the commission rate and the allocation percentage, the agent's sales commission for the insurance contract is calculated. That is, the sales commission is also distributed according to the distribution ratio. When using the results registered in the performance data table for each application number (Fig. 6) instead of the annual insurance premium, the distribution rate is already used, The sales commission is calculated by multiplying.

On the other hand, in the case of SP, since the type of SP does not matter when calculating the sales commission, the commission rate is specified by the type of the insurance contract and the insurance payment period. Therefore, for example, by multiplying the annual insurance premium by the commission rate and the distribution ratio, the sales commission of the SP for this insurance contract is calculated. That is, the sales commission is also distributed according to the distribution ratio. When using the results registered in the performance data table for each application number (Fig. 6) instead of the annual insurance premium, the distribution rate is already used, The sales commission is calculated by multiplying. The calculated sales commission amount data is registered in the commission management DB 55 corresponding to the application form number as shown in FIGS. 10 (a) and 10 (b). In addition, the total amount is increased by the sales commission acquired this time and registered.

{Circle around (5)} Then, the server 5 transmits a notification about each sales fee to the SP and the agency (step S39). The SP operates the SP terminal 3 to receive a notification about the sales commission and display the notification on the display device (step S41). This allows the SP to confirm the acquired sales commission. Similarly, the agency operates the agency terminal 7 to receive a notification about the sales commission and display the notification on the display device (step S43). This allows the agency to confirm the acquired sales commission.

Then, the server 5 performs a sales result calculation process of the sales person and the department of the insurance company to which the sales person belongs (step S45). This processing will be described later in detail with reference to FIG.

In this way, the distribution ratio of the sales commission is determined according to the attributes of the insurance contract (especially the attributes of the policyholder), the status of the agency or SP's contribution to the conclusion of the insurance contract, and the status of management after the conclusion of the insurance contract. And a sales commission according to the distribution ratio can be paid to the SP and the agency.

Next, a processing flow in the case where the agency corrects the distribution ratio will be described with reference to FIG. The server 5 transmits the correction confirmation request data to the corresponding SP or to the SP terminal 3 (Step S47). For example, the server 5 uses the identification code of the agent terminal 7 included in the previous confirmation response data (correction instruction data) to refer to the terminal identification code / salesman code association table, and the confirmation response data is Confirm that it was sent from the agency. Then, the server 5 transmits the correction confirmation request data to the SP terminal 3 corresponding to the relative SP included in the confirmation response data via the communication unit. Upon receiving the correction confirmation request from the server 5, the SP terminal 3 displays the request on the display device. For example, in accordance with the instruction of the SP, the SP terminal 3 transmits a correction confirmation data request to the server 5 (Step S49). Upon receiving the correction confirmation data request from the SP terminal 3, the server 5 generates correction confirmation data based on the correction instruction data received from the agency terminal 7, and transmits the correction confirmation data to the SP terminal 3 via the communication unit (step S51). . The SP terminal 3 receives the correction confirmation data from the server 5 and displays it on the display device (Step S53). For example, in the screen example illustrated in FIG. 13, for example, a portion that is “SP input content” is set as “agency input content”. When the agency specifies the numerical value of the distribution ratio, only the numerical value display column and the distribution ratio input column may be included. Further, there is a case where the content input by the SP last time is displayed so that the content can be compared.

The SP refers to the contents of the modification displayed by the agency displayed on the display device of the SP terminal 3 and determines whether or not to agree. If you agree, click the confirm button. If you do not agree, change the selection status of the setting item by clicking the radio button and click the modify button, or enter the appropriate value of the allocation ratio in the allocation ratio input field etc. Click the Modify button. The SP terminal 3 receives the input of the correction confirmation response by the SP, and transmits the correction confirmation response data to the server 5 (Step S55). The server 5 receives the correction confirmation response data from the SP terminal 3 and temporarily stores the data in the storage device (step S57). Here, the contents of the received correction confirmation response data are confirmed, and it is determined whether or not the data is a correction instruction (step S59). If it is determined that the instruction is a correction instruction (step S59: Yes route), the process returns to step S21 of FIG. On the other hand, if it is determined that the confirmation button has been clicked instead of the correction instruction, the server 5 determines that both the SP and the agent have agreed on the allocation ratio and determines the final allocation ratio of the SP and the agent. The application form data including the above data is registered, that is, counted (step S61). If, for example, the accounting process is performed from the agency terminal 7 or the SP terminal 3 before the server 5 confirms that both sides have agreed on the distribution ratio, the server 5 performs the accounting process. Not accepted. That is, when the server 5 receives the consent confirmation information, the server 5 can proceed to the step for accounting processing for the first time. As shown in FIG. 3, the data of the distribution ratio of the SP and the distribution ratio of the agency, for which both sides have agreed, are registered in the distribution ratio data table of the contract DB 51 in accordance with the application form number. As shown in FIG. 4, selection data for final registration of allocation ratio setting (and other data of insurance contractor corporations and individuals) is also registered in contract DB 51. Also, since the secretary is determined to be either the SP or the agent, the information is also registered in the contract data table shown in FIG. Further, in the result data table (FIG. 6) for each application form number in the achievement DB 53, the total result value, the ID of the agency, the distribution ratio of the agency, and the The result value, SP ID, SP distribution ratio, and SP result value are registered. Thereafter, the processing shifts to the step S37 in FIG.

(4) In the case where the correction is instructed by the agent in this way, the processing for obtaining confirmation of the distribution ratio to the SP again is performed.

Next, the processing flow of the business result calculation processing will be described with reference to FIG. The server 5 reads one record of the result data table (FIG. 6) for each application form number stored in the result DB 53 (step S71). The result of the SP included in the record is added to the value of the result registered corresponding to the SP code in the result data table (FIG. 5) and registered in the result data table (FIG. 5). (Step S73). If the record has no SP code registered, step S73 is skipped. Further, the contribution of the SP is calculated by multiplying the result of the SP by a change ratio (for example, 0.7), and is registered corresponding to the department code of the SP in the result data table (FIG. 5). The result is added to the value of the result and registered in the result data table (FIG. 5) (step S75). That is, the result of the department to which the SP belongs is accumulated. Note that the replacement ratio is a distribution ratio to the sales office to which the SP belongs. The remaining distribution ratio is allocated to the SP management department. As in step S73, if the record has no SP code registered, step S75 is skipped.

Then, it is determined whether or not processing has been performed for all records to be processed (step S81). If there is an unprocessed record (step S81: No route), the process returns to step S71. On the other hand, when the processing has been performed for all the records to be processed (step S81: Yes route), the processing ends.

By performing the above processing, it is possible to calculate the business performance of each business unit, and perform statistics and evaluation.

Next, the accident handling process will be described with reference to FIG. For example, a call center accepts a report such as an accident by telephone (step S91). The operator of the call center operates the call center terminal 9 to instruct the server 5 to search for a contact using the application number or the like. The server 5 searches the contract DB 51 to read contract data (step S93), specifies secretary data included in the read contract data, and searches a correspondence table between an agency or SP (not shown) and contact information. The contact information of the secretary is extracted (step S95). The server 5 transmits the contact data to the call center terminal 9 and causes the display device to display the data. The operator looks at the contact information of the secretary displayed on the display device of the call center terminal 9 and contacts the secretary (step S97).

In step S95, the contact is specified based on the secretary data included in the contract data. However, when the secretary is not set, for example, the contact is specified by the distribution ratio in the distribution ratio table. Such a configuration may be adopted. For example, an SP or an agency having a relatively large distribution ratio is specified as a secretary. This is because the larger the allocation ratio, the greater the involvement in the insurance contract. In addition, although the description has been made with respect to dealing with an accident, similar processing may be performed even when there is some inquiry from a contractor.

In addition, when a call from a contractor to a call center or the like has changed the contract details or the contractor's status (change of address, etc.), and wants to change the contract contents, the call center The operator operates the call center terminal 9 to instruct the server 5 to specify the maintenance clerk data of the contract. The server 5 extracts the contact information of the sales representative who is in charge of maintenance, transmits the contact information to the call center terminal 9, and causes the display device to display the contact information. The operator looks at the contact information of the maintenance person displayed on the display device and contacts the person in charge. Further, when the maintenance person is not set, the contact is specified based on the distribution ratio in the distribution ratio table in the same manner as described above.

In this way, when a policyholder receives a notification of an accident response or a request for policy maintenance, the data of the person in charge of future management of such insurance contracts can be extracted and sent to the appropriate person. The response process can be entrusted. Further, even when a person in charge of the future management of the insurance contract has not been set, an appropriate person in charge can be contacted based on the allocation ratio.

Although one embodiment of the present invention has been described above, the present invention is not limited to this. For example, although the server 5 has been described as a single computer, a similar function may be implemented by a plurality of computers instead of a single computer. Further, the database configuration is not limited to the example of FIG. 1, and another database configuration for storing similar data may be adopted. Omitting the registration of some data may not have a significant effect.

In the above example, the attributes of the insurance contract, which are the insurance contractor's corporations and individuals (more specifically, the attributes of the insurance contractor), the contribution status up to the conclusion of the insurance contract, the management settings after the conclusion of the insurance contract, Although the distribution ratio of the sales commission between the SP and the agency is determined based on the combination of the above, it may be determined by this subset. Further, it may be determined by any of these. It is also possible to arbitrarily select to adjust the distribution ratio according to the attribute of the SP, or to adjust the distribution ratio also according to the accident rate or the churn rate of a past contract involving the agency. Also, in the present embodiment, an example has been shown in which the agent and the SP are sales participants relative to each other. It may be, or may be another sales person involved. The nature of the sales participants is arbitrary.

Further, the attributes of the insurance contract are not limited to the position of the insurance contractor, such as whether the insurance contractor is a corporation or an individual, or the distance between the insurance contractor and the SP (or agency) office. May be used as an attribute. For example, if the result is 1,000,000 yen or more, the agency is 60% and SP is 40%, if the result is less than 1,000,000 yen and 500,000 yen or more, both the agency and SP are 50%, and the result is If the amount is less than 500,000 yen, the distribution ratio between the agency and the SP may be determined stepwise according to the scale of the achievement, such that the agency is 40% and the SP is 60%.

Further, in the processing flow of FIG. 11 and thereafter, the processing flow when the SP performs the accounting processing is performed, but when the agency performs the accounting processing, the agency performs input for setting the distribution ratio, It is just as if the SP enforces the consent. Further, in the above-described example, the configuration is described in which the sum of the distribution ratio of the SP and the distribution ratio of the agency is 100%, but the sum does not necessarily have to be 100%. In this case, for example, results of less than 100% may be distributed to a third agency or SP. Similarly, as in the fourth and fifth embodiments, the distribution of the results of a contract in cooperation with a plurality of agents and the SP can be performed. In the processing flows of FIGS. 14 and 16, the order of the steps can be changed within a range that does not affect other operations.

It is a functional block diagram in one embodiment of the present invention. It is a figure showing an example of a contract data table stored in contract DB. It is a figure showing an example of a distribution ratio data table stored in contract DB. It is a figure showing an example of a distribution ratio judgment element data table stored in contract DB. It is a figure showing an example of a result data table stored in a result DB. It is a figure which shows an example of the result data table for every application number stored in the result DB. (A) is a diagram showing an example of a distribution ratio setting table stored in a parameter DB 57, and (b) is a diagram showing an example of a distribution ratio setting table based on SP attributes. It is a figure showing an example of a sales commission calculation table of an agency stored in parameter DB57. It is a figure showing an example of the sales commission calculation table of SP stored in parameter DB57. (A) shows an example of an SP sales commission table stored in the commission management DB 55, and (b) shows an example of a sales commission table for an agency stored in the commission management DB 55. FIG. 3 is a diagram illustrating a processing flow (1) according to the embodiment of the present invention. It is a figure showing an example of an agency SP distribution ratio setting registration page. It is a figure showing an example of a agency SP distribution ratio confirmation page. FIG. 9 is a diagram showing a processing flow (part 2) in the embodiment of the present invention. FIG. 10 is a diagram showing a processing flow (part 3) in the embodiment of the present invention. It is a figure showing the processing flow of business result calculation processing in one embodiment of the present invention. It is a figure showing the processing flow of the accident response processing in one embodiment of the present invention.

Explanation of reference numerals

Reference Signs List 1 network 3 SP terminal 5 server 7 agent terminal 9 call center terminal 51 contract DB 53 achievement DB
55 commission management DB 57 parameter DB

Claims (17)

Obtaining insurance contract data and storing it in a storage device;
When the acquired insurance contract data includes data indicating that the insurance contract is an insurance contract in cooperation with a first sales associate and a second sales associate, the insurance contract data is based on at least the attribute of the insurance contract. A distribution ratio determining step of determining a distribution ratio of a result or a sales commission to the first sales person and the second sales person, and storing data on the distribution ratio in a storage device;
An information processing method including: Obtaining insurance contract data and storing it in a storage device;
When the acquired insurance contract data includes data indicating that the insurance contract is an insurance contract in cooperation with a first sales associate and a second sales associate, the first sales associate and the second sales associate Identifying a contribution status of at least one of the second sales participants with respect to the conclusion of the insurance contract, and storing data regarding the contribution status in a storage device;
A distribution that determines a distribution ratio of a result or a sales commission to the first sales participant and the second sales participant based on at least the data on the contribution status, and stores the data on the distribution ratio in a storage device. A ratio determining step;
An information processing method including: In the allocation ratio determining step,
The distribution ratio of a result or a sales commission to the first sales participant and the second sales participant is determined based on the attribute of the insurance contract and the data on the contribution status. Information processing method. Acquiring charge setting data for future management of the insurance contract and storing it in a storage device,
In the allocation ratio determining step,
Further, based on the setting data on the future management of the insurance contract, a result or a sales commission distribution ratio between the first sales participant and the second sales participant is determined. Item 4. The information processing method according to any one of Items 1 to 3. In the allocation ratio determining step,
Further, based on an attribute of the first sales participant, a result or a distribution ratio of a sales commission to the first sales participant and the second sales participant is determined. 5. The information processing method according to any one of 4. The allocation ratio determining step,
When information indicating consent is received from the terminal of the first sales entrant and the terminal of the second sales entrant regarding the distribution ratio, data on the distribution ratio for which the consent has been obtained corresponds to the insurance contract. The information processing method according to claim 1, further comprising: registering the information. When receiving information indicating consent from the terminal of the first sales entrant and the terminal of the second sales entrant regarding the distribution ratio, further performing a accounting process using the insurance contract data. Item 7. The information processing method according to Item 6. The allocation ratio determining step,
Receiving information for determining the distribution ratio from at least one of the first sales entrant terminal and the second sales entrant terminal;
Transmitting, to at least one of the terminal of the first sales entrant and the terminal of the second sales entrant, a notification requesting consent for the distribution ratio;
The information processing method according to claim 1, further comprising: Calculating a sales commission for the first sales participant based on information including at least the allocation ratio of the first sales participant and the attributes of the first sales participant;
Calculating a sales commission for the second sales participant based on information including at least the allocation ratio of the second sales participant and attributes of the second sales participant;
The information processing method according to claim 1, further comprising: The attribute of the insurance contract may include at least one of the classification of the insurance contractor's corporation or individual, the performance of the insurance contract, or the positional relationship between the insurance contractor and the first or second sales associate. The information processing method according to claim 1 or 3, wherein: Changing a distribution ratio of a result or a sales commission to the first sales participant and the second sales participant based on an attribute of an insurance contract group made in relation to the second sales participant; The information processing method according to claim 1, further comprising: The method according to claim 1, further comprising: adding a result of the first sales participant to a result of a department to which the first sales participant is related according to the distribution ratio. Information processing method. The method according to claim 4, further comprising the step of: when contacted by the insurance contractor, specifying a contact based on data on the contribution status of the insurance contract or data on charge of future management of the insurance contract. Information processing method. A result calculation step of calculating a result of the first sales participant and the second sales participant based on at least the distribution ratio and storing data of the result in a storage device;
14. The information processing method according to claim 1, further comprising: A program for causing a computer to execute the information processing method according to any one of claims 1 to 14. Means for acquiring insurance contract data and storing it in a storage device;
When the acquired insurance contract data includes data indicating that the insurance contract is an insurance contract in cooperation with a first sales associate and a second sales associate, the insurance contract data is based on at least the attribute of the insurance contract. Distribution ratio determining means for determining a distribution ratio of a result or a sales commission to the first sales entrant and the second sales entrant, and storing data on the distribution ratio in a storage device;
Information processing device having Means for acquiring insurance contract data and storing it in a storage device;
When the acquired insurance contract data includes data indicating that the insurance contract is an insurance contract in cooperation with a first sales associate and a second sales associate, the first sales associate and the second sales associate Means for identifying the contribution status of at least one of the second sales participants with respect to the conclusion of the insurance contract and storing data relating to the contribution status in a storage device;
A distribution that determines a distribution ratio of a result or a sales commission to the first sales participant and the second sales participant based on at least the data on the contribution status, and stores the data on the distribution ratio in a storage device. Ratio determining means;
Information processing device having

Images