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 digital-computing platform provides a unified account current and statement billing workflow. This workflow comprises a plurality of event points including, for example, sending a statement, checking for receipt of a promise to pay, and checking for receipt of a payment. This platform uses an end-user interface to facilitate configuring a specific billing plan by use of this unified workflow. This can comprise configuring at least one action with respect to at least one of the aforementioned event points. By one approach, this can comprise providing an opportunity to select whether and when to send a statement, whether to receive a promise to pay, and/or a date by when to receive such a promise to pay. Configuring a specific billing plan can also comprise, if desired, providing an opportunity to identify an action to automatically take when an expected promise to pay is not received as expected.

Abstract: An insurance policy management computing system (201) stores a legally-binding insurance policy as a read-only document including the complete policy history. To facilitate revisions to the policy, the computing system (201) provides an opportunity (202) to revise an insurance policy and recalls (203) the currently legally-binding insurance policy. Since the legally-binding insurance policy is a read-only document, the computing system (201) uses the legally-binding policy to generate an editable version that is a complete copy of the legally-binding policy. Once the editable version of the insurance policy has been generated, the input revisions can be incorporated into the policy and then, the revised version of the insurance policy is saved as a read-only, now-current version of the insurance policy. The new legally-binding insurance policy has a new creation and effective dates of the various policy elements.

Abstract: An insurance policy management computing system (201) stores a legally-binding insurance policy as a read-only document including the complete policy history. To facilitate revisions to the policy, the computing system (201) provides an opportunity (202) to revise an insurance policy and recalls (203) the currently legally-binding insurance policy. Since the legally-binding insurance policy is a read-only document, the computing system (201) uses the legally-binding policy to generate an editable version that is a complete copy of the legally-binding policy. Once the editable version of the insurance policy has been generated, the input revisions can be incorporated into the policy and then, the revised version of the insurance policy is saved as a read-only, now-current version of the insurance policy. The new legally-binding insurance policy has a new creation and effective dates of the various policy elements.

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 computer-based processing system (29) for use in managing incident-related work provides an address book (103) containing a plurality of entries that persist independently of incident durations and that comprise contact information for corresponding entities. New contact information is then received (102) via the user interface, stored, and associated with a given incident and as regards an entity. The system then provides for establishing a link (103) between the stored contact information and a corresponding entry in the address book to thereby associate information that corresponds to a same entity, such that the link can facilitate subsequent processing of at least one of an incident and contact information.

Abstract: A computer-based insurance billing system for use in controlling insurance business processes is provided. As used herein the insurance business processes may include delinquency, invoicing, accruing earned commissions, paying commissions, distributing received payments, and disbursing owed amount, to note a few. At a user interface, the end user is provided (101) an opportunity to effect a trouble ticked with respect to a particular insurance entity. The characteristics of the trouble ticket may be automatically determined (102) to identify which of the insurance business processes relate to the trouble ticket. The end user is automatically provided (103) an opportunity to establish a temporary hold on the identified insurance business processes.

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: A computer-based processing system for use in controlling access to liability exposure data contains input received from an end user. The end user declares a plurality of exposure security levels that are associated with particular liability exposure data. A permission is declared for a user and the permission is mapped to the exposure security level. Upon an attempt to access the particular liability exposure data, the system then automatically verifies whether the user attempting to access the data has the permission required to access the exposure security level correlating to the particular liability exposure data.