Financial institutions need a sharp eye to spot suspicious behavior and prevent financial crimes. However, detecting fraudulent activities can be tricky, as transactions that initially appear suspicious, for example, may end up being perfectly legal or normal, and vice versa. To determine if the transaction is fraudulent or not, financial institutions must be fully equipped, experienced, and exact to flag and investigate it.
Financial crime continues to be rampant as criminals devise more and more creative ways to circumvent safety and security measures. To constantly combat this, governments around the world require financial institutions to take measures toward flagging suspicious transactions.
In the event that a transaction is suspected of money laundering or fraud, financial institutions submit a Suspicious Activity Report (SAR) to the Financial Crimes Enforcement Network (FinCEN). It is a specialized report that triggers the monitoring and investigating suspicious activities.1
Severe penalties can be pressed against a financial institution when they fail to file an SAR. SARs help law enforcement detect patterns and trends in organized and personal financial crimes, which is key to anticipating criminal behavior before it escalates.
A suspicious activity reporting system can only be as good as the content it receives. To help FinCEN investigate an incident thoroughly, it’s paramount to ensure the quality of the SAR before submission. Essentially speaking, a SAR must answer the following questions:
An effective SAR has five vital components2:
The introduction to a SAR should begin with the reason for the filing, including the type of activity being reported. It contains an overview of the SAR’s purpose, a general description of the known or suspected violation, the date of any SARs previously filed on the subject, the purpose of the SARs and any internal investigative numbers used by the filing institution to maintain records of the SAR.
After the introduction, relevant facts about the participants should be included. Provide the basic account information and the type of account being suspected. Adequately describe all information related to the suspicious activity including the employer and occupation information, relationship between the suspect and the filing institution, and the length of the financial relationship.
Account holders and respective entities should be listed. For example, demographic information of the individual will depend on the type of SAR being written and an investigation conducted for elderly exploitation or human trafficking may include date of birth. Below are the specific details that should be included in the account information:
The SAR should include details of the transactions and other information that provide cause for the suspicions of the reporting financial institution. These may include cash deposits and/or withdrawals, checks and other monetary instruments, wire or other electronic transfers, cash letters, pouch activity or other correspondent account activity, stocks, bonds, notes, casino chips or markers, and foreign currency.
Summary of all relevant information to be provided under due diligence/investigation include:
This part of the report must show a brief overview of the suspicious activities being monitored. Transaction activities and amounts must be completely and accurately presented in a CSV file or Excel spreadsheet. This part of the SAR should include:
To conclude a SAR, include a brief overview of the incident, including the amount filed on and contact information for the filing institution. The closing statement and conclusion should also provide the following information:
Depending on the specific activity and any regulatory requirements, a SAR may include other specific information. The investigating authority may also request for additional information or clarification. Either way, submitting a high quality SAR that provides all the necessary information for law enforcement to assess will help determine the best course of action.
The introduction of SAR regulations have resulted in successful prosecution of various criminal enterprises. Year after year, the volume of SARs being submitted have been increasing. Bribery and corruption are currently the top concerns most firms experience.4 But as other typologies emerge, regulators call on financial institutions to focus on filing best practices such as providing high quality SARs.
For financial institutions, it’s important to note that as financial crimes continue to increase, regulators will consequently double their efforts to monitor financial companies. In 2021, the anti-money laundering statutes were significantly adjusted, causing several corporations to be charged with penalties for violating Anti-Money Laundering laws.5 Governments do not take financial regulations lightly and persuade companies to do the same.
Financial institutions are duty-bound to report known or suspected criminal activities and must learn to go above and beyond standard security measures to prevent extensive damages. Finding the right service provider in fighting illicit financial activities is one way to protect a business and its clients. Such a partner must have the proven capability not just to provide excellent results, but to keep up with the ever-changing financial climate.
References
We exist to empower people to deliver Ridiculously Good innovation to the world’s best companies.
Services
Cookie | Duration | Description |
---|---|---|
__q_state_ | 1 Year | Qualified Chat. Necessary for the functionality of the website’s chat-box function. |
_GRECAPTCHA | 1 Day | www.google.com. reCAPTCHA cookie executed for the purpose of providing its risk analysis. |
6suuid | 2 Years | 6sense Insights |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
NID, 1P_JAR, __Secure-3PAPISID,__Secure-3PSID,__ Secure-3PSIDCC | 30 Days | Cookies set by Google. Used to store a unique ID for various Google services such as Google Chrome, Autocomplete and more. Read more here: https://policies.google.com/technologies/cookies#types-of-cookies |
pll_language | 1 Year | Polylang, Used for storing language preferences on the website. |
ppwp_wp_session | 30 Minutes | This cookie is native to PHP applications. Used to store and identify a users’ unique session ID for the purpose of managing user session on the website. This is a session cookie and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 Years | Google Analytics, Used to distinguish users. |
_gat_gtag_UA_5184324_2 | 1 Minute | Google Analytics, It compiles information about how visitors use the site. |
_gid | 1 Day | Google Analytics, Used to distinguish users. |
pardot | Until Cleared | Salesforce Pardot. Used to store and track if the browser tab is active. |
Cookie | Duration | Description |
---|---|---|
bcookie | 2 Years | Browser identifier cookie. Used to uniquely identify devices accessing LinkedIn to detect abuse on the platform. |
bito, bitolsSecure | 30 Days | Set by bidr.io. Beeswax’s advertisement cookie based on uniquely identifying your browser and internet device. If you do not allow this cookie, you will experience less relevant advertising from Beeswax. |
checkForPermission | 10 Minutes | bidr.io. Beeswax’s audience targeting cookie. |
lang | Session | Used to remember a user’s language setting to ensure LinkedIn.com displays in the language selected by the user in their settings. |
pxrc | 3 Months | rlcdn.com. Used to deliver advertising more relevant to the user and their interests. |
rlas3 | 1 Year | rlcdn.com. Used to deliver advertising more relevant to the user and their interests. |
tuuid | 2 Years | company-target.com. Used for analytics and targeted advertising. |