Building a Process to Assign an Independent Unique ID to All Membership Accounts
We have received requests for a way to identify member accounts for use with third-party marketing and other vendors, in a way that does not require the use of an account number or SSN/TIN. The idea is to provide a cross reference so that the file sent to a third party only includes the unique ID, which can then be tied back by the credit union to actual account information in CU*BASE as needed.
We are currently working on a custom project, submitted via our Developer’s Help Desk, that will populate a new table within the credit union’s file library that contains a membership number and a randomly-generated unique identifier. A credit union would then be able to request that this unique identifier be used for specific third-party exchanges, and would also be able to access the table using Query for other uses as needed.
The ID will likely include alphabetic and numeric characters so as to be obviously different from an account number or SSN/TIN. New programs will be written to perform a one-time population for all active memberships, then a new nightly routine will be established to update that file to add new memberships created that day as well as update the closed sequence number for memberships that were closed during the day.
Keep in mind:
- This identifier WILL NOT BE incorporated into any existing CU*BASE processes (screens, reports, statements, etc.).
- The credit union will be able to access this table for use with custom Queries.
- The credit union can also request this data to be used when transmitting data to third parties. Each third-party integration will be addressed as a separate project, subject to our normal fees.
- Data in the new table will be updated only once per day, at the end of each day. New memberships created that day would not be assigned an identifier in the new table until that update is complete. Likewise, any memberships closed that day would be updated to include the closed sequence number to match back to closed account files.
Once we have completed this custom project we will be deciding whether we will automatically generate this file for all CUs, or whether individual custom requests will be needed to activate the new process.
Status as of September 2024: Project #62000 was implemented in March.
Chef for this recipe: Dawn Moore
