Synchronize Data between Nominee and Participant Data (e.g., Delivery Pattern)

Payments from multiple cases are frequently made to a single participant who is a nominee on those multiple cases in social services organizations. OOTB, this occurs for the Registered Person and may more frequently occur for Employers. In addition, organizations set other Participant types as nominees to take advantage of nominee-specific functionality not available with third party deductions (See RFE [RFE 1 – ‘External Party’ Participant as Nominee]), increasing the frequency of a single Participant being set as a nominee on multiple cases.

Currently, Curam does not support the synchronization of payment information from the Participant to various cases on which the Participants acts as a nominee, resulting in manual effort to update individual nominee information, including delivery patterns, bank account details, and addresses.

In ESDC, there are multiple Participants who acts as nominees on thousands of cases. Changes in Delivery Patterns are expected for these participants are expected post go-live and in the years thereafter, necessitating manual updates on up to 25,000 cases rather than a few dozen participant records.

CURAM:Workarounds + Proposed Solution

The following functionality is not available, which would significantly reduce manual effort associated with updates made to participants who are also nominees on multiple cases:

1. Highest Priority - Ability to modify the nominee delivery pattern across multiple cases simultaneously – e.g., switching from Check to Direct Deposit. For ESDC

2. Ability to modify the bank account on the participant, and have this reflected across multiple nominee records for the participant

   1. Note: ESDC accepts future-dated changes (e.g., someone informing the organization of a future change to a bank account); currently, entering a future-dated change on the participant will not be reflected on the nominee

3. Ability to add a new address for a participant and end the old one, and have this reflected across multiple nominee records for the participant

   1. Note: A workaround exists for this (editing an address rather than ending an old address and creating a new one; however, this is not preferred by the customer)

      1. Note that updates like this do not permit future-dated evidence changes – e.g., the organization learning that someone will move in the future. Rather than being able to enter future-dated changes, this workaround forces the organization to wait until the day of the move to make an update.

The solution should permit updates across multiple nominee records but should not force this – i.e., some flexibility should be provided. For example – a participant may have different preferences for delivery patterns when acting as a nominee on different programs, even when they are a nominee on multiple benefit cases for that program.