Skip to main content

Feature Description

  • Update the Tax Information Request form and its components. This includes the questions and the look/feel of the portal navigation.
  • The existing List feature, where Users can add multiple Contacts and perform a group action, has been extended to include a new “Duplicate Tax Information Request” button. When clicked, the specified Tax Information Request will be cloned and assigned to each member of the List.
  • Simplify the “Assumptions” tab of the Tax Information Request to improve the UX and make it more likely that a Client will pay attention and respond accurately.
  • Develop a new form on Practice Gateway for gathering tax information that can handle multiple configurations.
    • Allow Users to specify a configuration choice which will impact both the User viewed and Client facing forms.

Dependencies

Data protection implications, considerations, and dependencies​

  • Business data is accessible to Users (in the App) with the security roles “Business Tax user – client security” or “Business Tax user – global".
    Note that the usual client security behaviour applies, and Users with either of these security roles will only see data belonging to Contacts that are in the same Team as the User.
  • Business data is accessible to Clients (in the Portal) with a Connection to the business contact if the Connection Role is set to either “Business Tax – Data Approver", “Business Tax – Data Provider” or “Business Tax – Read Only”.
  • Business data can be exported from Practice Gateway as a PDF by saving a local copy of the "Tax Information Request Summary” report.

Confirmation of dependency map check:
Signature: ____Gavin Thomas
Date: ____05/06/2023

List of dependencies as per the dependency map:

  • List
  • Tax Information Request

Data protection implications, considerations, and dependencies​

  • All data included in a Tax Information Request row will be replicated and added to the new clone rows.
  • If a Contact is included in the List then they will have access to this copied financial information.
  • Care must be taken to include the correct Contacts in a List.

Confirmation of dependency map check:
Signature: ________Gavin Thomas
Date: ________27/07/2023

List of dependencies as per the dependency map:

  • Tax Information Request components

Data protection implications, considerations, and dependencies​

  • None

Confirmation of dependency map check:
Signature: ________Gavin Thomas
Date: ________09/08/2023

Practice Gateway Power App – User Interface

  • New button and related fields added to List form.

Practice Gateway Portal – Client Interface

The question text has been condensed into a single line. Responses have been relabelled to “Agree” and “Disagree”.
The responses default to “Agree”, and a new “Assumptions Confirmation” field has been added that is mandatory.

Functional Requirements

A list and description of the functional requirements:

  • Update the Tax Information Request (TIR) questions as described in requirements documentation.
  • Convert TIR from an Advanced Form to a series of Basic Forms, i.e. to enable a clickable navigation bar.
  • Integrate TIR with the Modules & Features logic, so it can be enabled/disabled at environment level.
  • Swap position of “Other Items” and “Assumptions” pages.
  • New “Start” page added with instructional text for client.
  • When opening TIR, go to “Summarise” page unless no data is entered – in which case go to “Start” page.
  • Questions do not need to be set to “Complete” to submit TIR.
  • Clients can respond to a question with “N/A” as well as “Yes” or “No”.
  • “Advisor Notes” field added to each question, only shown in the portal when populated.
  • “Assumptions” page accordion to be removed.
  • Add a “Mark All As Complete” button.
  • Add new button “Duplicate Tax Information Request” to List form.
  • Add fields to List form that will unlock the new button and pass information to it when clicked.
  • Build Flow that will duplicate a specified Tax Information Request and assign the duplicates to the specified Contacts.
  • Ensure the Flow handles any child schedules (e.g. “Entertaining” rows).
  • Build a JavaScript library to be called by the new button that will run the Flow and receive its data.
  • Hide the section headers to remove the accordion styling.
  • Change the question text into statements that begin with “I agree”.
  • Remove the pop-up text based on the selected response.
  • Change the response text to “Agree” and “Disagree”.
  • Remove the Notes, Advisor Notes, and Documents areas for each question.
  • Add a Notes, Advisor Notes, and Documents section at the foot of the page for the “Assumptions” section as a whole.
  • Conditionally display Advisor Notes when populated (in the App by a User).
  • Conditionally display the Notes and Documents when an assumption question is set to “Disagree”.
  • Add info buttons as requested.
  • Default all question responses to “Agree”.
  • Add a confirmation question that requires the Client to confirm they have reviewed the other questions.
  • Make all questions non-mandatory except for the new confirmation.
  • Ensure that the “Assumptions” navigation bar item is only highlighted in green when the confirmation is set to “Yes”.

User Interface – Model Driven App​

  • Allow a user to create a Funds Tax Information Request.
  • Allow a user to specify the template for the Funds Tax Information Request.
  • Depending on the template chosen, different tabs and questions will be available in the Model Driven App.
  • A list and description of the changes to the Practice Gateway Model Driven App.

Client Interface – Portal​

  • Allow a client to log into the portal and have access to the Funds Tax Information Request.
  • The Form tabs and questions available will be managed by the template configuration that a user has selected.
  • Consolidation of Tax Forms to be accessed by a singular Provide Information page, following the same layout as Documents and Document Approvals.
  • A new Tax Form for Funds Tax Information Requests that functions in a similar manner to the US Tax Return.

Non-functional Requirements

A list and description of the non-functional requirements:

  • Newly created Tax Information Request rows are set to status “Created” (so they do not appear in the Portal immediately).
  • Feedback notifications to be displayed to User when waiting for background processes to finish creating the Tax Information Request rows.
  • Tax Information Requests can only be created for Contacts with Client Type “Corporate”.
  • Maintain the existing form design for consistency.
  • Ensure the logic monitoring the form progress is preserved.
  • Make the “Assumptions” tab as simple to use as possible and its content perfectly clear to readers.

Client Requirements

A list and description of the client requirements:

  • Can navigate TIR by clicking on the progress bar.
  • Can submit TIR without marking all questions as “Complete”.
  • Can set all questions as “N/A”.
  • See a Start page when opening for the first time.
  • See a Summarise page when opening an in-progress TIR.
  • Clients should be able to quickly review the “Assumptions” page.
  • Clients should only have to click one button to confirm they approve the assumptions (assuming that they do not disagree with any of said assumptions).

User Requirements

A list and description of the user requirements:

  • Can add Advisor Notes to each question that are shown to the client.
  • User can select a Tax Information Request to be duplicated.
  • User can specify one or more Contacts to receive the duplicated Tax Information Request rows.

Risk Assessment​

Potential risks within this project are:

  • No impact to existing RPA schedules or Dataverse data, as TIR is not yet in use.
  • Contacts can be mistakenly added to the List, and thereby receive information copied from another Contact’s tax information.

Impacts​

Data Protection​

List of potential data protection impacts:

  • No existing data will be impacted.

Data Privacy​

List of potential data privacy impacts:

  • No existing data will be impacted.

Documentation​

Dependency Map Updated​

List of updates:

  • Magic Numbers & Strings (Web view)

Usage Notes​

  • Create a List. In the “Members” tab, add one or more test Contacts using the “Add” button. On the “Summary” tab, set “Service Line” to “Business Tax”. A new field “Duplicate Tax Information Request?” will appear once the Service Line has been set.

  • Set “Duplicate Tax Information Request?” to “Yes”. A new section “Duplicate a Tax Information Request” will appear. Populate the lookup field “Tax Information Request”.

  • Save the form. If a Tax Information Request row was specified in the lookup field then a new button will appear in the command bar. Click “Duplicate Tax Information Request” to begin the process.

  • A notification will pop up to inform you that the Tax Information Request is being duplicated. Once this has been completed, a different notification will appear to confirm the process has finished. Note that the List will be deactivated once the process has finished.