At some point during the year your credit union's audit firm may contact your credit union to perform a member account verification. This involves sending statements with a special message and unique return address, so that members respond to the auditing firm rather than the credit union directly. Here are some important tips to ensure your audit is successful: CU*Answers cannot change your credit union's return addresses on statements. CU*Answers uses custom statement envelopes for a  More...

At the time an email address is being recorded on a member's account, either in CU*BASE or via Online Banking, e-statement enrollment, bill payment enrollment, etc., the system will check the address entered and provide error messages if the following rules are not followed: Do not allow a period or @ in position 1 of the email address The last character in the address must be a letter (a-z or A-Z) Do not allow two periods in a row Do not allow two @ symbols within the address Must have a pe  More...

The most common reason that a member is not receiving their text banking verification code is that they are blacklisted by their provider . To resolve this, the member needs to contact their cellular provider and have the block removed.

If there is no image found for the account, you can click the image not found graphic on the Verify Identity screen to access the Secondary Names screen. On that screen, you may need to uncheck Photo ID on File to reveal a Scan button. Use this to scan the new ID. If there is already an image saved and you need to replace it with a newer ID, back up to the Who are You Serving screen. From there, access the Secondary Names screen. Then follow the directions above to replace the photo ID.

If you are showing ID images right on the Xpress Teller screen, and the search doesn't locate an ID for that member's SSN/TIN, then an Image not found graphic will appear in place of the ID. You can click that image to access the Secondary Names Inquiry screen, where you can view other IDs for joint owners/co-borrowers or scan a new ID for the member or any other name listed on that account.

Prior to the 16.10 release, the SSA began using multiple Company IDs, and it was recommended that credit unions consider using Automated Funds Transfers (AFTs) to handle distributions. Beginning the 16.10 release a new cross-reference system will be implemented that will automatically funnel all incoming company IDs from the Social Security Administration and treat them as if they came from one, consistent company ID we’re referring to as the “Primary ID.” With the changes ma  More...

OFAC is defined in the NACHA Operating Rules and Guidelines Chapter 3, Section 1 pages OG15-OG21. There is a difference between OFAC procedures for ACH transactions and the verification of parties with which a financial institution does business. For ACH purposes, only the addenda information on cross border transactions (IATs) require an OFAC scan for both RDFIs (receiving depository financial institutions) and ODFIs (outgoing depository financial institutions). As far as OFAC compliance goes  More...

With the 16.10 release a new cross-reference system was implemented that automatically funnels all incoming company IDs from the Social Security Administration and treat them as if they came from one, consistent company ID we’re referring to as the “Primary ID.” In cases where the Depositor ID is the same, for example a husband and wife, these ACH transactions will be handled by the same master ACH distribution record under the Depositor ID since duplicate Depositor IDs are no  More...

Prior to the 16.10 release, the SSA began using multiple Company IDs, and it was recommended that credit unions consider using Automated Funds Transfers (AFTs) to handle distributions. Beginning with the 16.10 release a new cross-reference system will be implemented that will automatically funnel all incoming company IDs from the Social Security Administration and treat them as if they came from one, consistent company ID we’re referring to as the “Primary ID.” With the chang  More...

There is an option when you are creating the G/L through Tool # 202 Chart of Accounts where you can choose to exclude the G/L from the Trial Balance G/L Verification. Once that is added you will no longer see the section highlighted in red, and your G/L will show in balance. See the question below for directions on how to exclude a G/L.

There are two primary reasons we charge this fee: Our belief that we should do our best to keep our fees down when credit unions do not earn. This is why, for example, It's Me 247 mobile web is offered free to our credit unions. It's also behind our constant pressure to reduce fees where CUs have no basis or belief they can charge for a defensive, relationship service. Charging for these services in this manner fund other areas where the direct expenses cannot easily be identified wi  More...

The Name ID verification is designed to provide an immediate double check that the correct account number was entered on several entry screen in CU*BASE. CU*BASE can be configured to display a hint as to what should be entered. Whether or not the hint is displayed depends on how the individual workstation configured. Follow your credit union policies and procedures to determine if the hint should be displayed. To display the hint, use Tool 326 CU Hardware Configuration , select Terminal/Wo  More...

For the individual scan, the program looks at last name first. If the first name happens to be spelled incorrectly, the name will pass the scan. The first name is only checked if there is a hit on the last name. The batch scan of your entire membership does a more thorough verification, checking last name and first name independently.

The NSF Statistics Dashboard (Tool #557) will track this information for you automatically. It is separated into the NSF category and the Courtesy Pay Category. Credit unions are using this dashboard to help predict averages of NSF/Courtesy Pay fee income and also to track how many members may be using the service. You can click on any of the origins (listed in blue text) and you can drill further to members who had more than X transactions in a specific month. There are a lot of graphical oppor  More...

Special care should be taken when adding distribution records for a member who has more than one deposit coming for the family from the same institution. Take the time to research the member ACH records using the ACH inquiry screen, and if there isn't enough information on this screen, go to CU*SPY and find the PACXTB report to review the ACH detail. For example, the Smith family receives three ACH payments for Social Security benefits: one for the husband, John, one for the wife, Mary, and   More...

When you get the check copy and verify beyond a doubt that it was not the intended biller who cashed the check, re-open the case with Fiserv. Explain that the check was wrongfully deposited, explain your verification processes, and ask for Fiserv's assistance with a refund to the member. They will contact the Federal Reserve and work to get the money back. This can only be done with a Corporate Check. If it was a Member Draft, then the credit union would need to assist the member in reclai  More...

The Social Security Administration uses several company IDs for its ACH transactions. Previously two recommendations were made to handle the changing Company IDs, namely to create records for all possible Company IDs with duplicate distribution records or to transfer the distributions with the Automated Funds Transfers (AFT) system. With the 16.10 release a process was implemented that will no longer require either of these complicated solutions. Going forward only one Company ID will need to   More...

One method is to use the the Begin +/- and End +/- fields (Toool #640 Print Financial Reports) to define a period for the report that is specific number of months before (-) or after (+) the Current Period Begin defined. Therefore with the Current Period Begin of January 2017, as shown in the screenshot below, the first column defined is reporting a period of January 2018 (plus 12 months from the Current Period Begin ) to December 2018 (plus 23 months from the Current Period Begin ). And the sec  More...

Message Types are utilized by CU*BASE to determine what action is to be taken for this transaction. The original message type is the incoming message received by CU*BASE from your vendor. Depending on the Message Type received by CU*BASE, the system could perform any of the following type of transactions (this is not an all inclusive listing): Balance Inquiry Request for Authorization of Transaction Advice of Authorization (Vendor/VISA/MC approved) Transfer of Funds Request Reversal of Transac  More...

The information sent to the bureau was not an exact match, but based on the information provided (including name, address, DOB, etc.), the bureau returned a match to the correct SSN. CU*BASE is set up to pull a credit report for applications that are sent from online banking based on the applicant's consent to have their credit pulled within the application. There is not a way for the SSN to be verified as correct or not at the time of the application, but the credit bureau is able to do fur  More...

2501 There are several reasons why the LGLACT member balance does not ever match the G/L balance. When a loan is charged off, the member balance is credited (offsetting the general ledger to which the loan reports) and the offsetting entry is to a general ledger account 719.00. The loan remains an active account on the system which no longer accrues interest but does retain the ability for staff to apply payments. When payments are applied, the member account balance is reduced and the 719.00   More...

With the 16.10 release we have developed a new cross-reference system that will automatically funnel all incoming company IDs from the Social Security Administration and treat them as if they came from one, consistent company ID we’re referring to as the “Primary ID.” Refer to the linked to Answer Book items for more information about this feature. At implementation of the release two reports were placed in your credit union’s HOLDxx OUTQ. The first, CNV40003, lists all  More...

The following Reason Codes are used with the A2A processing: 00 - Payment accepted 01 - Invalid bank routing number 02 - Invalid checking account number 07 - Algorithm code invalid 08 - Invalid alternate company 09 - Missing or incomplete data in URL 10 - Invalid date format 11 - Invalid access number 16 - Bad password 17 - Invalid User ID 18 - Transaction already processed 19 - Account info does not match 20 - Invalid credit card number 21 - invalid credit card expiration date 22 - Credit card   More...

Just like the existing way that IDs are searched, the amount of time it takes to loan an ID onto the screen will vary depending on things like your network speed, whether you use the CU*Spy vault or your own in-house vault, what the level of traffic on the system is at any given time, and myriad other factors that may even vary from one moment to the next. Based on early feedback from beta-test CUs and early adopters, though, we're excited to see that the new technique is at least comparabl  More...

For a forced password change, the security table can be flooded with a forced password change status and the member would have to change their password the next time they log in. The hold password would remain in the system until the member updates their password. There is not an automated process for this on CU*BASE. A programmer will have to do this manually via a custom programming request. A custom request would need to be submitted and an estimate for leadtime will be provided at that time.  More...