Curam by Merative Ideas Portal

Shape the future of Curam!

We invite you to shape the future of Curam, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Curam team to refine your idea

Help Curam prioritize your ideas and requests

The Curam team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Not under consideration
Categories Social Program Management Platform
Created by Guest
Created on Feb 9, 2025

RELATED IDEAS

Joint Bank Account with different start and end dates between clients

In Curam, a single joint bank account needs to have the same start and end date across the various participants that use this account. However, it is not ways possible for the organization to get the correct earliest start date. Also, if one participant decides not to use the bank account with the organization and needs it to be ended, due to the account being joint, it ends the bank accounts for all other participants.

E.g. James and Susan have a joint bank account and both are receiving their corresponding organization benefits to this bank.

James decides to not use this bank account for his benefits in future and provides new bank account.

When the user captures the new bank account and ends the previous bank account, it ends on Susan's account as well.


Consider privacy impact as Susan had not given the authorization to change her details even though it's shared info.

Consider benefit impacts as Susan will not get paid.

Consider if the same bank account was used amongst different type of participants like Person, Prospect, Representative, External Party etc.

Customer Name ESDC, Canada
Type of Request Idea
Market Opportunity

Common Requirement for organizations delivering multiple benefits.
CURAM:Workarounds + Proposed Solution

In OAS, a custom validation is added to ensure if another client uses the same joint bank account it cannot be ended if it causes payments impact to that client. Validation is only for Person/Prospect Person.
  • Attach files
  • Admin
    ANGELA BRADY
    Reply
    |     Mar 10, 2025

    Hi Vishek,

    We have reviewed your enhancement suggestion.

    Based on the information provided, our understanding of your request is as follows:

    • The start and end date for a joint bank account can vary across participants sharing the bank account

    We do not intend to incorporate this capability into our product as it does not align with our product strategy. We are therefore closing this request and do not plan to take any further action.


    In Cúram, the bank account record is a representation of a person's actual bank account.

    For a joint bank account, only one bank account record is created and any participants that share the bank account link to this bank account record. The bank account is not tied to one specific person but is a representation of a shared bank account between multiple participants.

    The 'From' and 'To' dates associated with this bank account (indicating when the account was active for each participant) are synchronised across all participants sharing the account. So, when you view the bank account from any linked person’s profile, you’ll see the same start and end dates. All participants linked to a joint bank account view the same account details (dates, account status, etc.), ensuring consistency across the system.

    When changes are made to the account (e.g. closing the account), it automatically impacts all participants, preventing any discrepancies or different account statuses for the same joint account. If one participant closes the joint account, it results in the account being closed for all participants. The closure is not individual; it applies across all linked participants at the same time.

    If a joint account is no longer valid then it should be closed for all participants and new bank account records can be created to represent individual bank accounts. This transition process is important because it keeps the historical record of the joint account intact while ensuring that individual bank account records reflect the accurate, current state of each participant’s banking information.

    Bank account evidence that is added for a person (whether it’s an active or end-dated account) is visible to the caseworker. This means that even if the bank account has been end-dated (i.e., it’s no longer active or in use), it will still show up in the person’s record for reference. This is important because it ensures the historical data related to the person’s bank accounts is accessible, even if the account itself is no longer in use.



    Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

    Regards,

    Angela Brady, Cúram Product Management team

  • Admin
    Graham McCrindle
    Reply
    |     Feb 10, 2025

    Hi Vishek

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.

    Thank you,

    Graham McCrindle, CURAM Product Management Team