Views:

Overview

In this article we'll show how North52's business rules engine, a Microsoft Dataverse model driven app and Power Pages can be combined to build an effective solution to manage the rules and regulations regarding pension transfers in the UK. A similar solution could be used for many regulatory processes around the world. 

The Pensions Regulator provides detailed guidance on managing transfer requests within pension schemes. Their website offers information on the legal obligations and responsibilities of scheme administrators when processing transfer requests. 

The guidance covers various aspects, including the assessment of member requests, transfer processes, and safeguards to protect members' interests. It emphasizes the importance of conducting due diligence to ensure that transfers are in the best interests of the members and outlines the steps administrators should take to assess the receiving scheme's suitability, such as checking for appropriate authorization and conducting risk assessments.

The guidance also addresses the potential risks associated with pension scams and the importance of protecting members from fraudulent activities. It highlights the need for robust anti-scam measures and provides resources and tools to help administrators identify and mitigate risks.

Using this information we can design as system to assist scheme administrators in effectively managing transfer requests while adhering to legal requirements and safeguarding the interests of pension scheme members.

 

 

Rules for Pension Transfer Request

High level rules are shown by the following Decision Tree:

Pension Transfer Decision Tree

These rules can be implemented using a combination of Dataverse Business Process flows and North52 rules (Formulas).

  • Business Process Flow used for the high-level milestones 
  • North52 Rules for:
    • Analysing results from Questionnaire and identifying Red and Amber risks
    • Creating Tasks for specific parts of the process, and validating tasks before moving the to the next stage
    • Power Pages
      • UI rules for showing/hiding/validating fields
      • UI rules for displaying progress bar (North52 Quick Tile functionality)

 

North52 Decision Suite Solution

For this article we will focus on the North52 solution for Analysing results from the Questionnaire and identifying Red and Amber risks - it works like this:

  • A Formula is set up to trigger when the Information Collection Completed column is set to Yes
  • Multiple conditions are checked from the Questionnaire related columns and for each Risk identified a Library Calculation Formula is executed
  • The Library Calculation Formula creates a Risk record based on the parameter passed from the calling Formula - this allows Risk records to be created from multiple Formula triggers but have the details of the risks contained in one Formula 
  • A Formula also triggers on the create of a Risk record which maintains a total count on the Pension Transfer Request record
    • The Red and Amber risk counts determine how the Business Process Flow can be completed
      • If there are any Red Flags the transfer must not proceed
      • If there are any Amber Flags the transfer is referred to MoneyHelper

 

Business Process Flow

A Dataverse Business Process Flow determines the high level path depending on attributes of the Pension Transfer request - some of these attributes are determined by North52 rules.

Power Pages Portal Forms

Power Pages forms are used to collect information about the Pension Transfer.

North52 business rules are used for:

  • Progress Bar using Quick Tile custom template
  • Showing form notification and hiding/showing sections and fields

Power Pages Forms with North52 Business Rules Engine

Power Pages form detailed questionnaire

North52 business rules are used for:

  • Progress Bar using Quick Tile custom template
  • Hiding/showing sections and fields
  • Field validation

Power Pages Forms with North52 Business Rules Engine

North52 Formulas

Once the questions have been submitted North52 rules process the results and create Red and Amber flags. 

Evaluate Results Formula

  • Decision Sheet 1 - Information Collection Completed
    North52 business rules engine for Microsoft Dynamics 365 decision sheet - evaluate results 1
  • Decision Sheet 2 - Red Flag Rules
    North52 business rules engine for Microsoft Dynamics 365 decision sheet - evaluate results 2
  • Decision Sheet 3 - Amber Flag Rules
    North52 business rules engine for Microsoft Dynamics 365 decision sheet - evaluate results 3

Create Red and Amber Flag Records Formula

The creation of the Red and Amber Flags can be triggered from multiple places (e.g. the Questionnaire evaluation rules above) or from other trigger points. For this reason they are set up as a Library Calculation Formula. 

  • Decision Sheet 1 - Create Red Flag records
    North52 business rules engine for Microsoft Dynamics 365 decision sheet - create red flags
  • Decision Sheet 2 - Create Amber Flag records 
    North52 business rules engine for Microsoft Dynamics 365 decision sheet - create amber flags

Risks Displayed to End User

The Red and Amber flags are clearly displayed to the end user in the model-driven app - because of the risks identified this application will be refused.

North52 business rules engine for Microsoft Dynamics 365 decision sheet - Risk displayed in Model Driven App