WO2001009801A9 - System and method for electronically providing a financial service using rating factors - Google Patents
System and method for electronically providing a financial service using rating factorsInfo
- Publication number
- WO2001009801A9 WO2001009801A9 PCT/US2000/021234 US0021234W WO0109801A9 WO 2001009801 A9 WO2001009801 A9 WO 2001009801A9 US 0021234 W US0021234 W US 0021234W WO 0109801 A9 WO0109801 A9 WO 0109801A9
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- module
- rating
- modules
- attribute
- financial service
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Definitions
- 60/146,958 (Attorney Docket No. ECOVP001+) entitled SYSTEM AND METHOD FOR ELECTRONICALLY PROVIDING FINANCIAL SERVICES USING MODULES filed August 3, 1999 which is incorporated herein by reference for all purposes; and this application claims priority to U.S. Provisional Patent Application No. 60/146,964 (Attorney Docket No. ECOVP002+) entitled SYSTEM AND METHOD FOR ELECTRONICALLY PROVIDING AN ESTIMATE FOR A FINANCIAL SERVICE filed August 3, 1999 which is incorporated herein by reference for all purposes; and this application claims priority to U.S. Provisional Patent Application No. 60/146,957 (Attorney Docket No.
- the present invention relates to a system and method for providing financial services.
- the present invention relates to a system and method for providing financial services.
- a financial service such as insurance
- a financial service may be provided through the use of reusable modules that may be called upon multiple times for various functions.
- An example of a practical result of the use of these modules is that an insurance program may be quickly and easily established in all states with a minimum of duplication of effort.
- a method according to an embodiment of the present invention for providing a financial service is presented. The method comprises providing a first rating factor by using a first module; providing a second rating factor by using a second module; combining the first and second rating factors to result in a third rating factor; and generating an estimated quote related to the third rating factor.
- a system for providing a financial service is also presented.
- the system comprises a processor configured to provide a first rating factor by using a first module; provide a second rating factor by using a second module; combine the first and second rating factors to result in a third rating factor; and generate an estimated quote related to the third rating factor.
- the system also includes a memory coupled to the processor to provide instructions to the processor.
- FIG. 1 is a block diagram of an example of a computer system suitable for use with an embodiment of the present invention.
- FIG. 2 is a flow diagram of a method according to an embodiment of the present invention for providing a financial service.
- FIG. 3 is another flow diagram of a method according to an embodiment of the present invention for providing a financial service.
- FIGs. 4A - 4B are further flow diagrams of a method according to an embodiment of the present invention for providing a financial service.
- FIG. 5 is an example of a table showing modules which may be used according to an embodiment of the present invention.
- FIGs. 6A-6F are examples of tables that may be used according to an embodiment of the present invention.
- FIG. 7 is a flow diagram of a method according to an embodiment of the present invention for using a meta collection in conjunction with providing a financial service.
- FIG. 8 is a flow diagram of a method according to an embodiment of the present invention for calculating a net factor in conjunction with providing a financial service.
- FIG. 9 shows an example of questions that may be asked of a potential customer who is interested in obtaining an auto insurance quote according to an embodiment of the present invention.
- FIGS. 10A - 10B shows an example of a list of collections and modules that are valid for a product according to an embodiment of the present invention.
- FIG. 11 shows an example of a screen shot of a quote manipulation tool.
- FIG. 1 is a block diagram of a general purpose computer system 100 suitable for carrying out the processing in accordance with one embodiment of the present invention.
- FIG. 1 illustrates one embodiment of a general purpose computer system.
- Computer system 100 includes at least one microprocessor subsystem (also referred to as a central processing unit, or CPU, 102). That is, CPU 102 can be implemented by a single-chip processor or by multiple processors.
- CPU 102 is a general purpose digital processor which controls the operation of the computer system 100. Using instructions retrieved from memory 110, the CPU 102 controls the reception and manipulation of input data, and the output and display of data on output devices.
- CPU 102 is coupled bi-directionally with memory 110 which can include a first primary storage, typically a random access memory (RAM), and a second primary storage area, typically a read-only memory (ROM).
- primary storage can be used as a general storage area and as scratch-pad memory, and can also be used to store input data and processed data. It can also store programming instructions and data, in the form of data objects and text objects, in addition to other data and instructions for processes operating on CPU 102.
- primary storage typically includes basic operating instructions, program code, data and objects used by the CPU 102 to perform its functions.
- Primary storage devices 110 may include any suitable computer-readable storage media, described below, depending on whether, for example, data access needs to be bi-directional or uni-directional.
- CPU 102 can also directly and very rapidly retrieve and store frequently needed data in a cache memory (not shown).
- a removable mass storage device 112 provides additional data storage capacity for the computer system 100, and is coupled either bi-directionally or uni- directionally to CPU 102.
- a specific removable mass storage device commonly known as a CD-ROM typically passes data uni-directionally to the CPU 102, whereas a floppy disk can pass data bi-directionally to the CPU 102.
- Storage 112 may also include computer-readable media such as magnetic tape, flash memory, signals embodied on a carrier wave, PC-CARDS, portable mass storage devices, holographic storage devices, and other storage devices.
- a fixed mass storage 120 can also provide additional data storage capacity. The most common example of mass storage 120 is a hard disk drive.
- Mass storage 112, 120 generally store additional programming instructions, data, and the like that typically are not in active use by the CPU 102. It will be appreciated that the information retained within mass storage 112, 120 may be incorporated, if needed, in standard fashion as part of primary storage 110 (e.g. RAM) as virtual memory.
- bus 114 can be used to provide access other subsystems and devices as well. In the described embodiment, these can include a display monitor 118, a network interface 116, a keyboard 104, and a pointing device 106, as well as an auxiliary input/output device interface, a sound card, speakers, and other subsystems as needed.
- the pointing device 106 may be a mouse, stylus, track ball, or tablet, and is useful for interacting with a graphical user interface.
- the network interface 116 allows CPU 102 to be coupled to another computer, computer network, or telecommunications network using a network connection as shown. Through the network interface 116, it is contemplated that the CPU 102 might receive information, e.g., data objects or program instructions, from another network, or might output information to another network in the course of performing the above-described method steps. Information, often represented as a sequence of instructions to be executed on a CPU, may be received from and outputted to another network, for example, in the form of a computer data signal embodied in a carrier wave. An interface card or similar device and appropriate software implemented by CPU 102 can be used to connect the computer system 100 to an external network and transfer data according to standard protocols.
- method embodiments of the present invention may execute solely upon CPU 102, or may be performed across a network such as the Internet, intranet networks, or local area networks, in conjunction with a remote CPU that shares a portion of the processing.
- Additional mass storage devices may also be connected to CPU 102 through network interface 116.
- An auxiliary I/O device interface (not shown) can be used in conjunction with computer system 100.
- the auxiliary I/O device interface can include general and customized interfaces that allow the CPU 102 to send and, more typically, receive data from other devices such as microphones, touch-sensitive displays, transducer card readers, tape readers, voice or handwriting recognizers, biometrics readers, cameras, portable mass storage devices, and other computers.
- embodiments of the present invention further relate to computer storage products with a computer readable medium that contain program code for performing various computer-implemented operations.
- the computer-readable medium is any data storage device that can store data which can thereafter be read by a computer system.
- the media and program code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known to those of ordinary skill in the computer software arts.
- Examples of computer-readable media include, but are not limited to, all the media mentioned above: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and specially configured hardware devices such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs), and ROM and RAM devices.
- the computer-readable medium can also be distributed as a data signal embodied in a carrier wave over a network of coupled computer systems so that the computer- readable code is stored and executed in a distributed fashion.
- Examples of program code include both machine code, as produced, for example, by a compiler, or files containing higher level code that may be executed using an interpreter.
- bus 114 is illustrative of any interconnection scheme serving to link the subsystems. Other computer architectures having different configurations of subsystems may also be utilized.
- FIG. 2 is a flow diagram of a method according to an embodiment of the present invention for providing a financial service.
- Data related to a financial service such as insurance
- a module associated with the provided data is then selected (step 202).
- Modules as defined herein, are encapsulations of code, with attributes that collectively define a component of a process of a financial institution. Examples of modules for insurance include the make of a car, a pricing weight of a person's driving record, and zip code. There may be multiple modules dealing with a specific piece of information needed for processing a particular type of insurance in a specified state. For example, there may multiple modules dealing the make of the person's car. Further details of modules will later be discussed in conjunction with the remaining figures, particularly FIG. 5.
- the selected module is executed (step 204).
- FIG. 3 is another flow diagram of a method according to embodiment of the present invention for providing a financial service.
- a quote request is received (step 300).
- the quote request may be sent via the Internet by a potential customer interested in a financial service product.
- an underwriting decision is then performed (step 302).
- the underwriting decision may be a preliminary decision determining whether this potential customer qualifies for an initial quote for the financial service product.
- a potential customer requesting a quote may provide information to help determine the underwriting decision. If the potential customer requests a quote for car insurance but it is determined that he is too high of a risk based on his driver's record, the requested quote may simply be refused. Accordingly, time and resources are not wasted in determining and describing a product that will eventually not be offered to the potential customer. Further details of the underwriting decision performed in step 302 will later be discussed in conjunction with FIGs. 4A - 4B.
- quote generation is performed (step 304). Modules may be used to perform the quote generation to return quote information to the potential customer requesting the quote. Further details of the generation of the quote are later discussed in conjunction with FIGS 4A - 4B.
- FIGs. 4A - 4B are further flow diagrams of an example of a method according to an embodiment of the present invention for providing a financial service.
- FIG. 5 shows an example of a modules table showing examples of modules and their attributes.
- FIGs. 6A - 6F show examples of table mappings and collections that may be used in conjunction with modules.
- FIG. 6 A shows a person table 600; FIG.
- FIG. 6B shows a frequency table 610
- FIG. 6C is an example of a table of mappings 620
- FIG. 6D is an example of a table of collections 630
- FIG. 6E is another example of a table of collections 640
- FIG. 6F is an example of a table of meta collections 650.
- a potential customer logs onto a web site providing a financial service (step 400).
- the potential customer requests a financial service application, such as an application for a particular type of insurance in a particular state (step 402).
- FIG. 9 is an example of questions that may be asked of a potential customer who is interested in obtaining an auto insurance quote. Examples of questions include name, gender, marital status, years as a licensed driver in the U.S., years without lapse in insurance coverage, points on driving record in the last three years, whether the person has completed a defensive driving course in the last three years, whether the person is a student with a B or better grade average, vehicle year, make, model, usage, principal driver, home zip code, and any other information that may be relevant to an application for the requested financial service product.
- Quote request modules associated with the selected state and selected insurance type are identified (step 404).
- modules used for the quote request process may be identified based on their assigned module type, such as quote request modules.
- An example of quote request modules associated with a selected state and insurance type is shown in FIGs. 6C and 5.
- FIG. 6C shows a mappings table that identifies modules with some attributes. For example, modules with an assigned type of "quote request", for the state of
- FIG. 5 shows an example of a modules table showing examples of modules and their attributes.
- the modules table 500 is shown to include the names 501 of the modules and various attributes 502A-502J of the modules.
- the modules included in the modules table 500 is zip code, car make, car year, zip code, and frequency.
- Further examples of module names include “Calculation”, “Content”, “Document”, “External”, “frame”, “rating”, and “underwriting”.
- attributes shown in the modules table 500 include code type 502A, code 502B, whether this module is repeatable 502C, a destination table 502D, a destination field 502E, initial conditions 502F, date from 502G, date to 502H, state 5021, and insurance type 502J.
- Further examples of attributes which may be associated with modules include the following: ATTRIBUTES FOR CALCULATION MODULE Calculation Language Destination Table Destination Field Destination Custom
- California may be the selected state 5021 and auto may be the selected insurance type 502J of FIG. 5.
- the modules that would be identified during step 404 include zip code, car make, car year, and frequency.
- quote request modules are then displayed to the potential customer (step 406).
- the potential customer then inputs requested data (step 408). Examples of requested data are later discussed in conjunction with FIG. 9.
- Each module then takes input associated with that particular module and places it in a predetermined location (step 410).
- An example of determining the predetermined location is shown in FIG. 5 as the attributes destination table 502D and destination field 502E. For example, if the destination table 502D of FIG. 5 identifies "person" as the destination table and "frequency" as the destination field, then the data related to frequency module would be placed in the person table 600 of FIG. 6 A in the frequency column.
- calculation modules related to the selected state and insurance type are then retrieved (step 412).
- the calculation modules may be modules that are related to calculating a rating associated with the potential customer and the insurance policy to be offered to him.
- the rating may be the insurance rate a potential customer would qualify to receive.
- Primary underwriting modules are then implemented in this example (step 414). These underwriting modules determine whether or not to offer insurance to this particular potential customer.
- Quote generation modules are then determined (step 416).
- Quote generation modules determine a rating factor or a set of rating factors to be used in offering a quote to the potential customer. As previously mentioned, these modules may be determined by referring to a mappings table 620 of FIG. 6C which give examples of types of the modules that may be associated with a given module.
- a net rating factor for the potential customer is then generated (step 450).
- a net rating factor is a customized rating factor for a particular potential customer that is a compilation of other rating factors. For example, there may be several rating factors provided in the form of modules such as car type, number of years of driving experience, driving record, insurance deductible, gender, age, location of residence, and age of the car. Each of these factors may be translated into a number system so that the number system may be associated with a particular cost and risk associated with that particular rating factor. For example, a ten may signify an extremely high risk factor which can be equivalent to a very high price for the offered policy, while a factor of one may indicate a very low risk and a correspondingly low price for the offered policy.
- the number system may be any system that denotes a degree of risk or price.
- a net factor For example, all of the various rating factors may be multiplied to produce a net factor.
- This net factor may be used in conjunction with a specific insurance company's base rate for a specific state. For example, a particular insurance company may have a base rate in the state of California for bodily injury at $1000 per year.
- the net rating factor may be combined with the base rate, such as multiplying by the base rate, to produce a price for the potential customer for a particular type of insurance. For example, if the bodily injury base rate for car insurance in California is $1,000 per year, then the potential customer's price may be $1,000 per year times the net factor calculated for this particular customer.
- another quote for another type of financial service may also be presented.
- a net rating factor may be generated for auto insurance for a potential customer in a given state.
- the same information provided by the potential customer may be used to generate a net rating factor for home owner's insurance.
- Both the auto insurance quote and the home insurance quote generated from these net rating factors may be presented to the potential customer. In this manner, even though a potential customer may only request a quote for auto insurance, he can view a quote for home owner's insurance without having to input a significant amount of additional information, if any at all.
- a quote manipulation tool may be displayed to the potential customer (step 452).
- An example of a quote manipulation tool is described in conjunction with FIG. 11.
- the use of a quote manipulation tool is optional.
- the net rating factor may be used to generate a quote for the requested financial service to be presented to the user. The user may then decide whether to accept the financial service at that price.
- a potential customer may insert variables to generate different quotes with a quote manipulation tool (step 454).
- the potential customer selects a policy or coverage (step 456).
- the potential customer then provides detailed information regarding the property or person being insured (step 458).
- the potential customer also provides billing information (step 460). Examples of the billing information include information required for electronic transfer. Validation of the information may then be performed (step 461). Resolution of outstanding issues are also performed if there are any outstanding issues (step 462). For example, a notification may be sent to the marketing department of the insurance company to send out a new customer package to the potential customer. Any remaining customer documents may be executed (step 464), and any required company documents may also be executed (step 466).
- FIG. 5 is an example of a modules table according to an embodiment of the present invention.
- the modules table 500 identifies the name 501 of the modules and the various attributes 502A - 502J associated with the modules.
- the sample list of attributes associated with the modules for the modules table 500 includes a code type 502A, code 502B, repeatable 502C, a destination table 502D, a destination field 502E, initial conditions 502F, date from 502G, date to 502H, state 5021, and insurance type 502J.
- a code type 502A indicates a type of programming code that is associated with a particular module. For example, SQL or math may be code types associated with a particular module.
- Code 502B is the actual code or calculation used in conjunction with the module.
- the code may identify a field in another table multiplied by a factor and added to another field from another table.
- the code associated with the module frequency may be a SQL code and defined as (person serious) times 5 plus (person minor) times 1 , wherein person serious indicates a column entitled "serious" in the "person” table and person minor is the "minor" column in the "person” table.
- the attribute "repeatable" 502C simply indicates whether a module may be used more than once in a particular process. For example, a potential customer may have more than one car that needs to be insured under his name. Accordingly, the car make and car year may be repeatable to allow input of more than one car.
- Destination table 502D and destination field 502E identify the location to which the data received from the potential customer associated with a particular module is to be placed. For example, the data received from the potential customer associated with the module "frequency” is placed in destination table “person" 600 of FIG. 6 A, in the destination field "frequency" of the "person” table 600 of FIG. 6 A.
- Initial conditions 502F indicate under what conditions the module is activated. For example, for processing billing information, data associated with the billing information is an initial condition such that the billing module does nothing if there is no billing information to process.
- Another example is a credit card module wherein initial conditions of the credit card module may include a credit card number, a charge on the credit card or a lack of payment of a charge on the credit card. Under these conditions, the credit card module is activated.
- Completion conditions (not shown) may also be used in addition to or instead of initial conditions 502F. Completion conditions may indicate under what conditions the module is deactivated.
- the credit card module may include completion conditions such as payment of a charge on the credit card. When a charge on the credit card is paid, then the credit card module is deactivated.
- the “date from” 502G and “date to” 502H indicate the time period during which the module is valid.
- State 5021 may indicate the state or location to which the module applies.
- Insurance type 502J which may also be financial services type, indicates what type of financial service to which the module applies.
- Modules may be dynamic such that the modules may be rearranged in any order and associated with any other module or program. Modules may be classified into collections or groups and may be arbitrarily rearranged. Modules may include definable and editable attributes and may be defined by a set of its attributes.
- Modules may be used so that an outside program simply executes the modules in any order desired by the programmer.
- a single module may be assigned to various uses such that the same module may be used repeatedly for different projects.
- a module may be disconnected from the data pool such that the module simply accesses the location of the data. Accordingly, the data may be changed in one location to update multiple modules.
- a group of modules or all of the modules may have at least one thing in common so that all of these modules may be generalized. For example, all modules or a subset of all modules may be valid for certain dates or have common initial conditions. This facilitates the use of an admin tool that can manipulate all of the modules or a subset of all of the modules by taking advantage of the factors that these modules have in common.
- a module is an encapsulation of code with attributes that collectively define a component of a process of financial services. It is optional to have different types of modules.
- An example of a type of module is a query module which would ask a potential customer a predetermined question or questions, such as the make of his car, and placing the answers to those questions in a predetermined location, such as a data table.
- Another example of a type of module is a rating module which is a piece of programming code that can determine a price for a particular financial service product.
- modules for a concept such as three modules for a car: make, model, and year. All of these modules associated with this particular concept may be placed in a collection called a car collection.
- FIGs. 6D and 6E show examples of a table of collections 640, 630.
- the collections table 640 shows the name of the collection, the name of the modules within that collection, and date from and date to which identify dates during which the collection is valid.
- a collection may also include other collections and not just modules.
- the collections are a convenient form of access to the modules. Collections are not necessary to access modules, however, some modules may be convenient to be grouped together because they are often accessed together. Accordingly, a collection, such as car collection, may be re-accessed and reused more conveniently then accessing every module and collection within the car collection each time those modules and collections need to be accessed.
- modules used for the auto insurance may be reused for the application for the property insurance.
- a collection may be used to take advantage of the relationships that have already been determined. Examples of names of collections include “frameset", “page”, and “content”. Each collection identifies modules or other collections which point to the location of those modules and other collections. The following are examples of modules and collections that may be included in collections:
- An operational collection is preferably a collection that gets executed, while a meta collection is preferably not executed.
- Meta collections are preferably not used by transactions, they are only for administrative purposes.
- a meta collection identifies modules or collections for an operation.
- a meta collection associates modules to collections.
- the example of the meta collection 650 shown in FIG. 6F shows electronic funds transfer (EFT) as the name of a meta collection. If an electronic funds transfer is desired in the state of Texas, then a module, such as one identifying a credit card number, should be added to a billing page content as well as to billing processing. For administrative purposes, it may be desired to group these two collections, billing page content and billing processing, together since changes to the billing page content would also effect billing processing. Accordingly, it may be helpful to group these two collections together under a meta collection.
- EFT electronic funds transfer
- the meta collection named "EFT" associates module 19 with collection 8 and module 35 with collection 11, collection 8 being billing page content and collection 11 being billing processing.
- Examples of module 19 and 35 may be a credit card number and expiration date. Accordingly, if it is desired to add electronic funds transfer to pay for the financial service, then the EFT meta collection identifies the modules to be included in a particular collection to ensure that the EFT is properly added. If the electronic funds information is changed, such as the customer wishes to charge on a different credit card, then the EFT meta collection may again be used to identify what new or revised modules need to be added to which collections to enact these changes.
- FIG. 7 is a flow diagram of a method according to an embodiment of the present invention for using a meta collection in conjunction with providing a financial service.
- a user such as the program administrator, selects an option (step 700).
- An example of an option is whether the user chooses to present electronic fund transfer as an option to a potential customer applying for insurance.
- the selected option is then looked up under a meta collection (step 702).
- Modules identified under the meta collection are inserted into operational collections from the meta collection (step 704).
- the operational collection puts together the modules required for the customer for the selected state and insurance type (step 706), as discussed in conjunction with FIGs. 2 - 6A-6F.
- FIG. 8 is a flow diagram of a method according to an embodiment of the present invention for determining a net rating factor for providing a financial service, such as in step 450 of FIG. 4B.
- a rating factor for each calculation module is looked up for the selected state and insurance type (step 800). All of these rating factors are multiplied together to result in a net rating factor (step 802).
- a base rate of the financial service provider is looked up for the selected state and insurance type (step 804). The base rate is then multiplied with the net rating factor to result in a price for the customer (step 806).
- these rating factors may be combined in any way such as addition, subtraction, division or by any other mathematical function or combinations thereof to result in the net rating factor.
- FIGS. 10A - 10B show an example of a list of collections and modules that are valid for a product according to an embodiment of the present invention. As shown in FIGS. 10A - 10B, collections can be included in other collections as well as modules (elements). Examples of collections include a purchasing master, quote request page, quote request frameset, quote questions frameset, auto quote, pre- underwriting calculation, preferred filter underwriting, post-underwriting calculation, auto program, auto rating, deductible rating, class factor rating, quote header page, drivers page, points questions content, and vehicles page.
- modules include quote header frame, drivers frame, vehicles frame, nav bottom frame, points calculation, symbol calculation, vehicle count, experience underwriting, accidents underwriting, points underwriting, frequency and severity calculation, driver assignment calculation, base rates rating, symbol rating, multiple vehicle rating, multiple vehicle rating, affinity group rating, mature driver rating, model year rating, and anti-theft rating.
- FIG. 11 shows an example of a screen shot of a quote manipulation tool.
- variables that may be used to allow the potential customer to see the effect of the premium quote includes bodily injury liability amount, property damage liability amount, medical payments, uninsured motorist bodily injury amount, uninsured motorist personal damage amount, comprehensive coverage, and collision coverage.
- a potential customer may vary any of these variables to recalculate the total premium quote for that customer.
- a method and system for providing a financial service has been disclosed.
- Software written according to the present invention may be stored in some form of computer-readable medium, such as memory or CD-ROM, or transmitted over a network, and executed by a processor.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Technology Law (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU65162/00A AU6516200A (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing a financial service using rating factors |
Applications Claiming Priority (14)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14696499P | 1999-08-03 | 1999-08-03 | |
US14694899P | 1999-08-03 | 1999-08-03 | |
US14696699P | 1999-08-03 | 1999-08-03 | |
US14694999P | 1999-08-03 | 1999-08-03 | |
US14695899P | 1999-08-03 | 1999-08-03 | |
US14695999P | 1999-08-03 | 1999-08-03 | |
US14695799P | 1999-08-03 | 1999-08-03 | |
US60/146,957 | 1999-08-03 | ||
US60/146,959 | 1999-08-03 | ||
US60/146,964 | 1999-08-03 | ||
US60/146,949 | 1999-08-03 | ||
US60/146,958 | 1999-08-03 | ||
US60/146,948 | 1999-08-03 | ||
US60/146,966 | 1999-08-03 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001009801A1 WO2001009801A1 (en) | 2001-02-08 |
WO2001009801A9 true WO2001009801A9 (en) | 2002-07-25 |
Family
ID=27568991
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/021235 WO2001009802A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing a financial service using collections including modules |
PCT/US2000/021160 WO2001009798A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing financial services using modules |
PCT/US2000/021181 WO2001009811A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing an estimate for a financial service |
PCT/US2000/021234 WO2001009801A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing a financial service using rating factors |
PCT/US2000/021180 WO2001009810A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically creating a new financial service product |
PCT/US2000/021220 WO2001009800A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically revising a financial service product |
PCT/US2000/021183 WO2001009799A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically managing financial service claims |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/021235 WO2001009802A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing a financial service using collections including modules |
PCT/US2000/021160 WO2001009798A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing financial services using modules |
PCT/US2000/021181 WO2001009811A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically providing an estimate for a financial service |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/021180 WO2001009810A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically creating a new financial service product |
PCT/US2000/021220 WO2001009800A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically revising a financial service product |
PCT/US2000/021183 WO2001009799A1 (en) | 1999-08-03 | 2000-08-02 | System and method for electronically managing financial service claims |
Country Status (2)
Country | Link |
---|---|
AU (7) | AU6516200A (en) |
WO (7) | WO2001009802A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6867789B1 (en) | 2000-02-15 | 2005-03-15 | Bank One, Delaware, National Association | System and method for generating graphical user interfaces |
US7127486B1 (en) | 2000-07-24 | 2006-10-24 | Vignette Corporation | Method and system for facilitating marketing dialogues |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4831526A (en) * | 1986-04-22 | 1989-05-16 | The Chubb Corporation | Computerized insurance premium quote request and policy issuance system |
US4839804A (en) * | 1986-12-30 | 1989-06-13 | College Savings Bank | Method and apparatus for insuring the funding of a future liability of uncertain cost |
US4837693A (en) * | 1987-02-27 | 1989-06-06 | Schotz Barry R | Method and apparatus for facilitating operation of an insurance plan |
US4953085A (en) * | 1987-04-15 | 1990-08-28 | Proprietary Financial Products, Inc. | System for the operation of a financial account |
US5557515A (en) * | 1989-08-11 | 1996-09-17 | Hartford Fire Insurance Company, Inc. | Computerized system and method for work management |
US5182705A (en) * | 1989-08-11 | 1993-01-26 | Itt Corporation | Computer system and method for work management |
US5191522A (en) * | 1990-01-18 | 1993-03-02 | Itt Corporation | Integrated group insurance information processing and reporting system based upon an enterprise-wide data structure |
US5235702A (en) * | 1990-04-11 | 1993-08-10 | Miller Brent G | Automated posting of medical insurance claims |
US5504674A (en) * | 1991-02-19 | 1996-04-02 | Ccc Information Services, Inc. | Insurance claims estimate, text, and graphics network and method |
US5802500A (en) * | 1992-05-06 | 1998-09-01 | The Evergreen Group Incorporated | System and method for computing a financial projection of a prefunding program for other postretirement employee benefits under FASB statement 106 |
US5655085A (en) * | 1992-08-17 | 1997-08-05 | The Ryan Evalulife Systems, Inc. | Computer system for automated comparing of universal life insurance policies based on selectable criteria |
US5913198A (en) * | 1997-09-09 | 1999-06-15 | Sbp Services, Inc. | System and method for designing and administering survivor benefit plans |
US5765142A (en) * | 1994-08-18 | 1998-06-09 | Creatacard | Method and apparatus for the development and implementation of an interactive customer service system that is dynamically responsive to change in marketing decisions and environments |
US5752236A (en) * | 1994-09-02 | 1998-05-12 | Sexton; Frank M. | Life insurance method, and system |
US5745687A (en) * | 1994-09-30 | 1998-04-28 | Hewlett-Packard Co | System for distributed workflow in which a routing node selects next node to be performed within a workflow procedure |
EP0806017A4 (en) * | 1994-12-13 | 2000-08-30 | Fs Holdings Inc | A system for receiving, processing, creating, storing and disseminating investment information |
US5754980A (en) * | 1995-05-24 | 1998-05-19 | Century Associates L.L.C. | Method of providing for a future benefit conditioned on life expectancies of both an insured and a beneficiary |
US5907828A (en) * | 1995-12-26 | 1999-05-25 | Meyer; Bennett S. | System and method for implementing and administering lender-owned credit life insurance policies |
US5930759A (en) * | 1996-04-30 | 1999-07-27 | Symbol Technologies, Inc. | Method and system for processing health care electronic data transactions |
US5855005A (en) * | 1996-06-24 | 1998-12-29 | Insurance Company Of North America | System for electronically auditing exposures used for determining insurance premiums |
-
2000
- 2000-08-02 AU AU65162/00A patent/AU6516200A/en not_active Abandoned
- 2000-08-02 AU AU66199/00A patent/AU6619900A/en not_active Abandoned
- 2000-08-02 WO PCT/US2000/021235 patent/WO2001009802A1/en active Application Filing
- 2000-08-02 WO PCT/US2000/021160 patent/WO2001009798A1/en active Application Filing
- 2000-08-02 AU AU65145/00A patent/AU6514500A/en not_active Abandoned
- 2000-08-02 AU AU65159/00A patent/AU6515900A/en not_active Abandoned
- 2000-08-02 AU AU65137/00A patent/AU6513700A/en not_active Abandoned
- 2000-08-02 AU AU65163/00A patent/AU6516300A/en not_active Abandoned
- 2000-08-02 WO PCT/US2000/021181 patent/WO2001009811A1/en active Application Filing
- 2000-08-02 WO PCT/US2000/021234 patent/WO2001009801A1/en active Application Filing
- 2000-08-02 WO PCT/US2000/021180 patent/WO2001009810A1/en active Application Filing
- 2000-08-02 WO PCT/US2000/021220 patent/WO2001009800A1/en active Application Filing
- 2000-08-02 AU AU65146/00A patent/AU6514600A/en not_active Abandoned
- 2000-08-02 WO PCT/US2000/021183 patent/WO2001009799A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
AU6516200A (en) | 2001-02-19 |
WO2001009798A1 (en) | 2001-02-08 |
WO2001009801A1 (en) | 2001-02-08 |
WO2001009810A1 (en) | 2001-02-08 |
WO2001009811A1 (en) | 2001-02-08 |
AU6514500A (en) | 2001-02-19 |
AU6516300A (en) | 2001-02-19 |
WO2001009802A1 (en) | 2001-02-08 |
AU6513700A (en) | 2001-02-19 |
AU6514600A (en) | 2001-02-19 |
WO2001009800A1 (en) | 2001-02-08 |
WO2001009798A9 (en) | 2002-08-08 |
AU6619900A (en) | 2001-02-19 |
WO2001009799A1 (en) | 2001-02-08 |
AU6515900A (en) | 2001-02-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8271304B1 (en) | System and method of providing pricing information | |
US20030139990A1 (en) | Method, apparatus and system for control and assessment of risk in commercial transactions | |
US7908210B2 (en) | Systems and method for managing dealer information | |
US20030229582A1 (en) | Method, apparatus and system for providing notifications in commercial transactions | |
US20030093302A1 (en) | Method and system for online binding of insurance policies | |
US20080091700A1 (en) | Network-based document generation and processing | |
US8050947B2 (en) | Automated insurance enrollment, underwriting, and claims adjusting | |
US8060382B1 (en) | Method and system for providing a healthcare bill settlement system | |
US20050119920A1 (en) | Method and apparatus for automated insurance processing | |
US20110119077A1 (en) | Virtual medical self management tool | |
US20010044773A1 (en) | Systems and methods for automatically obtaining loss mitigation loan workout decisions | |
US20070111190A1 (en) | Data Transformation And Analysis | |
US7966234B1 (en) | Structured finance performance analytics system | |
US20070192115A1 (en) | Method for initiating a real estate transaction | |
CN109658255A (en) | Continuation of insurance method, apparatus, equipment and storage medium | |
US20130218762A1 (en) | Method and software application and system for automated bill processing | |
US20060069631A1 (en) | System and method for providing an incentive program | |
US20060031125A1 (en) | Interactive forms processing system and method | |
WO2001009801A9 (en) | System and method for electronically providing a financial service using rating factors | |
US20110153366A1 (en) | System and method for pricing and issuing level pay death benefit policies | |
US11367146B2 (en) | Life insurance policy application process and system | |
US7974895B1 (en) | System and method for developing finance rate information | |
US20040167835A1 (en) | Record keeping system supporting tax determination | |
WO2002041109A2 (en) | Global vendor financing system and method | |
EP1275059A1 (en) | Insurance file note generation method and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
AK | Designated states |
Kind code of ref document: C2 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1/14-14/14, DRAWINGS, REPLACED BY NEW PAGES 1/14-14/14; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase in: |
Ref country code: JP |