Cody Smith

For 2021, we met a few times to discuss PRV projects for weekly releases and upcoming major releases. We also discussed ways we can both assist in the verification process, and how we can educate the credit unions to verify their data as well. An example would be reviewing their stop pay fee income g/l after implementing a different fee for online stop pay fees. For weekly releases, we touched base and determined the things to look for. I took this information and did verification myself but also pulled in credit unions to do it as well (and so they use CU*BASE to its fullest potential). I do want to give a shoutout to Bridge CU, Cherokee Strip CU, Affinity CU, and PowerNet CU for participating and in turn learning more about CU*BASE and how it works “behind the scenes.” Not only this, but it’s a good way to implement new toolsets released into CU*BASE that may not be on their radar. I plan to involve many more credit unions going forward. We have a dashboard in Track*It that we can use to be proactive when a project is getting close to being released. This gives a heads up and prompts us to prepare to know what to look for when validating.

Keegan Daniel

The PRV initiatives powered by Earnings Edge began in the fall of 2020 with the 20.10 CU*BASE release. Prior to the release, the PRV team (Earnings Edge and production team leaders) identified projects that they believed would be best suited for review after the software is released to all credit unions. These identified projects were reviewed by the Earnings Edge team after they had been released to ensure the software is working as designed. We also developed “run sheets” for how to verify the software (which ultimately is a combination of running thru the software, reviewing the data that is created by the software, and using CU*BASE tools to verify that data is within tolerance). Projects that are flagged for PRV resources have typically been projects that may affect the income statement of our credit unions. Therefore, priorities have been placed on those projects, but we also discussed the differences between traditional software releases and on-demand software releases. Historically, the projects that have “burned” us the most are the projects that have been released outside of a traditional release because there are fewer eyes aware of the changes. We tested/reviewed multiple projects in 2021 and involved a handful of credit unions to get involved in the PRV processes with us.

Mary VanAntwerp

With the start-up of PRV in 2021, we have incorporated additional verification procedures for adjustments involving high risk programs (effect on income or high impact to member). By validating post production, it allows us to increase the number of environments reviewed where credit unions have varied product and service configurations. It has also assisted with understanding some changes that previously may have gone under the radar. PRV also highlights various functionality from major releases and follows through results in production for credit unions that utilize the feature.

Cody Smith

For 2022, continuing to use the dashboards and reports available in CU*BASE is a great way to validate data, and at the same time ensure credit unions know about the tools right in the core to monitor their operations. There have been a couple instances where I’d get back “I didn’t know this tool existed!” from a credit union. For example, for a project that works with a dividend program, we can use the dividend accrual dashboard to monitor “red flags” in the accruals over time and remind credit unions this is available to them. Personally, I plan on hosting a few events to emphasize the importance of PRV for the 2022 FY and how I can help credit unions know what to keep an eye on, etc. I believe the PRV dashboard in Track*It is very valuable and can keep us prepared at any time for what’s coming soon. It’s a team effort both internally and within the network.

Keegan Daniel

In 2022, the primary focus for PRV will be a shift to marketing our efforts and getting credit unions involved in the processes. This will include the creation of a PRV website, a webinar reviewing all PRV identified projects prior to traditional CU*BASE releases, a publication of our “run sheets” (so that credit unions can follow alongside our PRV efforts…), etc. If I were to sum up our goals for PRV in 2022, it would be for us to spend more time on marketing our efforts to the marketplace so that our customers will begin to recognize PRV as a differentiator in their choice for a technology provider. In addition to the marketing work that happens externally, the same amount of marketing will need to occur within the cuasterisk.com network as well. CU*SOUTH has already asked how they can get involved more with PRV, so I envision that we will loop CU*SOUTH into our future conversations for how they can execute PRV efforts.

I am also interested in discussing how PRV could be added to the price of custom projects completed by the DHD team. For example, a credit union pays for programming a new ACH translate within their library. CU*Answers releases the software, and the credit union assumes all is well (until its not). Therefore, we might be able to offer PRV services as a premium to our DHD credit union customers.

Mary VanAntwerp

For PRV in 2022, I expect that information learned in the past year on how to utilize some of our own tools in verification can now be passed on to credit unions, helping them to be more proactive in reviewing their own data on a regular basis in addition to any follow-up work we do in-house. We’ve built a base to communicate and watch upcoming software changes, both new functionality and changes to existing program that can be added to the PRV program. By communicating this information to clients, working with them to watch key areas and marketing PRV efforts at validation in production, we hope to increase both the knowledge of how to look at data and identify any impacts to clients before they become problematic.