JP2002092333A - Blanket insurance contract change processing system and its method, and storage medium with blanket insurance contract change processing program stored therein - Google Patents

Abstract

PROBLEM TO BE SOLVED: To largely improve the work efficiency of change processing of a blanket insurance contract and convenience of customers. SOLUTION: In this blanket insurance contract change processing system, an information processing terminal of a contractor of a blanket insurance contract for a plurality of insurance contract objects has a producing means of electronic data of a change approval bill having all or a part of change contents of the insurance contract of which approval is requested to an insurance company in relation to the change of the insurance contract objects of at lest blanket insurance contracts, and an information processing device of the insurance company has an information processing means for executing the information processing of the blanket insurance contract based on the electronic data of the received change approval bill.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system and method for batch insurance contract transfer processing for performing transfer processing of policy contents of a collective insurance contract for a plurality of insurance contract objects (for example, vehicles and real estate elements). The present invention relates to a storage medium storing an insurance contract transfer processing program.

[0002]

BACKGROUND OF THE INVENTION The present invention aims to dramatically improve the operational efficiency of casualty insurance such as car insurance and fire insurance and life insurance and the convenience of customers.

For example, many companies use or own a plurality of vehicles. As a car insurance contract system suitable for such a person (including a corporation) to conclude, there is a contract system called a fleet contract. In the fleet contract, the fleet contractor concludes an insurance contract with the insurance company for all or a part of the vehicle owned or used, with the insured as the insured.

Originally, an automobile insurance contract had to be concluded and paid an insurance premium before the vehicle was owned. However, in a fleet contract system in which many vehicles owned by a company or the like are collectively contracted. At the time of contract, by contracting in advance the insurance contract contents related to the transfer of vehicles owned by the company etc. after the contract, the contractor will be able to own vehicles (additional vehicles), sell, Notify the contents of the scrapped vehicles (reduced vehicles) and settle the transfer insurance fee at regular intervals.

[0005] The transfer processing when a company or the like newly owns a vehicle is as follows.

[0006] First, when a company or the like newly owns a vehicle (in the case of increasing the number of vehicles), it is determined whether or not the vehicle is covered by an insurance contract which has been previously contracted. Judgment as to whether or not to apply the insurance content to the vehicle concerned, and when applying the promised insurance content and the promised insurance content, a notice stating the details of the vehicle that will be owned on the specified date Create a copy of the certificate and attach a copy of the vehicle verification to the agency.

[0007] Upon receiving the notification, the agent checks the contents, prepares a transfer approval bill for each vehicle, calculates the transfer insurance fee, visits the contractor, receives a seal, and receives the transfer insurance fee. Create a receipt and issue it to the contractor. If there is a mistake in calculating the insurance premium, the same procedure must be performed again.

[0008] Thereafter, the sales representative of the insurance company collects the completed documents from the agency and enters the key or O.
By performing accounting using a CR (optical character recognition device), a transfer approval letter is created and sent, and a database is updated.

[0009] Each time the contracted vehicle is different from the contracted vehicle or when the contracted insurance content is not applied, the contractor informs the agency of the details. The contacted agency prepares a transfer approval bill, calculates the transfer premium, visits the contractor, receives a seal, and receives the transfer premium by the day the contractor owns the vehicle Create a receipt and issue it to the contractor.

[0010] A sales representative of the insurance company collects the completed documents from the agency and performs key input or OCR accounting to create and send a transfer approval letter and update the database.

When a contractor (a company or the like) sells or scraps a vehicle related to a fleet contract (in the case of a reduction in the number of vehicles), the contractor, an agency, and an insurance company exchange documents, etc. And update the database.

[0012]

When a company or the like newly owns a vehicle, it determines whether or not the vehicle is covered by an insurance contract that has been previously contracted, and then determines the insurance contents that have been previously contracted. In order to judge whether or not to apply to the vehicle, the information of the vehicle and the contents of the desired insurance must be collated each time with the contract contents, and the contracted target vehicle and the contracted insurance contents must be checked. In the case of application, a notice stating the contents of the vehicle that will be owned on the specified date is created separately from the management ledger of the assets etc. of the company etc. There is a problem that the store has to be notified, and the contractor (company or the like) requires a great deal of labor.

The agent receiving the notification of the increase in the number of vehicles checks the contents, prepares a transfer approval bill for each vehicle, calculates a transfer insurance premium, visits a contractor, receives a seal, and receives a transfer. In order to receive insurance premiums, create receipts, and deliver them to policyholders, it takes a lot of effort to manage forms such as transfer approval invoices and insurance receipts and create many forms, and visits companies etc. each time There is a problem that the cost to perform is generated.

Further, if there is a mistake in calculating the insurance premium, the same procedure must be performed again, so that not only a lot of costs are required but also the risk of losing the trust of the contractor.

[0015] Furthermore, the contractor must contact the agent every time only when the contracted vehicle is different from the contracted target vehicle or when the contracted insurance content is not applied. There is a problem that it takes.

[0016] Also, the contacted agent prepares a transfer approval bill, calculates the transfer insurance premium, visits the contractor, receives a seal, receives the transfer, by the day the contractor owns the vehicle. In order to receive the insurance premium, create a receipt, and issue it to the contractor, there is a problem that it requires a great deal of labor to manage the forms and prepare many forms, and incurs the cost of visiting a company or the like each time.

The insurance company supplies forms such as transfer approval bills and insurance receipts to the agency, so that printing costs for the forms,
There is a problem that costs such as inventory management are required.

[0018] The sales clerk of the insurance company collects the completed documents from the agent, and enters the key input or OC.
By performing the accounting by R, the transfer approval is created, sent, and the database is updated, so that there is a problem that a lot of labor and costs such as printing costs of the form and inventory management are required.

The problem when increasing the number of contract vehicles as described above is as follows.
This is almost the same when contract vehicles are reduced.

By the way, other than the automobile insurance, there is also an insurance which adopts a lump sum contract system. For example, group life insurance is insurance that uses a lump-sum contract method. In addition, fire insurance for factories and the like in which insurance premiums are set for each component such as mechanical equipment and buildings is also insurance that employs a lump-sum contract system.

In the insurance employing such a lump-sum contract method, the number of contracted objects may increase or decrease.
Even in this case, the above-described problem occurs.

An object of the present invention is to provide a package insurance contract transfer processing system and method capable of dramatically improving the work efficiency of the transfer of contract contents relating to the conclusion of a contract of the collective contract type and the convenience of customers, and a package insurance. It is intended to provide a storage medium storing a contract transfer processing program.

[0023]

In order to solve such a problem, a lump-sum insurance contract transfer processing system according to the present invention of claim 1 is an information processing terminal for a policy holder of a lump-sum insurance contract for a plurality of insurance contract objects. , Seek approval from the insurer, at least with respect to the transfer of the policy object of the lump-sum insurance contract,
A means for creating digitized data of a transfer approval request that describes all or a part of the transfer details of the insurance contract is provided, and the information processing device of the insurance company applies the relevant data based on the received digitized data of the transfer approval request. It is provided with transfer processing means for performing transfer processing for a lump-sum insurance contract.

According to a second aspect of the present invention, in the lump-sum insurance contract transfer processing system according to the first aspect of the present invention, the transfer processing means is configured to authenticate a contractor who has transmitted digitized data of a transfer approval request. After matching the lump-sum insurance contract with the contents of the transfer approval request, immediately or every predetermined period, a content confirmation report transmission unit that transmits digitized data of a content confirmation notice to the information processing terminal of the policyholder, An updating unit that updates the contents of the lump-sum insurance contract database immediately or at specified intervals based on a content confirmation response from the policyholder's information processing terminal, and a content confirmation response from the policyholder's information processing terminal And a transfer approval unit that creates digitized data of a transfer approval letter and transmits it to the information processing terminal side of the contractor immediately or based on a predetermined period.

According to a third aspect of the present invention, there is provided the lump-sum insurance contract change processing system according to the second aspect of the present invention, wherein the content confirmation note transmitting section requires the settlement of the insurance premium for the change requested for approval. At this time, the settlement insurance premium is calculated and included in the digitized data of the transfer approval letter.

According to a fourth aspect of the present invention, there is provided the lump-sum insurance contract transfer processing system according to the second or third aspect of the present invention, wherein the information processing terminal of the contractor is a notice of contents confirmation from an information processing apparatus of an insurance company. And an output unit that outputs digitized data of a transfer approval letter from the information processing device of the insurance company based on the digitized data of (1).

According to a fifth aspect of the present invention, there is provided the lump-sum insurance contract change processing system according to the fourth aspect of the present invention, wherein the notice of confirmation of the change includes information on a settlement premium to be settled in accordance with the change. The content confirmation unit of the information processing terminal of the contractor executes all or a part of the settlement process.

In a sixth aspect of the present invention, there is provided a lump-sum insurance contract transfer processing system according to any one of the first to fifth aspects of the present invention, wherein the information processing terminal of a contractor and the information processing apparatus of an insurance company are electronically connected. All or a part of the transmission and reception of the structured data is performed via an information processing device of an insurance business operator.

[0029] According to a seventh aspect of the present invention, there is provided a method for processing a transfer of a lump-sum insurance contract according to the present invention. , Requesting the insurance company to approve, transmit the digitized data of the transfer approval request that describes all or part of the transfer details of the insurance contract, and the information processing device of the insurance company digitizes the received transfer approval request. After the authentication of the contractor who sent the data and the comparison of the current lump-sum insurance contract with the contents of the transfer approval request, immediately or every specified period, digitize the notice of contents confirmation to the information processing terminal of the contractor The data is transmitted, and the information processing terminal of the contractor confirms the details of the transfer based on the digitized data of the notification letter of the content confirmation, and the information processing device of the insurance company confirms the content from the information processing terminal of the contractor. Based on the answer, the contents of the lump-sum insurance contract database are updated immediately or at regular intervals, and digitized data of the transfer approval form is created and transmitted to the contractor's information processing terminal side. The information processing terminal outputs digitized data of the transfer approval letter.

The present invention according to claim 8 is a storage medium storing a lump-sum insurance contract transfer processing program loaded on an information processing terminal of a policy holder of a lump-sum insurance contract for a plurality of insurance contract objects. The lump-sum insurance contract transfer processing program requires the insurer to approve at least the transfer of the insurance contract object of the lump-sum insurance contract. It has a creation function unit.

The storage medium according to the ninth aspect of the present invention is the eighth aspect of the present invention.
In the present invention, the lump-sum insurance contract transfer processing program further comprises: a contents confirmation function unit for confirming the contents of the transfer based on digitized data of a notice of contents confirmation from the information processing device of the insurance company; A transfer approval letter receiving function unit for outputting the digitized data of the transfer approval letter from the information processing device;

[0032]

DESCRIPTION OF THE PREFERRED EMBODIMENTS (A) Embodiment Hereinafter, a system and a method for processing a package insurance contract transfer according to the present invention and a storage medium storing a package insurance contract transfer processing program are applied to a fleet contract for automobile insurance. Embodiments will be described in detail with reference to the drawings.

(A-1) Configuration of the Embodiment FIG. 1 is a block diagram showing a schematic overall configuration of a package insurance contract transfer processing system 1 of this embodiment.

With respect to the automobile insurance contract, a contract handler (hereinafter, simply referred to as a handler) intervenes in addition to the insurance company and the customer (polician). Handlers are employees of insurance company sales agents, agents of agents, and individual agents.

In FIG. 1, the insurance company (office processing center, etc.) includes a server 10, various databases 11, a host computer 12, a center terminal 13, a dedicated printing unit 14, a form reading unit 15, a business branch terminal 16, and a form A reading unit 17 and the like are provided.

The server 10 is actually composed of a plurality of servers such as a communication server and an application server, but is collectively shown in FIG. The server 10
It has a communication function with the operator terminal 20 and the customer terminal 30, which will be described later. The server 10 creates digitized data to be sent to the customer terminal 30 or the operator terminal 20, and appropriately processes data received from the customer terminal 30 or the operator terminal 20.

The various databases 11 include a fleet contract database, a vehicle verification database, and the operator terminal 2.
0, a database for temporarily storing data received from the customer terminal 30, a database for storing data to be transmitted to the operator terminal 20 and the customer terminal 30, and a data for periodic processing. Databases,
There is a database that stores update data.

The host computer 12 performs processing for the contract database, such as recording of accounting data in various contract databases. In this specification, a description will be given on the assumption that the processing relating to the transfer of the lump-sum insurance contract is mainly performed by the server 10.

The center terminal 13 has a general configuration such as an input unit, a display unit, and a printing unit (not shown), and in addition to the above, special printing for printing a form or the like according to a special format related to insurance business. Unit (Printer) 14
And a form reading unit (OCR) 1 for reading various forms
5 is also connected.

The form reading unit 17 is connected to the host computer 12 via a communication server (not shown) or a dedicated line.
1 (one is shown in FIG. 1 but a plurality is actually used), which also constitutes a part of the insurance company side device. The accounting data of the paper form is also converted into the sales branch terminal 16.

The details of the above-mentioned various databases 11 will be clarified in the operation description described later.

The operator terminal 20 and the customer terminal 30 can be connected to the insurance company server 10 via the communication network 2.

The operator terminal 20 is of a personal computer level having a general configuration such as an input unit, a display unit, and a printing unit (not shown). A dedicated printing unit (printer) 21 for printing a form or the like according to a special format for insurance business is also connected to the operator terminal 20.

The customer terminal 30 is a customer (fleet contractor)
Is a so-called personal computer-level information processing device owned by the company. Although a detailed description of the configuration of the customer terminal 30 is omitted, it is necessary to have an image scanner in order to obtain at least image data for vehicle verification. The customer terminal 30 is connected to the server 10 or the operator terminal 20 via the communication network 2.
It can be connected to.

In the case of this embodiment, the customer terminal 30 has a fleet contract transfer processing program (including data and the like) 40 supplied directly from the insurance company or via the operator when the fleet contract is concluded. The fleet contract transfer processing program 40 may be provided by an insurance company on a recording medium such as an FD or a CD-ROM, or may be downloaded by the customer terminal 30 via the communication network 2. Further, the fleet contract transfer processing program 40
Need not be resident at the customer terminal 30, but may be loaded when the transfer processing is necessary.

Here, the fleet contract transfer processing program 40 may be common to all customers (fleet contractors), as will be described later. It may be.

FIG. 2 is an explanatory diagram showing an example of the functional configuration of the fleet contract transfer processing program 40.

The fleet contract transfer processing program 40 of this configuration example includes a transfer approval request function section 41, an insurance payment settlement function section 42, a transfer approval note receiving function section 43, a communication function section 44, a vehicle management data section 45, and the like. ing.

The transfer approval request function unit 41 is a processing routine for requesting the insurance company to approve the contents of the transfer of the fleet contract. The insurance premium settlement function unit 42 is a processing routine for confirming the notification of the settlement insurance premium accompanying the contents of the current transfer from the insurance company and performing a settlement process for the same. The transfer approval letter receiving function unit 43 is a processing routine for taking in a transfer approval letter made up of digitized data from the insurance company, outputting it, updating the data of each unit, and the like. The communication function unit 44 is a processing routine or the like for performing communication processing between the customer terminal 30 and the server 10 or the operator terminal 20. The vehicle management data unit 45 is a data unit that stores at least information on each vehicle related to the fleet contract and the details of the contract.

The communication function unit 44 performs an encryption process at the time of transmission and a decryption process at the time of reception. The encryption key (equivalent to the decryption key) may be the same for all customers (fleet subscribers), or may be different for each customer. In the latter case, the vehicle number of any vehicle related to the fleet contract (for example, the vehicle whose branch number is "5" described later) may be used as the encryption key.

The fleet contract transfer processing program 40
If the information is common to all customers (fleet contractors), the information (telephone number, e-mail address, etc.) required for connection with the vehicle management data section 45 and the operator terminal 20 is provided by the insurance company. (Server 10). Alternatively, the information may be provided to the customer as paper information.

The vehicle management data section 45 can be used not only in the fleet contract transfer processing program 40 but also by a customer (fleet contractor) for vehicle management unrelated to the fleet contract. It is preferable to keep it as a file. For example, a record for each vehicle is provided with not only data fields for items related to fleet contracts such as vehicle type information and insurance amount, but also data fields such as a driver name, a total mileage, and a next periodic inspection date. May be.

The system 1 of this embodiment can use any communication method, but hereinafter, a terminal (customer terminal) 30 to which an e-mail (hereinafter referred to as e-mail) address is assigned. Is intended for customers who have That is, the server 10 or the operator terminal 20 can transfer predetermined document data or the like to the customer terminal 30 by e-mail. In contrast, predetermined document data and the like can be transferred by e-mail.

Therefore, the communication network 2 shown in FIG. 1 also includes a configuration for providing an e-mail service of an e-mail service provider.

As an example of another communication method, there is the Internet. For example, by accessing the insurance company site from the customer terminal 30, entering the customer's password, taking out the input screen for the vehicle data related to the contract and the transfer approval request, entering various information in the input fields,
The digitized data of the transfer approval bill may be transmitted to the insurance company.

(A-2) Operation and Processing Flow of Embodiment Next, the operation of the system of the embodiment and the operation of a human (handler or customer) are described together with the processing flow in the sequence shown in FIGS. This will be described with reference to the drawings.

FIGS. 3 and 4 show the flow of processing from the customer's transfer application (transfer approval request) to the transmission of a transfer approval letter to the customer.

The customer (fleet contractor) purchases a new vehicle and wants to include that vehicle in the already-concluded fleet contract (when he wants to increase the number of vehicles) or sells some vehicles related to the fleet contract For example, when the vehicle is excluded from the contract due to scrapping or scrapping (when it is desired to reduce the number of vehicles), or when the vehicle related to the fleet contract is replaced by replacement of the vehicle, etc., the fleet contract transfer processing program 40 on the customer terminal 30 is started and the approval is approved. The contents of the change in the fleet contract to be claimed are input (digitized data) and transmitted to the insurance company side (server 10 or operator terminal 20) (T1).

The contents of the change in the fleet contract are as follows:
In addition to increasing the number of vehicles, reducing the number of vehicles, and replacing vehicles, there are also changes in the address of customers (fleet policyholders). Since the entire process is more complicated than in other cases, the following description focuses on the case where the content of the transfer is increased, decreased, or replaced. Increasing or decreasing the insurance amount without changing the vehicle also involves the process of adjusting the insurance premium. However, since the process at that time can be understood from the case of increasing the number of vehicles, decreasing the number of vehicles, or replacing the vehicle, the detailed description thereof will be omitted.

Although there is no limitation on the input method (digitization method) of the transfer contents of the fleet contract for which approval is requested, two examples will be described below.

First, a customer (fleet contractor) writes necessary information on a transfer approval bill, which is a paper form similar to the conventional one, and causes the image scanner to read the necessary information. The fleet contract transfer processing program 40 (transfer approval request) The function unit 41) obtains digitized data of the transfer contents of the fleet contract by optical character recognition. In addition, the transfer approval invoice, which is a paper form, is common to increasing, decreasing, and replacing vehicles, and may include items that can distinguish between increasing, decreasing, and replacing vehicles. , Vehicle reduction, and vehicle replacement may be separate.

A second method is to display an input screen for the details of the change on the customer terminal 30 and to input the details of the change by key input or selection from a plurality of options. Also in this case, the input screen may be common for increasing the number of vehicles, decreasing the number of vehicles, and replacing the vehicle, or may be different for increasing the number of vehicles, reducing the number of vehicles, and replacing the vehicle.

FIG. 5 is a flow chart showing the processing at the customer terminal 30 in the case of displaying and inputting separate input screens for increasing, decreasing, and replacing vehicles.

When the fleet contract transfer processing program 40 (transfer approval request function section 41) is started, first, a selection screen for selecting one of increasing, decreasing, and replacing vehicles is displayed (S1), and any of the transfers is performed. Is determined (S2).

When the additional vehicle is selected, an input screen for additional vehicles is displayed to input information on additional vehicles (S3).
If the vehicle reduction is selected, an input screen for vehicle reduction is displayed to input information on vehicle reduction (S4). If vehicle replacement is selected, an input screen for vehicle replacement is displayed to display the vehicle replacement input screen. The replacement information is input (S5). Note that the input information is stored internally for later confirmation processing.

In the case of increasing the number of vehicles, information such as the type of vehicle, the year, the contract amount, etc. of the additional vehicles is input. In the case of car reduction, the user is caused to input a branch number assigned to the car to be reduced in the concluded fleet contract and specific information of the vehicle. Please note that for multiple vehicles under a fleet contract,
A serial number is attached to the contract to distinguish it, and is called a branch number. In the case of vehicle replacement, a branch number of the vehicle that is lost due to the replacement and specific information of the vehicle,
In addition, information such as a vehicle type, a model year, and a contract amount of the vehicle added by the replacement is input.

FIG. 6 shows an example of an input screen in the case of increasing the number of vehicles, in which the number of additional vehicles is set in the "reception division, etc." In addition to the information, fleet contractor and handler specific information is also included. The specific information of the fleet contractor and the handler may be already inserted when the insurance company supplies the fleet contract transfer processing program 40 to the customer.

When the input of the details of the change is completed, in the case of increasing the number of vehicles and in the case of replacing the vehicles, a new vehicle verification image image of the vehicles included in the fleet contract is input (S6, S7).

Finally, an e-mail is sent to the operator terminal 20 or the server 10 of the insurance company (S8). At the time of this transmission, the transfer content body other than the specific information of the fleet contractor and the handler is encrypted and transmitted.

The display at the time of input may be a multi-window, and the contents of the current fleet contract by the vehicle management data unit 45 may be displayed in the vicinity of the input screen to provide a reference for input.

Further, whether to send the digitized data of the transfer approval bill to the operator terminal 20 or to the server 10 of the insurance company may be determined when the fleet contract is concluded.

When the destination of the digitized data of the transfer approval invoice is the operator terminal 20, the operator checks the transfer contents displayed on the operator terminal 20 (T2). When an input error or the like occurs, although omitted in FIGS. 3 and 4, the operator (handler terminal 20) exchanges e-mails with the customer (customer terminal 30) and transfers. Make the digitized data of the approval invoice appropriate. From the beginning, the digitized data of the appropriate transfer approval request and the digitized data of the transfer approval request that has become appropriate after correction are transmitted from the operator terminal 20 to the insurance company (server 10). At this time, the data is also encrypted and transmitted.

In the insurance company (server 10), when the customer terminal 30 or the operator terminal 20 receives the digitized data of the transfer approval bill for the fleet contract, it decodes the digitized data and sends it to a receiving database (not shown). After that, the insurance company (server 10) authenticates the customer (fleet contractor) using the password or the like included in the received data (T3). If the result of authentication is that the customer is not a legitimate customer, the received data may be discarded, although not shown in FIGS. 3 and 4, and the sender may be notified that authentication was not successful. You may reply.

In this authentication processing, when the digitized data of the transfer approval bill for the fleet contract is given from the customer terminal 30 without going through the operator terminal 20, the above authentication processing is required. It also includes a content confirmation process of whether or not sufficient information on items is included.

After the authentication, if the digitized data contains image data of the vehicle verification, it is stored in the vehicle verification database in association with the fleet contract number.
If the computerized data does not include the image data of the vehicle verification, immediately from the fleet contract database,
The data of the corresponding fleet contract is taken out, matched with the data given by the customer (T4), and the contents of the notice of the transfer approval from the customer are determined (T4).
5).

Although omitted in FIGS. 3 and 4,
Given the data in the fleet contract database,
When the data of the change content given by the customer is not appropriate (for example, when the branch number of the vehicle related to the vehicle reduction notification does not exist), the received data may be discarded. That effect may be returned.

If the content of the notification from the customer by the transfer approval bill (digitized data) is an increase in the number of vehicles, the branch number of the vehicle related to the increase in the fleet contract is secured (T
6) In the case of vehicle replacement, the vehicle information of the corresponding branch number in the fleet contract is replaced (T7), and in the case of car reduction, the corresponding branch number in the fleet contract is canceled (T8). At this stage, data manipulation by such processing is performed on the buffer of the server 10.

Thereafter, the settlement insurance premium, the renewal insurance premium, and the like are calculated in any of the cases of increasing the number of vehicles, replacing vehicles, and reducing the number of vehicles (T).
9, T10, T11). The insurance premium under the fleet contract is to be paid at a specified period, such as a specified date on a monthly basis, and the transfer requires an update of the insurance premium, and the transfer requires a settlement of the insurance premium. These are calculated.

In the case of increasing the number of vehicles or replacing vehicles, it is determined whether or not the newly contracted vehicle complies with the target vehicle type and the contents of insurance contracted in the original fleet contract, in other words, whether or not immediate settlement is required. (T12), and when immediate settlement is not required (when the newly contracted vehicle complies with the contract contents), the calculated data such as the settlement insurance premium and the change contents are periodically (monthly, etc.) ) Store in the processing database, and in the case of car reduction, immediately after the calculation of the settlement insurance premium is completed, the calculated data such as the settlement insurance premium and the contents of the change are stored in the regular (monthly etc.) processing database (T1).
3).

In the case of increasing the number of vehicles or replacing vehicles, if immediate settlement is required, the calculated data such as the settlement insurance premium and the details of the change are stored in the update database (T14).
In addition, a notice (contents confirmation; digitized data) of the calculated settlement premium, the set new branch number, and the like is formed, and the operator terminal 2
0 or send an e-mail to the customer terminal 30 (T1
5). Also at the time of this shipping, encryption processing is performed as appropriate.

FIGS. 7 and 8 show examples of the structure of such a content confirmation note (digitized data) in a display image.

The example of the notice 60 shown in FIG. 7 and FIG.
The first page 60-1 describes bibliographic information such as a greeting from the insurance company, and the second page 60-2 describes the body of the information to be notified. Yes,
The information on the second page is encrypted (encryption different from encryption during communication). On the first page 60-1, a content display icon 60a is provided. When the content display icon 60a is clicked, an input of an encryption key (decryption key) is required, and an encryption key (same as a decryption key; for example) First page 60 by inputting contractor's ID and password)
-2 is displayed. In addition, page 6
0-2 is provided with a content confirmation icon 60b and a cancel icon 60c. When the content confirmation icon 60b is clicked, at least data on the settlement method of the settlement insurance premium is sent to the operator terminal 20 by e-mail. Also,
When the cancellation icon 60c is clicked, the cancellation data of the transfer approval request is displayed in the handler terminal 20 or the server 10 of the insurance company.
An e-mail is sent to.

Here, the operator (the operator terminal 20) can view the contents of such a notice by, for example, inputting a special code or the like. Alternatively, the second page 60-2 is sent to the handler without encryption, and the
When transmitting to the customer terminal 30, the second page 60-2 may be encrypted.

Whether the notice (digitized data) such as the calculated settlement premium and the set new branch number is transmitted to the operator terminal 20 or the customer terminal 30 is determined, for example, when a fleet contract is concluded. It is based on an agreement or the like as to whether or not to go through the operator terminal 20.

The operator displays the contents of such a notice on the operator terminal 20 and confirms the contents.
An e-mail is sent to (T16). In addition, the handler
A comment or a message may be inserted into the notice. For example, a message such as "You can ask for payment" may be inserted.

The customer displays the contents of the notice on the customer terminal 30, confirms the contents (T17), and performs a settlement procedure (T18).

FIG. 9 is a flowchart showing the processing at this time in the customer terminal 30. First, when a notice (digitized data) is received (S10), the first page 60-1 is displayed (S11), and a click on the content display icon 60a is awaited (S12). Then, the content display icon 60a
Is clicked, an input of a decryption key for displaying the second page is requested (S13), and by inputting an appropriate decryption key, a decryption process is performed to display the second page 60-2 (S13).
14). When displaying the second page 60-2, it is possible to check the collation with the data stored at the time of transmitting the transfer approval bill (digitized data) and display the result of the match / mismatch.

Thereafter, the input by the customer is determined (S1).
5). If there is an input of a settlement method (a default method is provided) of the settlement insurance premium, the settlement method is updated to the input (S16), and the process returns to the customer input discriminating process (S15). If the customer input is a click on the content confirmation icon 60b, the data including at least the settlement method is encrypted and sent to the operator terminal 20 by e-mail (S17). Further, if the customer input is a click on the cancel icon 60c, the data for canceling the transfer approval request is entered in the operator terminal 2
0 or the server 10 of the insurance company encrypts and sends the e-mail (S18).

The operator terminal 20 when canceling the transfer approval request
Alternatively, the processing in the insurance company server 10 is data deletion or the like, and thus further description is omitted.

The settlement method data transmitted to the operator terminal 20 may be, for example, a cash payment by a visit of the operator, an automatic deduction of an adjustment insurance premium from an insurance withdrawal account, or a credit card. Withdrawal,
It specifies the settlement method such as transfer processing. It is possible that the insurance company pays the settlement insurance premium to the customer. In this case, the customer specifies a desired payment method by the settlement method.

The operator performs payment and confirmation of the settlement process in accordance with the settlement method displayed on the operator terminal 20, and contacts the insurance company through communication processing (T19). Note that the confirmation here is not the confirmation of whether the deposit or settlement has been completed (this case may be confirmed), but the confirmation of whether or not the procedure to complete the deposit or settlement has been taken. It may be confirmation. For example, in the settlement using a credit card or the like, payment is made a long time after the procedure is executed. However, it is only necessary to confirm that the regular procedure for settlement using the credit card or the like has been executed.

When the insurance company (server 10) can confirm that the payment or payment processing procedure related to the payment insurance premium has been performed (T20), the host computer 12 uses the data stored in the update database by the host computer 12. The data of the corresponding fleet contract in the fleet contract database is updated (T21), and the loan account data of the agent that manages the payment of the insurance premium of the customer (fleet policy holder) is also included in the settlement premium and the like. It is updated accordingly (T22). Further, the insurance company (server 10) forms a transfer approval form (digitized data) based on the data stored in the update database, and sends it to the customer terminal 30 by e-mail (T23).

FIGS. 10 and 11 show examples of the structure of such a transfer approval letter (digitized data) by display images.

The transfer approval form 70 shown in FIGS. 10 and 11 also has a two-page structure.
1 describes bibliographic information such as a greeting from the insurance company, the second page 70-2 describes information on the body of the approval content, and the information on the second page is encrypted ( Encryption different from encryption during communication). A content display icon 70a is provided on the first page 70-1. When the content display icon 70a is clicked, an encryption key (decryption key) is displayed.
Is required, and only when an encryption key (same as a decryption key; for example, a contractor's ID or password) is entered, 2
The page 70-2 is displayed.

[0095] The transfer approval letter may include only the information of the vehicle related to the transfer, or may include the information of another vehicle related to the fleet contract.

The customer displays the contents of the transfer approval form (digitized data) on the customer terminal 30 and performs an output process as appropriate (T20). Although illustration of the flowchart is omitted, the customer terminal 30 corresponds to print output, corresponds to storage of the entire transfer approval form (digitized data), and corresponds to rewriting of the vehicle management data unit 45. The rewriting of the vehicle management data section 45 may be automatically executed by the fleet contract transfer processing program 40 (transfer approval note receiving function section 43) when the transfer approval letter (digitized data) is received.

On the other hand, the calculated data such as the settlement premium and the details of the change (see T13 described above) stored in the periodic processing database as not requiring the immediate settlement, are the dates (see T13) settled as the settlement date in the fleet contract. For example, on the X day of each month, the data is moved to the update database (T25), and a notice (digitized data) such as a settlement insurance premium is created based on the data (T26).

[0098] Thereafter, the same processing as in the case of the above-mentioned immediate settlement is executed, the transfer approval document (digitized data) is delivered to the customer (customer terminal 30), and the fleet contract in the fleet contract database is transmitted. Are updated in accordance with the transfer contents (T27 to T35).

[0099] Although the sequence is not shown for transfers (for example, address changes) other than transfers requiring settlement processing such as increasing the number of vehicles, replacing vehicles, or reducing the number of vehicles, similar to the above-described case,
Sending a transfer approval request (digitized data) from the customer (customer terminal 30) to the insurance company (server 10), sending a notice (electronic data) of collation at the insurance company and content confirmation to the customer, customer The transfer process is executed by the procedure of updating the fleet contract database based on the response (electronic data) of the content confirmation from the customer and sending the transfer approval letter (electronic data) to the customer.

(A-3) Effects of the Embodiment According to the package insurance contract transfer processing system 1 of the above embodiment, the following effects can be obtained.

In the event that a change in the fleet contract occurs, the customer forms a transfer approval request (digitized data) using the customer terminal 30 and makes a request for transfer approval without contacting the operator. This can be performed, and the labor, time, and cost for a transfer approval request can be significantly reduced compared to the conventional case.

Here, the fleet contract transfer processing program 40 required for this is provided by the insurance company to the customer, so it is not necessary for the customer to develop software for forming a transfer approval bill (electronic data). There is no burden.

Also, the fleet contract transfer processing program 4
By adding a lot of information (fleet contractor's name, address, insurance number (security number), etc.) in the default state of the transfer approval invoice (digitized data),
It is possible to reduce the number of items actually input by the customer, and in this respect, the input operation of the customer can be simplified.

Further, since the current vehicle information (vehicle management data section) of the fleet contract is included in the fleet contract transfer processing program 40, the current status can be accurately grasped.
It is easy to input a transfer approval bill (digitized data) appropriately. It is to be noted that the customer can also have a secondary effect that the vehicle management data section can be used for other than the transfer processing of the fleet contract.

Further, from the point of view of the operator, the transfer of the fleet contract of the customer is only slightly limited, such as in the case of cash settlement, even if the customer goes to the office. In addition, the labor and time required for the transfer process can be significantly reduced.

Further, from the point of view of the insurance company, the transfer related to the fleet contract can be dealt with by communication processing with the customer (customer terminal 30) or the operator (handler terminal 20), and the transfer processing can be executed quickly. This also has the effect of reducing costs by reducing the burden on operators and agents.

(B) Other Embodiments In the above embodiment, the lump-sum insurance contract transfer processing system and the like according to the present invention are applied to a fleet contract for automobile insurance. The system of the present invention can be applied to the present invention. For example, the system and the like of the present invention can be applied to group life insurance, fire insurance for factories and the like in which premiums are set for each component such as machinery and buildings, and the like.

[0108]

As described above, according to the present invention, the operational efficiency of the transfer processing of a lump-sum insurance contract and the convenience of customers can be dramatically improved.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating an overall configuration of a package insurance contract transfer processing system according to an embodiment.

FIG. 2 is a fleet contract transfer processing program 4 of the embodiment.
It is explanatory drawing which shows the example of a functional structure of 0.

FIG. 3 is an explanatory diagram (1) illustrating a flow of a transfer process of a collective insurance contract according to the embodiment;

FIG. 4 is an explanatory diagram (2) illustrating a flow of a transfer process of a collective insurance contract according to the embodiment.

FIG. 5 is a flowchart illustrating a process performed by the customer terminal when the transfer content is input according to the embodiment.

FIG. 6 is an explanatory diagram showing an example of an input screen for a change content in the case of additional vehicles according to the embodiment.

FIG. 7 is an explanatory diagram (1) showing an example of a notice (email data) of a settlement contract fee and the like according to the embodiment.

FIG. 8 is an explanatory diagram (2) illustrating an example of a notice (e-mail data) of a settlement contract fee and the like according to the embodiment.

FIG. 9 is a flowchart showing a process at a customer terminal at the time of confirming the change content and making a payment according to the embodiment.

FIG. 10 is an explanatory diagram (1) illustrating an example of a transfer approval letter (e-mail data) according to the embodiment;

FIG. 11 is an explanatory diagram (2) illustrating an example of a transfer approval letter (e-mail data) according to the embodiment;

[Explanation of symbols]

1 ... lump-sum insurance contract transfer processing system 2 ... communication network 10
... server, 11 ... various databases, 12 ... host computer, 20 ... handler terminal, 30 ... customer terminal, 40 ... fleet contract transfer processing program.

Claims (9)

[Claims] Claims: 1. A change in insurance contract, wherein an information processing terminal of a policy holder of a collective insurance contract for a plurality of insurance contract objects requests approval of an insurance company for at least a change in the insurance contract object of the collective insurance contract. Means for creating digitized data of the transfer approval claim that describes all or part of the transfer approval request, and the information processing device of the insurance company A lump-sum insurance contract transfer processing system comprising transfer processing means for performing transfer processing. 2. The method according to claim 1, wherein the change processing means authenticates a contractor who has transmitted the digitized data of the change approval request, and immediately or for a predetermined period after comparing the current package insurance contract with the contents of the change approval request. Each time, based on the contents confirmation response from the information processing terminal side of the contractor,
An update unit that updates the contents of the lump-sum insurance contract database immediately or at specified intervals, and based on the content confirmation response from the information processing terminal side of the policyholder,
The lump-sum insurance contract according to claim 1, further comprising: a transfer approval unit that creates digitized data of the transfer approval letter immediately or at a predetermined period and transmits the data to the information processing terminal side of the contractor. Transfer processing system. 3. The content confirmation note transmitting section calculates a settlement premium and includes it in the digitized data of the change approval letter when the change content required for approval requires the settlement of the insurance premium. The package insurance contract transfer processing system according to claim 2, wherein 4. The information processing terminal of a contractor, wherein the information processing terminal of the insurance company includes: a content confirmation unit for confirming a transfer content based on digitized data of a notice of content confirmation from the information processing device of the insurance company; 4. An all-in-one insurance contract transfer processing system according to claim 2, further comprising: an output unit for outputting digitized data of a transfer approval letter from the company. 5. The notice of confirmation of the contents of the change includes information on a settlement insurance premium to be settled in accordance with the change, and the contents confirmation section of the information processing terminal of the contractor performs all or a part of the settlement. 5. The batch insurance contract transfer processing system according to claim 4, wherein: 6. All or part of the transfer of digitized data between the information processing terminal of the contractor and the information processing device of the insurance company is performed via the information processing device of the insurance business operator. The package insurance contract transfer processing system according to any one of claims 1 to 5. 7. An insurance contract change wherein an information processing terminal of a policy holder of a collective insurance contract for a plurality of insurance contract objects requests approval of an insurance company at least for a change of an insurance contract object of a collective insurance contract. Send the digitized data of the transfer approval invoice that describes all or part of the above, and the information processing device of the insurance company authenticates the contractor who sent the received digitized data of the transfer approval invoice, After collating the contract with the contents of the transfer approval request, immediately or every specified period, the digitized data of the content confirmation notice is transmitted to the information processing terminal of the contractor, and the information processing terminal of the contractor The details of the transfer are confirmed based on the digitized data of the content confirmation notice, and the information processing device of the insurance company immediately or at specified intervals based on the content confirmation response from the information processing terminal of the contractor , Update the contents of the database of the lump-sum insurance contract, create the digitized data of the transfer approval form and send it to the information processing terminal side of the contractor, and the information processing terminal of the contractor And a method for processing a transfer of a lump-sum insurance contract. 8. A storage medium storing a lump-sum insurance contract transfer processing program loaded on an information processing terminal of a policy holder of a lump-sum insurance contract for a plurality of insurance contract objects, wherein the lump-sum insurance contract transfer processing program is provided. Must have a function to create digitized data of a transfer approval invoice that describes all or part of the transfer details of the insurance contract, which requires the insurance company to approve at least the transfer of the insurance contract subject of the lump-sum insurance contract. A storage medium storing a lump-sum insurance contract transfer processing program characterized by the above-mentioned. 9. The insurance package change processing program according to claim 1, further comprising: a contents confirmation function unit for confirming the contents of the change based on the digitized data of the contents confirmation notice from the information processing device of the insurance company; 9. The storage medium storing a package insurance contract transfer processing program according to claim 8, further comprising a transfer approval reception function unit for outputting electronic data of the transfer approval from the information processing device.