It depends. Using shared branching does not automatically exclude you from the beta pool! But the specific changes being made can affect how your credit union works with others who are not part of the beta. The most common example is shared branching but might also include vendor relationships as well. This becomes an issue when the release includes changes to the database structure itself (new data in files or changes to the data’s format). CU*BASE requires that all of the data used   More...

The previous tools used for uploading and downloading to and from CU*BASE will be retired when your credit union recieves the 20.07 CU*BASE software release. For online and Site-Four credit unions, that date is Sunday, July 12. Self-processing credit unions will receive the release the following Sunday, July 19. To replace the two tools, a new tool was introduced in November 2018, Tool #1375 Data Transfers (Upload or Download) . Following the release, this tool will be the default data transfer  More...

At the time of the 21.10 release a conversion program was run to remove any relevant data that lived in the CLMLTRL table to its new home in the HMDAFDTA table. Keep in mind that if your credit union was not populating data to any of the 19 fields in the CLMLTRL table, there was nothing to transition to the new table. You may find the new table empty in this case.

When a device first connects to the iSeries, a virtual device is created - consider it a placeholder for that workstation or printer. Only one device can exist for each ID, which is why only one person can sign into a printer at a time. Throughout the virtual devices lifecycle, there are several different statuses that device can be in. Read below for some details! Workstations VARY ON PENDING - this is the default status of the virtual device. This status means the device is ready and wai  More...

Using CU*BASE to Comply with New Rules for Tracking Beneficial Ownership FinCEN has issued new rules under the Bank Secrecy Act that require financial institutions to identify and verify the identity of the beneficial owners of all legal entity members (corporations, etc.). Under the final rule, credit unions are required to have written procedures to identify and verify beneficial owners of legal entity members who open new accounts on or after May 11, 2018. In addition to identifying and coll  More...

The 21.10 CU*BASE release included a new data table for storing HMDA data fields, plus additional options for fields to record data. The previous capabilities for HMDA data were 19 fields in the CLMLTRL table, and with the release these fields were moved and renamed. HMDA data fields are now stored in the HMDAFDTA table, location FILExx (xx = your credit union ID). Below is a listing of fields that were changed . Keep in mind that the release in 21.10 also included many new HMDA fields that you   More...

Yes, in the 21.05 release this feature was removed from this dashboard as well as a couple others after evaluating it from a security standpoint. CU*BASE has controls in place to prevent employees from being able to download lists of member account numbers, names, SSNs, and other personal data without special download authority which can be monitored and controlled by the credit union. The Excel and CSV download features that appeared on some dashboards could be used to circumvent that and store  More...

Over the past year or so we worked on a project based on a request from Experian, related to how credit data pulled from Experian is stored on CU*BASE. In a nutshell, Experian requires that for credit unions who pull credit* from them, personally identifiable information about members must be encrypted while “at rest” in the database, and revealed only to authorized users – meaning CU employees, not data center support staff. What that means is that with this release we added i  More...

In CU*BASE Release 7.5 (February 2008), we released an improvement to the way Trackers are set up so that there could be a one-on-one link between a closed account record and any Tracker notes that were attached to that account. (Previously, the old Tickler system did not provide this type of link, so you would see the same tickler on more than one closed account at the same time!) For accounts closed after that change was implemented, the system now automatically ties the Tracker to the acco  More...