Customer Registration

Until now, you were able to create person, account, policy, and policy plan from the different screens. Now, ORMB provides the ability to create a person, multiple accounts for the person, multiple policies for the person, and multiple policy plans for the policy from the same user interface. A new object named Customer Registration is introduced in this release. Through a customer registration object, you can create person, accounts, policies, and policy plans at the same time from the same interface. Before creating a customer registration object, you need to create the following:

• Customer Registration Template

• Customer Registration Type

While creating a customer registration object, you need to specify the following:

• A customer registration type using which the customer registration object should be created

• A source system from the customer information is received

• A type of person that you want to create through the customer registration object

Once you specify the above details, the Customer Registration screen appears with a set of pages and sections which are added in the respective person template. The default values for the fields, characteristic types, identifier types, and phone types are shown as specified in the person template. In addition, the field values, characteristic types, characteristic values, identifier types, identifier values, phone types, and phone numbers are disabled as specified in the person template. On the Accounts page, you can view one row for each account template which is added in the customer registration type. You can then edit the row and thereby create an account for the person. You can create multiple accounts for the person using the same or different template.

On the Policies page, you can view one row for each policy template which is added in the customer registration type. You can then edit the row and thereby create a policy for the person. You can create multiple policies for the person using the same or different template. On clicking the Add icon corresponding to the policy row, you can view one row for each policy plan template which is added in the customer registration type. You can then edit the row and thereby create a policy plan for the policy.

On clicking the View/Edit icon or the Add New Account button in the Accounts page, the Customer Registration - Add Account screen appears with a set of pages and sections which are added in the respective account template. The default values for the fields, characteristic types, and identifier types are shown as specified in the account template. In addition, the field values, characteristic types, characteristic values, identifier types, and identifier values are disabled as specified in the account template.

On clicking the View/Edit icon or the Add New Policy button in the Policies page, you need to specify a policy type. The policy type indicates the category to which the policy belongs (i.e. whether it is Self Funded, Fully-Insured Group, or Fully-Insured Individual) and the policy business object using which the policy should be created. Once you specify a policy type, the Policy screen appears with a set of sections which are added in the respective policy template. The default values for the fields and characteristic types are shown as specified in the policy template. In addition, the field values, characteristic types, and characteristic values are disabled as specified in the policy template. You can create one or more policies for the person using the same or different policy type.

On clicking the View/Edit icon or the Add New Plan button corresponding to a policy plan row in the Policies page, the Plan screen appears with a set of sections which are added in the respective policy plan template. The default values for the fields and characteristic types are shown as specified in the policy plan template. In addition, the field values, characteristic types, and characteristic values are disabled as specified in the policy plan template.

You can save the person, account, policy, and policy plan details as and when you are entering the data by clicking the Save as Draft button. On clicking the Save as Draft button, the system creates a customer registration object in the Draft status. The status of the policies which are created through the customer registration object is set to Pending. Once the person, account, policy, and policy plan details are specified, you can click the Validate and Save button. The system then validates the information. You can edit, delete, or submit a customer registration object when it is in the Draft status. On submitting a customer registration object, the person, accounts, policies, and policy plans are created in the system. Finally, the status of the customer registration object is changed to the following depending on the type of person:

You can optionally configure the approval process for the customer registration. If the Approval Required option is selected in the customer registration type, the status of the customer registration object is changed to Approval In Progress on submitting it. A To Do using the approval To Do type is created and assigned to the users with the approval To Do role. The approver can then review the customer registration object and accordingly approve, reject, or request the submitter to resubmit the customer registration object for approval. On approving a customer registration object, the person, accounts, policies, and policy plans are created in the system. Finally, the status of the customer registration object is changed to the following depending on the type of person:

If the approver rejects a customer registration object due to some reason, the status of the customer registration object is changed to Rejected. However, if the approver requests the submitter to resubmit a customer registration object for approval after making the required changes, the status of the customer registration object is changed to Draft. The submitter can then make the required changes and resubmit the customer registration object for approval.

The system provides the following two options while defining a customer registration type:

• Manual Billing Hierarchy and Pricing- Used when you want to inform the user to create the billing hierarchy and pricing for the parent customer manually. In other words, you want the user to create the required bill groups for the parent customer, the bill group's accounts, pricing rules, bill group sorting information, and bill group derivation and pricing parameters. If this option is selected, a To Do is created using the Billing Hierarchy and Pricing To Do type and assigned to the users with the Billing Hierarchy and Pricing To Do role. This feature can be used only for customer registration objects where the person type is set to Parent Customer. Once the billing hierarchy and pricing is created for the parent customer, the user must complete the corresponding To Do which is created using the Billing Hierarchy and Pricing To Do type. On executing the Customer Registration Monitor (C1-CUSRG)batch, the system considers all customer registration objects which are in the Parent Customer Approvedor Pending Pricing Correction status. It checks whether the corresponding To Do (if any) created using the Billing Hierarchy and Pricing To Do type is completed. If so, it changes the status of the customer registration object to the following depending on whether the Final Approval Required option is selected:

  Final Approval Required (Yes or No)	Status
  Yes	Pending Final Approval
  No	Complete

• Final Approval Required- Used to indicate whether the final approval is required once the approver at the first level approves the customer registration object. Ideally, the final approval is required when the Manual Billing Hierarchy and Pricing option is selected. This ensures that the information related to the following entities is created and verified before the customer registration object moves to the Complete status:

  • Bill Group

  • Bill Group's Accounts

  • Bill Group's Sorting Records

  • Bill Group's Derivation and Pricing Parameters

  • Pricing Rules for the Policy Plans

  If this option is selected, a To Do is created using the Final Approval To Do type and assigned to the users with the Final Approval To Do role. This feature can be used only for customer registration objects where the person type is set to Parent Customer. Once the user with the Final Approval To Do role approves the customer registration object, the status of the customer registration object is changed to Complete.

  If the approver requests the submitter to resubmit a customer registration object for approval, the status of the customer registration object is changed to Pending Pricing Correction.

  Note: The system enables you to create maximum 10 accounts and 5 policies for a person and maximum 10 policy plans for a policy through a customer registration object from the user interface.

Once the status of a customer registration object is changed to Complete or Bill Group Approved, the system changes the status of the policies created through the customer registration object to In Force/Active. In addition, the status of the pricing rules which are created for such policies’ policy plans is set to Active.

You can also create a customer registration object using the File Upload Interface utility through an inbound message. On creating an inbound message using the File Upload Interface utility, the status of the inbound message is set to Pending. Once the inbound message is processed, a customer registration object is created in the following status depending on the person type:

At present, only the XML format is supported for creating a customer registration object using the File Upload Interface utility through an inbound message. To implement the Customer Registration feature, the following new screens are introduced in this release:

• Customer Registration Template

• Customer Registration Type

• Customer Registration

Parent topic: Oracle Revenue Management and Billing Insurance Business Processes