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

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

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.

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

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.

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.

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

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!

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.

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.

Make sure all monies is transferred from the branch vault to the bank (sell teller drawers to the vault first, then the vault to the bank) using Tool #32 Teller/Vault Cash Transfers Inquiry . Finally, suspend the branch using Tool #176 Branch Office Configuration . Once the branch has been closed for a period of time (we recommend after 90 days), you can move the members assigned to that branch to another branch based on where members are now performing the majority of their transactions.   More...

Previously, credit unions used Code 38 for “Return to Maker”, but this code is no longer available in the system. This change was initiated by a Reg CC change in 2018. Now, if you are presented with a situation where you need to return a check to another institution, it is recommended that you use one of these codes to clarify the reason for the check return. Some codes allow you to make the change in CU*BASE. Others require that you contact your Check Item Processor. Read below for   More...

There are two methods used to track delinquent loans for reporting purposes in CU*BASE: Method One (for Collections tracking) We have always tracked delinquency in two separate fields for “Months” and ‘Days” in the member files. When a loan is 30 days delinquent, it shows as “0 Months, 30 Days” delinquent. When a loan is 31 days delinquent, it is “1 Month, 0 Days” delinquent. A month is always considered 30 days regardless of the actual number o  More...

There are several steps in removing a member's Social Security number: 1) Run a global search to see what types of relationship codes the SSN has with your credit union. 2) The first relationship codes you will want to review are the 'CB' or 'JI' which mean the non-member is a co-borrower and/or joint owner on the account. They need to be removed first. To remove them, launch Tool #3 Open/Maintian Memberships/Accounts, choose Update member information then Joint owners an  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...

Below is a sample of an CU*BASE/Xtend shared branching receipt showing the name of the member's home credit union: In this sample ABC Testing Federal CU is the member's home credit union; their CU# is 123 and their CUID is XX. For national shared branching, you’ll see a section that shows “CO-OP Shared Branch Transaction” and the financial institution’s name as well as the tran seq# that we receive from Co-Op, like this: NOTE: When these receipts actually   More...

This comes from the Workstation Device Configuration in CU*BASE. To view or change this: Launch Tool #326 CU Hardware Configuration Select Terminal/Workstation In the list of workstations, locate the ID of the workstation you are looking up and double click on it (or just type the ID and press Enter) This will open up the terminal's configuration in CU*BASE. In the middle is the list of default printers where your documents will print: General Printer - this will be the printer to which a  More...

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

CU*BASE uses phone numbers that are stored in the MASTPH file when generating card activation information to send to vendors on initial card orders. The numbers in MASTPH are determined by the label/flag applied in Tool #3 Open/Maintain Memberships/Accounts or Tool #15 Update Membership Information as follows: Nighttime # - primary phone number sent to vendor and defaulting into the Card Activation field when ordering a card. Daytime # - secondary phone number sent to the vendor. Mobile –   More...