Bank Secrecy Act Report
|
Screen ID: Screen Title: Panel Number: Report Name: |
LBSAFIL-01 Bank Secrecy Act Report Selection 6492 LBSAFIL |
|
Access this screen by selecting Tool #633: Print BSA/SAR Activity Report.
Helpful Resources
Refer to theBank Secrecy Act Monitoring Tools booklet.
Screen Overview
This report, along with the online inquiry and automatic daily report, is one of the tools CU*BASE provides to help your credit union satisfy its responsibilities to the Bank Secrecy Act requirements. This report pulls data from the same summary and detail files (BSAMAST and BSADET) that were generated for each individual date and included on the daily report (LBKSC3).
-
NOTE: The main difference between this report and the automatic daily report is that here you can include multiple days worth of data, and you can limit the report to a single SSN/TIN. This can be helpful if you want to look for a pattern of suspicious activity over time for a particular member, or review a month’s worth of activity at the same time. Otherwise the data shown will match what was on the daily report for the date when each transaction was posted.
Use this screen to define which records should be included on the report. Remember that data is stored for 6 months. The report will be sorted and grouped by SSN. If a single member has multiple membership accounts, the system adds all activity for all of the member’s accounts to determine inclusion on the report.
A report sample is shown below, followed by some tips for reading the data on the report.
Looking for a more comprehensive report that includes joint owners, to help you see signs of structuring? Try the BSA/SAR Structuring Report instead, available via Tool #1990 Print BSA/SAR Structuring Report.
How Do I Save/Retrieve My Report Settings?
For more details on setting up this feature, refer to the Automating Reports and Queries booklet.
This report can be used with the “Report Scheduler,” a time-saving automation feature that allows you to select and save the filters you use to run several commonly used reports and then set these reports to be run automatically by our operations staff on the first of the month. Or you can save the settings and run them manually by yourself at any time.
To save your report settings, first select your filters, including printer (can be a physical printer or the HOLDxx or MONTHxx OUTQs) on any of the selection screens for this report. Then select Save Settings (F24). On the next screen name your settings (we recommend adding your name!), and designate whether you wish to run this manually or if you wish for operations to run the report. At a later time, use Retrieve Settings (F23) to populate the screen with the settings you have saved. You can also edit your settings using Retrieve Settings (F23). All saved settings can be viewed on the Report Automation: Standard Reports screen.
Tips for Selecting Date Settings for Report Automation
Unlike most other reports, this report is generated from a file that retains 90+ days of data (current + past 3 months) in a single file (BSAMAST). It also has the unique property in that the 90-day file might not match the EOM snapshot file, even for the same date range, because you can delete items from prior months after a new month begins; if looking at April data during June, one might see 10 items dated in April, but if looking at it as of the April EOM snapshot there might be 12 items, because 2 items dated April were actually deleted early in May.
We recommend that if you want to automate the report, you use one of the relative date options (Previous Calendar Week or Previous Calendar Month, specifically) rather than the absolute date options(Specify Data Range and One Month from Archive, specifically), as selecting the absolute options won't adjust the date range automatically during Report Automation, and therefore you'd get the exact same report every time and eventually no data at all as the data falls off in the usual purge cycle.
Additionally, the report automation feature has an option where you can request the report to be pulled as of either Current or Previous month-end. Report Automation will obey these settings, and if the report is set up using one of the relative date options, automation would simply calculate backwards from either the current date OR the prior month-end date.
Example 1:
Selected Date Range Past 30 Day Period (P) and Automation Record set to "Current month"
The report run on June 10 would include data from May 9 - June 9, pulled from the current BSAMAST file in FILExx.
Example 2:
Selected Data Range Past 30 Day Period (P) and Automation Record set to "Previous Month"
The report run on June 10 would include data from April 9-May 9, pulled from the May EOM snapshot (EBS0517).
In summation, we recommend that for report automation, the best option is Previous calendar month (M). Other relative date options may also work, however, it will complicate the data that you see on the report. For example, using Previous Calendar Week (W) would work, but would have to be set up with multiple different automation cycles since automation only runs once per month on a designated day. All ranges will work when running the report on demand, and remember - you can save your report settings without necessarily automating the report.
Field Descriptions
|
Field Name |
Description |
|
Date Range |
Choose one of the following:
|
|
SSN/TIN |
If you wish to view activity for only a specific member, enter the SSN/TIN here. (All memberships under this SSN/TIN will be included.) Leave the field blank to include all members. |
|
Export to File |
Check this to create a file containing the records generated by the report. A window will appear; you can choose either to create a file that ready for Member Connect (contains account base only), so you can communicate instantly with these members via email and online banking messages, set up a marketing outreach via mailing labels and selective statement inserts, and track the responses via a telemarketing Tracker. Or you can choose to export all report data into a file that can be used for further analysis with CU*BASE Report Builder. |
Report Sample
The “SB ID” column in this report indicates that the transactions took place at a shared branching location (this includes Xtend branches as well as national shared branch locations, if applicable to your credit union). This way you will be able to review member transactions at other locations just as you would work transactions posted at your own branches.
If your configuration specifies calculation method 1 (combine $$ in and $$ out), the report will simply list all records for the SSN. Only members whose combined money in and money out total exceeds your configured level will be included on the report.
If using calculation method 2, (separate $$ in from $$ out), the report will show up to two totals per SSN: one for the total money in (if it exceeds your threshold), and another for total money out (if it exceeds your threshold).
Remember that only the transaction types flagged in your BSA configuration will be included in the total calculation and shown on the report. The report will list all of the individual transactions that added up to the total which was compared to your configured threshold.
The “CASH TRANS RPT” columns on the right edge of the report will be marked as follows:
ALRT An asterisk will appear if the total transaction exceeds your configured CTR tolerance.
FORM An asterisk will appear if a CTR form exists for this SSN for this date.
SUBM An asterisk will appear if a CTR form exists and has been marked as submitted/locked.