For CU*Answers online clients, effective in March 2017 the standard online retention is 12 months for basic savings and checking accounts, and 48 months for all certificates, IRAs (shares and CDs), HSA share and checking accounts, club accounts (such as vacation, holiday, Christmas), tax escrows, and all loans. Prior to March 2017, data retention was 6 months for savings/checking, and 24 months for other member transaction history . Note that when this data is purged, it also removes the additio  More...

The Miscellaneous Receipt Monthly Analysis Report (Tool #533) can be used to print all 25 characters of the transaction description, and should be used for balance and reconciling the General Ledger.

As described in this AnswerBook item , this has to do with the unique way in which transaction records are displayed in this inquiry screen. You might get better results after you use page up or down, then use the debit/credit button. The most important thing to remember is that the date you enter is just a target, not a true filter. Because transactions must be listed in the order in which they were posted (in order for the resulting balances to make sense), the list will always “try&rd  More...

The transaction history screen is rather unique compared to other lists in CU*BASE. First, because it contains a Resulting Balance column which shows the change in the balance as each transaction was posted. Those balances are difficult to read when presented “backwards” with the most recent at the top. Second, remember that CU*BASE stores many months of transaction history. So the list you see when the screen first displays is not at the “top” of the list, but actually   More...

If you use the Retrieve e-Receipt feature from the pop-up window that appears via that function in Transaction History, you can pull the image of the original receipt you saved to your image vault, complete with whatever was shown in the account summary section at the time the receipt was originally generated. However, if you use the Print feature instead to simply recreate the receipt using the stored data, vertical receipts are currently unable to recreate the account summary showing wha  More...

Due to the limited size of the memo field in the download file, the amounts paid towards principal and interest are not included in the transaction history download.

The fields are related to Process Codes, in that they are derived from the code attached to the message received from the plastics processor (vendor, or switch). The Type you see in the initial Type column of the Activity screen relates directly to the Transaction Description when you view additional transaction details. Transaction types may not apply to all vendors. Examples of these labels are as follows: DEP (Deposit Transactions) ATM/DEP A deposit made at an ATM. ATM/DEP - including a $  More...

In many cases, the reason an opted-out member receives the non-return fee is because this transaction is a recurring payment. Recurring transactions are not covered by the Reg. E Opt In/Out requirements. You can identify this by the * after the DBT/WDR trans description on the member's transaction history. Recurring transactions are posted and fee'd even if the member is Opted Out.

Our recommendation is to suppress the transaction if it is the last transaction for that day. If there are transactions after that, do not suppress the transaction. It will affect the running balance shown on the member's statements. TIP: When you do decide to suppress a transaction, we recommend you place an asterisk (*) in front of the transaction description. When a credit union employee looks at transaction history, it will be easy to see that this transaction has been suppressed and   More...

Yes. Use Tool #918 Update Trans Desc IRA/HSA Post Codes, choose the appropriate suffix, then change the description. You can also add an additional line (secondary transaction description) in addition to the primary description. These changes will become a permanent part of the member's transaction history and will appear in CU*BASE transaction history screens as well as in online banking. Remember that changes will NOT affect member statements (including e-statements) that have alre  More...

You can use the “Print CU Checks” feature to cut a check to any vendor, including vendors that have been configured in your CU*BASE Vendor database, without creating an invoice record, if you wish. If you want that item to show up in the vendor's history (and update their YTD amount paid for the current year only ), you will need to perform a separate step to add the record manually. Here are the steps: Step 1: Printing a Quick A/P Check In a nutshell, you will be using Tool   More...

When you see one of the following symbols ($, *, #) in the 8th position of the transaction description of your EFT transaction, that indicates that the transaction was processed as a special type. You can view the transaction description either in the member transaction inquiry (account history) or via ATM/Dbt/Crdt inquiry and maintenance tools. As an example, the transaction description for a recurring debit withdrawal transaction will begin with: DBT/WDR* * indicates that the transaction was   More...

No, those statistics are only updated when the original posting program charges a fee to the member. The idea behind this stats file is to record the member was NSF when the item originally came in, regardless of why. There may be several reasons why you reverse the fee, not all of which would mean the history should be changed. (For example, say the item came in NSF but the member had called and said his paycheck was coming tomorrow, so you gave him a break and reversed the fee. In this cas  More...

Because of CU*BASE design to integrate directly to the general ledger is one of its most impressive features, the teller system needs to process as its own section. In order to discourage inaccurate or misleading transaction reversals or back-dating, the dual system segreates the teller drawer (cash) from the member transactions and balances. If the two steps are not completed correctly, the general ledger will be out of balance. Fortunately you can use Tool #31 Reverse Tran/Adjust Drawer (Same  More...

Today's teller transactions can be found in the teller drawer audit listing. This includes Outside Checks, In-House drafts, member transactions and Misc. Receipts and Advances. If you need a previous day you can view the Teller Daily Activity Report LTLAU2 found in CU*SPY.

The Process Code or PROC CODE on this screen refers to which accounts CU*BASE is going to look at to see if we can authorize the transaction or which account we are going to process against when the vendor is sending a completion. It is a 6 digit field and is broken down into 3 sections to determine how CU*BASE should process the transaction. First is an explanation of how this 6 digit code is broken down and what each segment refers to: OO FF TT in this example the first two digits would  More...

The detailed printing of a receipt for a Miscellaneous Receipt transaction is defined within the device configuration. To verify whether or not your device is configured to print the detail, you can launch Tool #326 CU Hardware Configuration. Select your workstation from the list and make sure that the Miscellaneous Expense/Receipt box is checked under the Application Receipt Printing column. Future receipts will print the detail after the option is selected.

This is the one exception to the way that Transaction Override normally works (i.e., to override for one transaction only). The override for Par Value was intended to allow a membership to be closed and all funds returned to the member, and some credit unions have large enough par values that it might require more than one transaction to handle the funds appropriately. Therefore the Account Adjustment feature does NOT reset the override flag after the first transaction is posted, so that you c  More...

The report you are looking for in CU*Spy is the LTLAU2: Teller Closing Transaction Audit Report. You can also access the teller audit via Tool #33 Teller Drawer Control/Inquiry. Select the 2-digit employee ID and choose a vault. On the second screen use the Audit button to display the Teller Audit / Change Fund Analysis screen, where you will see every transaction this teller has performed. In addition, you can enter in prior dates. The reference document My Favorite CU*BASE Reports is also   More...

The settings that control how this works are part of Tool 558 NSF/Overdraft Transfer Configuration, on the Overdraft Protection Activation screen. There are four flags: Use Negative Balance Limits for Authorizations and Use Negative Balance Limits for Posting. They control whether the member's ANR limit is added when determining the available balance amount. There are four different combinations of these flags: Authorization Flag Posting Flag Description of Result N N Negative bala  More...

The teller closing report (End-Of-Day Teller Trial Balance PTLCL2) uses the total number of audit key records as the total number of transactions. In addition, the total number of errors uses the total number of deleted audit keys. Use following link for details about teller audit processing.

The transaction description is pulling in from the account suffix description and then uses the origin code and origin type to determine if it was a payment (i.e. ACH or AFT). Those are combined to create the transaction description that appears in the member's history. For example, if your loan product is 360 MORTGAGE and a payment is made, the transaction description might be 360 MORTG PAYMENT. You can use Tool #105 Account Suffix Configuration, choose a suffix and update the trans  More...

Use Tool #918 Update Trans Desc IRA/HSA Post Codes. After entering the account number and suffix for the IRA account, you'll see a list of transactions for that account. Simply highlight the item and click the IRA/HSA Code option. The IRA Posting Type Update screen will appear showing details about the transaction and the processing code that was originally used. To change the code, click the lookup button next to the New IRA process field and choose an appropriate code from the po  More...

As a general rule of thumb, the Teller Override feature is intended to override a single transaction performed manually by a credit union employee. There may be exceptions but the intention is that batch programs which automate the posting of multiple transactions do NOT obey overrides for frozen accounts. For example, neither share draft posting nor ACH posting programs will obey the override flag (in other words, they will not post to a frozen account).

The member will see some new information on the Login History screen starting August 29, 2018. The data for this change was collected beginning August 7th. New information includes: Login Source types: iOS, Android, Desktop Browser, Mobile Browser, Loan Application, Other Login Methods: Username Password, Fingerprint, Pin, Voice, Face NOTE: If a member uses Personal Internet Branch (PIB) device registration, a duplicate login record might appear that doesn’t record the login source, IP  More...