We call this process “Roving Teller.” First give the teller access to the appropriate vaults in their employee profile (see below). Then when the teller activates his or her drawer via Tool #1 Teller Line Posting , the appropriate vault for the branch where the teller is working will be selected automatically. ( Tool #1600 Xpress Teller will do the same thing, but activation is done behind the scenes automatically.) NOTE: If the teller activates their drawer through Tool #33 Tel  More...

If your credit union uses the check holds configuration, holds for shared branch members will obey the configuration from the teller credit union and will completely ignore the electronic deposit hold override flag setting.

This particular issue arose due to N\A being listed in the driver's license and code word fields. With these indicators, the program is getting confused because \ is seen as a field separator rather than a text option in the field and is causing the program to read the fields incorrectly. This is why the account was being listed as invalid. These fields will need to be updated to include either the actual data or simply be left blank.

The reason the M/R code is not writing out with the teller's branch number is because it is being done through Phone Operator. Phone Op is actually posting to the member branch regardless of this configuration. The transaction is a bit different than teller because it’s built with a TRANS record with a direct connection to the offset GL rather than a teller audit key with an EOD GL interface for misc receipts. The trans record posts the member branch to both the member and teller bra  More...

When one of these options are selected, only those transaction types will appear in the results dashboard. You may select only one of these checkboxes (e.g., you may not select to include only shared branch transactions and only RDC transactions). When one of these options is selected, you cannot also select specific origin codes to monitor. Shared Branch Transactions : The pattern will monitor only shared branch transactions. RDC Transactions : The pattern will monitor only RDC transactions. P2  More...

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...

You can change the setting of the Allow shared branch trans field on the member's master record. When that member's account is selected at one of your shared branch locations, CU*BASE will display a message that shared branch services are not available to that member. (Make sure all your shared branch partners understand what to do when their tellers encounter this message!) To update this setting, use Tool #15 Update Membership Information. (The flag appears on the final update sc  More...

Yes! It is included in the CU*BASE product at no extra charge and provides a full Teller interface between two CU*BASE online credit unions, whether part of the Xtend Shared Branch network or just a credit union-to-credit union contractual arrangement. That means daily automated entries to your settlement and fee G/Ls. Some credit unions use it for additional service to their members or it can be a contigent disaster recovery configuration. The extent to which the credit unions cooperate is full  More...

The COOP National Shared Branch interface (CUSC/FISC) currently supports check disbursements but not money orders. Following is a technique that was shared with us by a credit union to offer shared branch members the ability to purchase money orders. Locate the account from which funds are coming, and make sure enough funds are available for both the money order and the fee. Run an OFAC scan and complete any paperwork and obtain signatures your credit union requires according to policy. In   More...

The CU*BASE BSA monitoring tool does include data about shared branch transactions conducted via its own internal shared branch tool (includes Xtend Shared Branching). From the national shared branch networks (such as CUSC/FSCC), CU*BASE does receive Funds In amounts (separated by checks and cash) and includes those in BSA tools. (Currently Cash Out is not included, although that is planned for a future project.)

The member will be subject to the teller credit union's configured money order printing fee (the shared branch where the transaction is being performed ).

For Shared Branch transactions, the teller credit union's check hold configuration is used. Since the Shared Branch credit union received and deposited the member's check, its hold configuration was used for the transaction.

The member will be subject to the teller credit union's configured check printing fee (the shared branch where the transaction is being performed ).

The member will be subject to the teller credit union's configured check cashing fee (the shared branch where the transaction is being performed ) and the fee will post to the teller credit union's configured fee G/L. NOTE: The system will use the member fee, not the non-member fee, in these cases.

In ths case, since deposit item fees are charged in a batch at the end of the month, the member will be subject to the normal fees charged by their own credit union, regardless of where the deposits were posted.

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 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...

Yes, we currently offer an online interface with CUSC and FSCC. Acquirer provides the integration of using the CU*BASE teller system to process other members in the national shared branch credit union listing. Issuer allows CU*BASE clients to participate in the national credit union network. Refer to our Pricing Guide for associated CU*Answers costs then contact the Client Service Department to get started!

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...

No, you do not have to automatically activate OLB or ARU for new memberships. Actually, you can default all new memberships to deactivate online banking and/or audio response access until the member specifically requests it. This is highly recommended as it helps to protect members who join the credit union but never get around to using your online tools right away. These accounts may be your most vulnerable since the member hasn't set up a private password or security questions. By deact  More...

Yes. There is a technique for reviewing and manually adjusting branch allocation calculations for projected asset and liability balances. See the Budgeting with CU*BASE booklet for instructions. NOTE: The classical budgeting tools also contain a “Close a branch” function which zeros out monthly figures from your budget starting with a month you specify. But this does not affect projections for asset and liability balances used in the modeling tools.

For online credit unions, contact a Client Service Representative or complete the It's Me 247 Configuration Change Request Form (see the link below; requires Microsoft Word) to activate this flag. For self processors, this is done using OPER Tool #5356 Online Banking Configuration and OPER Tool #5511 Audio Response Configuration . IMPORTANT: If you have already activated PIB and your members have a PIB profile, remember that the ability to view ACH records is controlled by the member&#  More...

Members who apply for membership via online membership applications (MAP) can be approved as members via Tool #13 Work Online Banking Apps/Requests ; however, this does not activate online automatically. To activate online banking, use Tool #14 Member Personal Banker . Use the reset password feature to activate online banking and set a temporary password for the member. This will reset the password to the temporary password setting configured by your credit union. This will appear on the p  More...

There are two steps: Choose Which Activity is Tracked Modify your NSF Configuration (Tool #558 NSF/OD Transfer Configuration , then #1) to indicate which origin codes will be counted in the fee totals. For example, you might need to report only fees that relate to share draft postings, but not include ACH or bill payment activity, based on your interpretation of the reg. as it applies to your situation. Change Statement Print Configuration Contact a Client Service Representative and request t  More...

The Teller Activity Report (Tool #848) uses multiple files. The main files are: TEAUDT1 - contains current-day teller transactions TEAUTR - contains prior-day teller transactions In short, these are all of the transactions that have audit keys attached to them: cash withdrawals, deposits, miscellaneous receipts, checks, and in-house drafts.