Suspicious Activity Reporting Sample Clauses

Suspicious Activity Reporting. You must immediately notify us if you detect any money laundering red flags, so that CSB can determine whether a suspicious activity report (SAR) must be filed with the U.S. Department of the Treasury. Typically a SAR must be filed within thirty (30) days of the initial detection of the suspicious activity. Insurance Industry red flags include but are not limited to: • The purchase of a product that appears to be inconsistent with a customer’s needs; • The purchase or funding of a product that appears to exceed a customer’s known income or liquid net worth; • Any attempted unusual method of payment, particularly by currency or cash equivalents such as money orders, traveler’s checks or cashier checks; • Payment of a large amount broken into small amounts; • Little or no concern expressed by a customer for the investment performance of an insurance product, but much concern expressed about the early termination features of the product; • The reluctance of a customer to provide identifying information, or the provision of information that seems fictitious; • A customer’s inquiring about how to borrow the maximum amount available soon after purchasing the product; • Listing a beneficiary or payee who is apparently an unrelated third party or who otherwise has no apparent relationship to the customer; • A customer applies for a policy out of state when the same or similar product is available in his/her home state; • The customer uses an out of state mailing address; and • Any other activity that you think is suspicious. If you identify any suspicious activity or money laundering red flags, you must promptly notify the CSB AML Compliance Contact, Xxxxxxxxx Xxxxxx, at 000-000-0000. In that regard, you may be asked by the CSB AML Compliance Contact or by other CSB management personnel to investigate further or obtain additional information from the customer. If so requested you must expeditiously obtain any requested information so CSB can determine in a timely manner if a SAR needs to be filed. The CSB AML Compliance Officer/Contact has the sole responsibility for determining whether to file a SAR and for responding to any regulatory agency’s, customer’s, employee’s, agent’s or producer’s inquiry regarding suspicious activity or SAR. The fact that a suspicious activity is under investigation, or that a SAR has been filed or considered - including the contents of any SAR that has been filed - are strictly confidential. An agent or producer must not, under any ci...
AutoNDA by SimpleDocs
Suspicious Activity Reporting. FMER agrees that on behalf of SunTrust, it will monitor for any potential or actual suspicious activity detected regarding any Services that FMER performs on behalf of SunTrust, including any potential or actual suspicious activity which is committed by Applicants or Borrowers. Such suspicious activity includes any potential or actual activity or transaction that would require SunTrust to file a Suspicious Activity Report as described in the USA PATRIOT Act or 12 C.F.R. § 208.62 (“USA PATRIOT Act”) or other activity which involves fraud, violations of federal, state or local law or which appears to have no legitimate purpose. If FMER becomes aware of any potential or actual suspicious activity, FMER will promptly, and in all cases within seventy-two (72) hours, notify SunTrust’s Consumer Lending Operations Department of the precise nature of any such activity and provide SunTrust with any information and documents concerning the matter. Further, FMER agrees to reasonably cooperate with SunTrust and to provide SunTrust with any additional information and documentation requested regarding any investigation of potential or actual suspicious activity. The contact in the SunTrust’s Consumer Lending Operations Department is Xx. Xxxxx Xxxxxxxxx, whose contact information is: Telephone: (000) 000-0000, Fax: (000) 000-0000, E-Mail: xxxxx.xxxxxxxxx@xxxxxxxx.xxx. SunTrust may change its contact in its Consumer Lending Operations Department at any time by written notice to FMC and FMER that meets the requirements of Section 19.1.
Suspicious Activity Reporting. FMER agrees that on behalf of Lender, it will monitor for any suspicious activity detected regarding any Services that FMER performs on behalf of Lender. Such suspicious activity includes any transaction that would require Lender to file a Suspicious Activity Report as described in the USA PATRIOT Act or 12 C.F.R. § 208.62 (“USA PATRIOT Act”) or other activity which involves fraud, violations of federal, state or local law or which appears to have no legitimate purpose. If FMER becomes aware of any such suspicious activity, FMER will promptly, and in all cases within ten (10) Business Days, notify Lender of the nature of any such activity and provide Lender with information and documents concerning the matter. Further, FMER agrees to reasonably cooperate with Lender and to provide Lender with any additional information and documentation requested regarding any investigation of suspicious activity.
Suspicious Activity Reporting. FMER agrees that on behalf of SunTrust, it will monitor for any potential or actual suspicious activity detected regarding any Services that FMER performs on behalf of SunTrust, including any potential or actual suspicious activity which is committed by the Primary Applicant or Secondary Applicant, as applicable, or the Borrower or the Cosigner. Such suspicious activity includes any potential or actual activity or transaction that would require SunTrust to file a Suspicious Activity Report as described in the USA PATRIOT Act or 12 C.F.R. § 208.62 (“USA PATRIOT Act”) or other activity which involves fraud, violations of federal, state or local law or which appears to have no legitimate purpose. If FMER becomes aware of any potential or actual suspicious activity, FMER will promptly, and in all cases within seventy-two (72) hours, notify SunTrust’s Consumer Lending Operations Department of the precise nature of any such activity and provide SunTrust with any information and documents concerning the matter. Further, FMER agrees to reasonably cooperate with SunTrust and to provide SunTrust with any additional information and documentation requested regarding any investigation of potential or actual suspicious activity. The contact in the SunTrust’s Consumer Lending Operations Department is Xx. Xxxxx Xxxxxxxxx, whose contact information is: Telephone: (000) 000-0000, Fax: (000) 000-0000, E-Mail: xxxxx.xxxxxxxxx@xxxxxxxx.xxx. SunTrust may change its contact in its Consumer Lending Operations Department at any time by written notice to FMC and FMER that meets the requirements of Section 19.1.
Suspicious Activity Reporting. (1) Within ninety (90) days, the Board shall develop, implement, and thereafter ensure Bank adherence to a written program of policies and procedures to ensure compliance with the requirements of 12 C.F.R. Part 21, Subpart B. At a minimum, this written program shall establish procedures for identifying and reporting known or suspected violations of Federal law, violations of the Bank Secrecy Act, or suspicious transactions related to money laundering activity, including suspicious activity relating to the opening of new accounts, the monitoring of current accounts, and the transfer of funds through the Bank as well as:
Suspicious Activity Reporting. We are required by Applicable Law to report suspicious activities relating to money laundering, bribery or corruption to the relevant money laundering reporting officers, regulators and/or other authorities in which event we would be prohibited by Applicable Law from notifying anyone that a report has been made. In certain circumstances, We may be required to suspend the Services or terminate Our relationship with You without giving You Our reason(s).

Related to Suspicious Activity Reporting

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Diversity Report The Contractor shall report to each Customer, spend with certified and other minority business enterprises. These reports shall include the period covered, the name, minority code and Federal Employer Identification Number of each minority business utilized during the period, Commodities provided by the minority business enterprise, and the amount paid to each minority business on behalf of each purchasing agency ordering under the terms of this Contract.

  • Regulatory Reporting Ultimus agrees to provide reports to the federal and applicable state authorities, including the SEC, and to the Funds’ Auditors. Applicable state authorities are those governmental agencies located in states in which the Fund is registered to sell shares.

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11165.7, AB 1432, and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • EDD Independent Subrecipient Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, Subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the State.” The term is further defined by the California Employment Development Department to refer specifically to independent Subrecipients. An independent Subrecipient is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Other Reporting Upon request, the School shall provide the Commission any other information determined by the Commission to be relevant to any term or condition of this Contract.

  • Information Reporting (a) The Fund agrees that, during the Current Special Rate Period and so long as BANA or any Affiliate thereof is the beneficial owner of any Outstanding VRDP Shares, it will deliver, or direct the Tender and Paying Agent to deliver, to BANA and any such Affiliate:

Time is Money Join Law Insider Premium to draft better contracts faster.