Abstract: A technique of tracking insurance funds using an interpretive representation of accounting information includes obtaining a plurality of accounting entities. It further includes deriving, based on the accounting entities, a plurality of funds-source entities and a plurality of funds-use entities. It further includes, in response to an allocation scheme, creating a set of tracking entities that allocate the funds-source entities to the funds-use entities, wherein each tracking entity connects one funds-source entity and one funds-use entity.

Abstract: Managing workflow on a plurality of installed application components that interact with a central hosted component is disclosed. A new rule is defined on the central hosted component. The new rule is applied, based on data provided by an installed application component and information that is managed by the central hosted component, to generate a new action item to be executed on the installed application component. The new action item to be executed by the installed application component is sent. The new action item modifies a workflow on the installed application component without modifying application code on the installed application component.

Abstract: Configuring composite ratebooks includes receiving configuration parameters associated with a composite ratebook; receiving a selection of one or more rate routines to be associated with the composite ratebook; receiving input defining one or more rate tables to be included in the composite ratebook; and generating a composite ratebook including the configuration parameters, the one or more rate routines, and the defined one or more rate tables. A rate routine includes operations used to determine a premium for an insurance coverage. The one or more rate tables include insurance factors used by the one or more selected rate routines to determine premiums for insurance coverages.

Abstract: Automated assignment of insurance claim work includes: obtaining an insurance claim work unit; identifying among a plurality of users of the insurance claims processing platform a set of eligible users who are eligible to process the insurance claim work unit; and automatically selecting among the set of eligible users a selected user to process the insurance claim work unit, including determining a set of weighted workloads that corresponds to the set of eligible users and applying a set of one or more assignment rules based on the set of weighted workloads.

Abstract: A computer-based insurance claim processing system (500) provides for the formation and segregated storage of associations (510) that link various active insurance claims (506) to one another. In addition, if desired, the associations can comprise additional information regarding, for example, the nature or type of association and/or other information as a user may wish to include to inform, control, or otherwise characterize the association and/or the associated claims.

Abstract: Insurance policy management includes: interpreting an insurance product model to facilitate collecting supplemental policy-specific data, the insurance product model defining structures of a plurality of derived insurance policies; obtaining the supplemental policy-specific data; and performing an insurance-related action based at least in part on the supplemental policy-specific data.

Abstract: An insurance policy is stored (101) as a plurality of discrete temporally-sequential policy data revisions. A legally binding revision for a first given date is then determined (102) by identifying all policy data revisions effective on the first given date and choosing a most temporally recent policy data revision temporally prior to a second given date. When a new policy data revision is (103) temporally subsequent as compared to a first policy data revision and also comprises a legally effective date range preceding at least in part an effective date range of the first policy data revision, legally non-overlapping policy data revisions are created (104) for each legally overlapping effective date range as exists between the new policy data revision and all temporally preceding revisions. Each newly-created legally non-overlapping policy data revision comprises changes introduced by the new policy data revision and at least one temporally preceding policy data revision.

Abstract: Providing configuration of inference logic for insurance policy forms is disclosed, including: presenting to a user: information associated with an insurance policy form; and a set of inference rule types, each inference rule type specifying a corresponding condition under which the form is to be created; receiving a selected inference rule type; presenting a set of insurance product definition templates; receiving a selected insurance product definition template corresponding to the selected inference rule type, the selected insurance product definition template being selected from the set of insurance product definition templates; and storing a mapping associated with the insurance policy form, wherein the mapping includes at least the selected inference rule type and the selected insurance product definition template.

Abstract: Presenting benefits of an insurance related product includes obtaining a master hierarchical benefits tree comprising a plurality of hierarchical levels, each hierarchical level comprising a plurality of nodes, at least one node in one hierarchical level is preconfigured to be connected to at least one node in an adjacent hierarchical level, the preconfiguration being based at least in part on categorized objectives of an insurance company; receiving a user selection of at least some nodes in the master hierarchical benefits tree; determining a set of available nodes in a next hierarchical level based at least in part on the user selection; and generating a customized hierarchical benefits tree that is formed based at least in part on the user selection and the master hierarchical benefits tree.

Abstract: Insurance policy management includes: interpreting an insurance product model to facilitate collecting supplemental policy-specific data, the insurance product model defining structures of a plurality of derived insurance policies; obtaining the supplemental policy-specific data; and performing an insurance-related action based at least in part on the supplemental policy-specific data.

Abstract: Managing insurance policy processing includes: receiving a set of insurance policy hold criteria specifying an insurance policy hold, the insurance policy hold criteria comprising an insurance policy hold period during which the insurance policy hold is in effect; receiving a request to execute an insurance policy processing operation on an insurance policy; determining, based at least in part on the set of policy hold criteria, that the insurance policy processing operation is subject to the insurance policy hold; disallowing the insurance policy processing operation from being executed; determining that the insurance policy hold is to be released; and allowing the insurance policy hold to be released.

Abstract: A computer-based insurance claim processing system (500) provides for the formation and segregated storage of associations (510) that link various active insurance claims (506) to one another. In addition, if desired, the associations can comprise additional information regarding, for example, the nature or type of association and/or other information as a user may wish to include to inform, control, or otherwise characterize the association and/or the associated claims.

Abstract: Insurance billing includes receiving a plurality of exceptions arising out of one or more billing events and associated with one or more billed parties; categorizing the plurality of exceptions into a plurality of exception groups based at least in part on one or more types of exceptions; determining, for an exception group corresponding to a particular type of exception, a plurality of exception metrics for each of one or more corresponding billed parties; presenting, to the user, a selectable plurality of exception groups; and in response to a user selection of a particular exception group, presenting to the user one or more billed party identifiers of the one or more corresponding billed parties in the particular exception group and the plurality of exception metrics determined for each of the one or more corresponding billed parties.

Abstract: A computing platform (201) of choice can be configured and arranged to access (102 and 103) a first memory (202) that stores attributes which specifically characterize a particular candidate insurance entity and a second memory (203) that stores mappings which relate insurance policy element availability for a plurality of insurance policy elements to various corresponding insurance entity characterizing attributes. The aforementioned attributes, by one approach, correspond to respective end user-configurable dimensions. This platform can then serve (104) as a matching component by automatically using the aforementioned mappings to determine available insurance policy elements for the particular candidate insurance entity as a function of these attributes and then automatically using (105) those available insurance policy elements to configure an insurance policy consistent with these mappings.

Abstract: Managing risks associated with reinsurance includes: obtaining a plurality of insurance policies, each of the plurality of insurance policies comprising a plurality of coverages; identifying, for each insurance policy in the plurality of insurance policies, a set of coverages that corresponds to a geographical location, a policy level liability, or a covered item; and evaluating, for each identified set of coverages, a corresponding reinsurable risk, the evaluation includes determining a total insured value associated with the corresponding reinsurable risk.

Abstract: A computer-based insurance claim processing system (500) provides for the formation and segregated storage of associations (510) that link various active insurance claims (506) to one another. In addition, if desired, the associations can comprise additional information regarding, for example, the nature or type of association and/or other information as a user may wish to include to inform, control, or otherwise characterize the association and/or the associated claims.

Abstract: An insurance product model comprising insurance policy metadata is provided (101) in a computer memory. The insurance policy metadata may comprise, at least in part, data that describes information that comprises a given corresponding insurance policy. A computer then serves to substantively interpret (102) this insurance product model to facilitate obtaining supplemental policy-specific data. The supplemental policy-specific data and the insurance policy metadata comprise separate and discrete data models and may, if desired, be stored (103) separately from one another. So configured, these teachings further support using (104) the insurance product model and the supplemental policy-specific data to facilitate an insurance-related action.

Abstract: A computing platform (201) of choice can be configured and arranged to access (102 and 103) a first memory (202) that stores attributes which specifically characterize a particular candidate insurance entity and a second memory (203) that stores mappings which relate insurance policy element availability for a plurality of insurance policy elements to various corresponding insurance entity characterizing attributes. The aforementioned attributes, by one approach, correspond to respective end user-configurable dimensions. This platform can then serve (104) as a matching component by automatically using the aforementioned mappings to determine available insurance policy elements for the particular candidate insurance entity as a function of these attributes and then automatically using (105) those available insurance policy elements to configure an insurance policy consistent with these mappings.

Abstract: Insurance billing includes receiving a plurality of exceptions arising out of one or more billing events and associated with one or more billed parties; categorizing the plurality of exceptions into a plurality of exception groups based at least in part on one or more types of exceptions; determining, for an exception group corresponding to a particular type of exception, a plurality of exception metrics for each of one or more corresponding billed parties; presenting, to the user, a selectable plurality of exception groups; and in response to a user selection of a particular exception group, presenting to the user one or more billed party identifiers of the one or more corresponding billed parties in the particular exception group and the plurality of exception metrics determined for each of the one or more corresponding billed parties.

Abstract: A computer-based billing system presents, via an end-user interface, a plurality of exceptions as have occurred with respect to corresponding billing events as pertain to a plurality of billed parties while also presenting exceptions metrics as pertain to this plurality of exceptions. These exceptions metrics include at least one age-related metric, at least one financial-related metric, and at least one count-related metric. These teachings then further provide for permitting the end user to selectively prioritize the presenting of the plurality of exceptions as a function of at least one of these exceptions metrics.