Before you implement VerifyBiz

✅

Purpose:

• Why are you implementing VerifyBiz (e.g. fraud prevention, payment error reduction).

✅

Objectives:

• What are the specific business-related objectives you want to achieve? (e.g. reducing admin from misdirected payments, lowering incidence of fraud, reducing direct debit failures)

✅

Measurement:

• How are you going to measure whether VerifyBiz is fulfilling its purpose and objectives?

✅

Scope:

Which processes will VerifyBiz be applied to? e.g.

• Onboarding of customers, suppliers or employees,
• Adhoc changing of existing account details,
• Setting up direct debitor accounts,
• Annual, quarterly or monthly account check controls.

✅

People:

Who will be impacted and in what ways? e.g.:

• Subjects of the CoP check
• Team members managing or using data
• Management and leadership
• Technology teams
• Helpdesks and support teams
• Third party or inhouse systems designers and developers

✅

Policies and compliance:

Are there governance policies that should be considered in this implementation? e.g.

• Technology policies
• Procurement polices
• Privacy polices
• Compliance obligations

✅

Primary processes:

How will the CoP check change the process(es) it’s embedded into?

• How does it change the user journey?
• How does it change the staff journey?

✅

Wider impacts:

• Thinking about your stakeholders, how does the implementation of the new system impact on other business functions or processes? e.g. payment processing, monthly reporting, IT incidence handling.

✅

Conditions:

• What will trigger a CoP check?
• Will there be exceptions where a check won’t be required?

✅

Outcome handling:

• For each possible result, (Match, Partial Match, No Match, an exception), what is the next step?

✅

Rule impacts:

What are the impacts of these rules? For example, on:

• ­User journey / customer experience
• Data handling
• Inclusivity policies

✅

Reporting:

• What do you want to report on?
• What data do you need to extract from your systems?
• What data will you extract from VerifyBiz*?
• How will you use this data to create the insights you need?
• What systems will you need to use to create effective reporting?

*GetVerified has limited reporting capability. 

✅

Stakeholders:

How do communications change for each stakeholder*?

• Subjects of the CoP check
• Team members managing or using data
• Management and leadership
• Technology teams
• Helpdesks and support teams

*We have stakeholder comms support here.

What do you need to communicate before the implementation of the CoP solution?

Before, during and after each possible result outcome? For example,

• Privacy obligations prior to performing a check
• Post the check, if the outcome is a:
  • Match
  • Partial Match
  • No Match
  • An exception result
• Disputes or escalations
• After the implementation to communicate success and progress?

✅

Training:

• Who needs to be trained?
• What do they need to know?
• When do they need to know?
• What materials and resources do they need to support them with this change?

*GetVerified's training capability is specific to the use the of tool and doesn't cover training in business-processes outside of tool use.