Process and Apply Registrations to Periods

This operation provides means to process and apply registrations to a policy. This process makes it possible to realize new payments and determine coverage period that is paid for a policy.

This feature is only available when the system property indicates that the registrations should be applied to the periods.

The process consists of the following sub steps:

• process registrations

• determines the Date paid to for payments that received on time and are exact.

• creates mutation for a late and non accurate payment

• apply registrations

These two steps are described in detail in the Implementation Guide for Apply Payments

Resource Representation

Only approved policies (last version) are eligible for being processed when the system property indicates that the registrations should be applied to the periods. Whether a policy can be processed or not, can be derived by the presence or absence of the "processandapplyregirstations" link.

The resource representation of a policy that can be processed looks like

{
  " ...policy properties ...",
  "links": [
    {
      "href": "http://<host>:<port>/<contextRoot>/generic/policies/",
      "rel": "self"
    },
    {
      "href": "http://<host>:<port>/<contextRoot>/policies//processandapplyregistrations",
      "rel": "policy:processandapplyregistrations",
      "httpMethod": "POST"

    }
  ]
}

In the resource representation of a policy that is not approved (last version), the processandapplyregistrations link is missing:

{
  ... policy properties ...
  "links": [
    {
    "href": "http://<host>:<port>/<contextRoot>/generic/policies/",
    "rel": "self"
    }
  ]
}

Policy events for recalculation of level 'Policy' (referring to the policy at hand) or level 'Insurable Entity' (referring to one of the policy enrollments of the policy at hand) are picked up and translated into policy mutations (described in detail in the Implementation Guide for Change Events). That way, all policy mutations can be subjected to the premium calculation after which they can be discarded. Then process registrations and apply registrations to periods processes are executed after events are translated to mutations.

Payload

It takes in the following attributes:

Name	Description
Premium Financial Transaction Function	This function facilitates the modification of 1) financial transaction details and 2) financial transaction and financial transaction process data attributes of the premium financial transaction.
Commission Financial Transaction Function	This function facilitates the modification of 1) financial transaction details and 2) financial transaction and financial transaction process data attributes of the commission financial transaction.
Disable Grouping on Reversal Indicator for Invoice Lines?	The default behavior is that invoice lines are grouped on (among others) the reversal indicator; as a consequence credit and debit invoice lines can never result in a single zero result invoice line. Setting the parameter to 'Y' will disable this default behavior.

{
  "finTransDynLogic": "PREMTRANSLO-02",
  "comFinTransDynLogic": "COMTRANSLO-01",
  "disableRevGrouping": true
}

Response Messages

This operation will provide HTTP status codes as defined in Response Messages. If successful,HTTP Status 200 is returned together with a resource representation of the policy. If an error occurs, appropriate HTTP status code is returned along with the error details.

The following operation specific error can occur:

Code	Severity	Message Text
POL-HTTP-003	Fatal	Policy must be the last version and in status Approved

Authorization

The above described operation is protected by access restriction "policies.processandapplyregistrations IP". A grant for this access restriction must be provided. If the access to a policy is restricted by a data access group restriction, then to perform this operation on that policy also a grant for that data access group restriction must be provided with the Update flag set.