Processing CU Parameter Configuration (1)
Screen ID: | USTR-01 |
Screen Title: | System Configuration Maintenance |
Panel Number: | 5638 |
Accessed by Tool Number: | 5435 (shortcut: PROCPARM) |
This is screen 1 of 7 used to configure information about how your credit union’s files are to be processed by CU*BASE. Use Enter to save and continue to the next screen.
IMPORTANT: Online credit unions are not able to access this screen. If you would like any of these settings to be changed for your credit union, contact a CU*BASE Client Service Representative. Self-processing credit unions should also consult a Client Service Representative for advice before making changes to these settings. Remember that some features used in a service bureau environment are not appropriate in the in-house environment.
Automated Filing of CTRs to FinCEN
This screen activates Automated Filing of CTRs (Currency Transaction Reports) to the Financial Crimes Enforcement Network (FinCEN). Once this feature is activated credit unions’ completed and locked CTR forms are sent directly from CU*BASE to FinCEN. This eliminates the time consuming step of re-entering the information into the FinCEN website. Refer to the Work with CTR Forms screen for more details on processing a CTR. FinCEN will also return a file with errors that can be worked. Refer to the first CTR fill in screen for information on how this error information can be viewed.
-
Important Note: Once the feature is activated, it will only affect CTRs going forward. CTRs locked prior to activation will not be sent to FinCEN, but will instead need to be manually entered in the FinCEN website. To make it easier to keep track of what you’ve sent and not sent, make sure you are all caught up on outstanding reports before asking us to activate the feature for you.
There is a monthly fee charge for this feature.
-
IMPORTANT: Online clients must first sign an authorization form, which is on Page 2 of this form.
-
Self-processing clients: Please contact a CRS before activating this feature.
-
NOTE: CTRs fall off of the automated log after 180 days. It is recommended that you print a copy of the CTRs for your five-year retention requirement. CU*BASE is should not be considered your long-term repository for CTRs.
Field Descriptions
Field Name |
Description |
Type of processor |
A (AS/400) is the only value allowed. This code represents whatever IBM happens to be calling its processor these days (iSeries, i5, System i, POWERi, etc.) (In the past, there were also separate codes for System 34, System 36, etc.) |
Integrated G/L |
This flag must be checked (Y). No other setting is currently warranted. We believe it was originally intended to control whether or not the automated G/L interface was done during daily processing. |
Passbooks |
The functionality of this flag is not currently warranted. It is typically left unchecked (N).
|
ICF3600 |
This flag is no longer used. It is typically left unchecked (N).
|
ICF4700 |
This flag is no longer used. It is typically left unchecked (N).
|
Automatic Processing |
|
Delinquency notice |
The functionality of this flag is not currently warranted. It is typically checked (Y).
|
CD renewal letter |
This flag is no longer used. CU*BASE currently does not support CD renewal letters (these are different from Maturity notices – renewal letters are a confirmation of the renewal when it happens). |
CTR Automated Filing |
Checking this box turns on Automated Filing of CTRs (Currency Transaction Reports) to the Financial Crimes Enforcement Network (FinCEN). Refer to the top of this topic for more information on this feature.
|
Extra Features These flags control whether or not certain programs will run during beginning-of-day and end-of-day processing. IMPORTANT: They do not control whether the features can be configured; therefore, if the CU wishes to use any of these features, these flags must be checked before setting up the configuration in order for all daily processing to occur correctly. |
|
IRA accounts |
Controls whether BOD/EOD processing related to IRA accounts will occur. |
Certificate accounts |
Controls whether BOD/EOD processing related to certificate accounts will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Open line of credit |
Controls whether BOD/EOD processing related to line-of-credit loan accounts will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Market shares |
Controls whether BOD/EOD processing related to certain types of share accounts will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Miscellaneous receipt |
Controls whether BOD/EOD processing related to miscellaneous receipts will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Utility payments |
This is no longer supported and should be left unchecked (N) in all cases. |
Government guaranteed student loan |
Controls whether BOD/EOD processing related to student loans will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Rec/check/pbk prt file |
This is no longer supported and should be left unchecked (N) in all cases. |
Service charge post |
Controls whether BOD/EOD processing related to transaction, account, and minimum balance service charges will occur. As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Stock option process |
Controls whether BOD/EOD processing related to automated stock pricing (for stock used as collateral on loans) will occur. SEE ALSO: Using Stock as Collateral for LOC Loans As there is no documentation currently available as to specifically which features are controlled by this flag, it is typically checked (Y) for all credit unions. As with any flag that is not actively used, testing should be done if intending to change the current value. |
Multiple vaults |
This flag must be checked (Y) and cannot be changed. |
Diskette magazine |
The functionality of this flag is not currently warranted. It is typically left unchecked (N).
|
Tape drive |
The functionality of this flag is not currently warranted. It is typically checked (Y).
|
Streaming tape |
The functionality of this flag is not currently warranted. It is typically left unchecked (N).
|