Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, 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 Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative 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

Status Not under consideration
Created by Jason Singleton
Created on Feb 26, 2021

Unable to edit Bank Sort Code

At present, once to create a Bank Account evidence you cannot edit the sort code.

Customer Name Scottish Government
  • Attach files
  • Guest
    Reply
    |
    Apr 7, 2021

    Hi Jason,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:
    * Rather than the ability to be able to edit the sort code of a bank account, due to the nature of customizations made on your project including the inability to verify bank accounts that have been end-dated, verifications should only be enforced on the latest active bank account, not on end-dated bank accounts.

    We acknowledge the benefit of your suggested enhancement however other features are taking a priority in our planning at this time.

    Although we will not be addressing this item in the near term, your suggestion will be available for future consideration.

    This request will be closed and we will not be taking any further action.

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

    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |
    Mar 22, 2021

    Hi Jason,

    Thank you for providing the additional information requested. Within the next 30 days, we will review the details you have provided and inform you of our analysis and decision.

    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Jason Singleton
    Reply
    |
    Mar 22, 2021

    Hi Shane, sorry for the delay in responding to this. I checked with the Client and received the following response:

    Currently in live, verifications are raised on the creation of bank accounts. However, when a bank account is created, the sort-code field is in-editable so if an invalid one is entered, the client advisor has to end date this bank account evidence and create a new one. However, the verification for the existing end dated bank accounts are still there and cannot be verified with modulus checks as they are invalid. Client Advisors cannot delete the bank accounts as they don't have privileges so the Finance Ops team has to delete them or the verifications are cleared with SQL. Both options aren't ideal and a new permanent solution needs to be designed.
    The agency cannot approve a case with a pending verification even if on an end dated bank account, so they need to stop this mandatory verification as its blocking payments. Verification should only be enforced on the latest active bank account not the old ones.

  • Guest
    Reply
    |
    Mar 5, 2021

    Hi Jason,

    We have reviewed your enhancement suggestion and require more information to properly understand the issue and the business scenario you are trying to support.

    We would like to get further details about when you are trying to edit the sort code, i.e. before a first payment is generated when the sort code can still be edited or whether you are trying to edit a sort code for a bank account that has already been used for payment.
    Also, why do you have a requirement to delete a verification for a bank account that has been end-dated, even if the verification remained outstanding?

    Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.
    Thank you,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Guest
    Reply
    |
    Feb 26, 2021

    Hi Jason,

    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 in order to complete our evaluation, we will send you a request for more information.

    Thank you,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.