Report Suspicious Activity To Sample Clauses

Report Suspicious Activity To. Contact: Xxxxxx X. Xxxxxx, AVP, Corporate Compliance, Chief Compliance Officer for AML/OFAC Xxxxxxxxx, XX 00000-0000 Email: XXXXxxxxxxxxx@xxxxx.xxx Advise customers that only the following types of payment may be accepted: • Personal checks and pre-authorized checks. • Cash equivalents (money orders, cashier’s checks, traveler’s checks, bank drafts.) - Cash and cash equivalents must be reported to the IRS and FinCEN on Form 8300 when payments received by the Company in a single transaction or in two or more related transactions total more than $10,000. Related transactions occurring within any 12-month period would be aggregated for reporting purposes even if individually they are less than $10,000. - Limited to $500 for variable contracts. • If a customer provides a form of payment that is not permitted, do not accept the payment and notify the AML compliance officer if it is in an amount greater than $1,000. I have received, read and understand Standard Life’s Company Guide to Anti-Money Laundering. I agree to comply with the requirements of such policies and understand that failure to do so will lead to disciplinary action, up to and including termination and appropriate legal sanctions. Date: Print Name: Personal Code or Social Security Number: Signature: CGAML ST-1832 R308 American National Insurance Company and its affiliated companies are committed to providing insurance and annuity products and services designed to meet your needs. We are equally committed to respecting your privacy and protecting the information about you that we may receive. We have prepared this notice to advise you what information we collect, how we use it and how we protect it.
Report Suspicious Activity To. Contact: Xxxxxx X. Xxxxxx (Xxxx) Assistant Vice President Corporate Compliance Chief Compliance Officer for Anti-Money Laundering /OFAC Or Xxxxx Xxxxxx, Quality Assurance Analyst Email: XXXXxxxxxxxxx@xxxxx.xxx Advise customers that only the following types of payment may be accepted: • Personal checks and pre-authorized checks. • Cash equivalents (money orders, cashier’s checks, traveler’s checks, bank drafts.) - Cash and cash equivalents must be reported to the IRS and FinCEN on Form 8300 when payments received by the Company in a single transaction. Related transactions occurring within any 12-month period would be aggregated for reporting purposes even if individually they are less than $10,000. • If a customer provides a form of payment that is not permitted, do not accept the payment and notify the appropriate AML compliance officer if it is in an amount greater than the limits defined herein.
Report Suspicious Activity To. Contact: Xxxxxx X. Xxxxxx (Xxxx), Assistant Vice President, Corporate Compliance, Chief Compliance Officer for Anti-Money Laundering Email: XXXXxxxxxxxxx@xxxxx.xxx Advise customers that only the following types of payment may be accepted: • Personal checks and pre-authorized check payments. • Cash (currency or coin) in amounts less than $1,000. • Cash equivalents (money orders, cashier’s checks, traveler’s checks, bank drafts). - Cash and cash equivalents must be reported to the IRS and FinCEN on Form 8300 when payments received by the Company in a single transaction or in two or more related transactions total more than $10,000. Related transactions occurring within any 12-month period would be aggregated for reporting purposes even if individually they are less than $10,000. [Agents may have independent reporting obligations and should check their Company’s website for additional information.] - Limited to $500 for variable contracts. • If a customer provides a form of payment that is not permitted, do not accept the payment and notify the appropriate AML compliance officer if it is in an amount greater than $1,000. For more details on each of these requirements, contact the AML officer of American National or of SM&R, for broker/dealer questions involving variable contracts. Agent’s Name: Social Security No: Address: City: State Zip Code Phone: (daytime) (evening) Title of training program Date training program completed Insurance company: ❑ (please specify full name and contact information) Broker Dealer: ❑ (please specify full name and contact information) Bank: ❑ (please specify full name and contact information) Vendor: (please specify full name and contact information) Other ❑ (please specify full name and contact information and attach outline of training program if available) I am a duly licensed insurance agent and affirm that I have completed the above-referenced training program, which to the best of my knowledge satisfies requirements imposed on insurance companies by regulations issued under USA Patriot Act Section 352 (US 31 CFR 103.137). I acknowledge that the insurance company to which this certification has been provided retains the right to review and approve the training program and its curriculum before accepting this certification. I affirm (i) that I have read and understand the insurance company’s AML Guide and (ii) that I am knowledgeable about my obligations under the regulation. Signature of Agent Date: ❑ Training program covers...
Report Suspicious Activity To. Contact: Xxxxxx X. Xxxxxx (Xxxx), Assistant Vice President, Corporate Compliance, Chief Compliance Officer for Anti-Money Laundering Email: XXXXxxxxxxxxx@xxxxx.xxx Advise customers that only the following types of payment may be accepted: • Personal checks and pre-authorized check payments. • Cash (currency or coin) in amounts less than $1,000. • Cash equivalents (money orders, cashier’s checks, traveler’s checks, bank drafts). - Cash and cash equivalents must be reported to the IRS and FinCEN on Form 8300 when payments received by the Company in a single transaction or in two or more related transactions total more than $10,000. Related transactions occurring within any 12-month period would be aggregated for reporting purposes even if individually they are less than $10,000. [Agents may have independent reporting obligations and should check their Company’s website for additional information.] - Limited to $500 for variable contracts. • If a customer provides a form of payment that is not permitted, do not accept the payment and notify the appropriate AML compliance officer if it is in an amount greater than $1,000. For more details on each of these requirements, contact the AML officer of American National or of SM&R, for broker/dealer questions involving variable contracts. The Federal Fair Credit Reporting Act, as amended, provides that any consumer reporting agency may furnish a consumer report in accordance with the written instructions of the consumer to whom it relates. In accordance with that provision, the person signing this form as "Applicant" hereby authorizes any person or agency to give, in writing, orally, or in any other form, to American National Insurance Company or its designated representatives any information gathered or maintained by a consumer reporting agency bearing on the Applicant's credit worthiness, credit standing, credit capacity, character, general reputation, personal characteristics, or mode of living which is used or expected to be used or collected in whole or in part for the purpose of serving as a factor in establishing the Applicant's eligibility for credit, employment or any other purpose authorized under Section 604 of the Act. Further, the Applicant understands that American National Insurance Company may, as part of its normal procedure, request that an investigative consumer credit report be made whereby information on the Applicant's character, general reputation, personal characteristics or mode of living is ...

Related to Report Suspicious Activity To

  • 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: 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

  • CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Duty to report Force Majeure Event 21.5.1 Upon occurrence of a Force Majeure Event, the Affected Party shall by notice report such occurrence to the other Party forthwith. Any notice pursuant hereto shall include full particulars of: (a) the nature and extent of each Force Majeure Event which is the subject of any claim for relief under this Article 21 with evidence in support thereof; (b) the estimated duration and the effect or probable effect which such Force Majeure Event is having or will have on the Affected Party’s performance of its obligations under this Agreement; (c) the measures which the Affected Party is taking or proposes to take for alleviating the impact of such Force Majeure Event; and (d) any other information relevant to the Affected Party’s claim. 21.5.2 The Affected Party shall not be entitled to any relief for or in respect of a Force Majeure Event unless it shall have notified the other Party of the occurrence of the Force Majeure Event as soon as reasonably practicable, and in any event no later than 10 (ten) days after the Affected Party knew, or ought reasonably to have known, of its occurrence, and shall have given particulars of the probable material effect that the Force Majeure Event is likely to have on the performance of its obligations under this Agreement. 21.5.3 For so long as the Affected Party continues to claim to be materially affected by such Force Majeure Event, it shall provide the other Party with regular (and not less than weekly) reports containing information as required by Clause 21.5.1, and such other information as the other Party may reasonably request the Affected Party to provide.

  • Regulatory Information (a) All the notaries at De Pinna LLP are regulated through the Faculty Office of the Archbishop of Canterbury. Its address is The Faculty Office, 0 Xxx Xxxxxxxxx, Xxxxxxxxxxx, Xxxxxx XX0X 0XX, its telephone: 000 0000 0000, and it can be reached by email at xxxxxxx.xxxxxx@0xxxxxxxxxxxx.xxx. It also has a website at xxx.xxxxxxxxxxxxx.xxx.xx. (b) We are required to comply with the rules of professional conduct and other regulatory arrangements of the Master of the Faculties, the sole regulator of notarial activities under the Legal Services Act 2007. Information about those rules and regulations may be found at xxxx://xxx.xxxxxxxxxxxxx.xxx.xx/notary/i-am-a-notary/notaries-rules-regulations/. (c) We comply with the Code of Practice published by the Master of the Faculties: xxxx://xxx.xxxxxxxxxxxxx.xxx.xx/notary/code-of-practice.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Reasonable Suspicion Testing All Employees Performing Safety-Sensitive Functions A. Reasonable suspicion testing for alcohol or controlled substances may be directed by the Employer for any employee performing safety-sensitive functions when there is reason to suspect that alcohol or controlled substance use may be adversely affecting the employee’s job performance or that the employee may present a danger to the physical safety of the employee or another. B. Specific objective grounds must be stated in writing that support the reasonable suspicion. Examples of specific objective grounds include but are not limited to: 1. Physical symptoms consistent with alcohol and/or controlled substance use; 2. Evidence or observation of alcohol or controlled substance use, possession, sale, or delivery; or 3. The occurrence of an accident(s) where a trained manager, supervisor or lead worker suspects alcohol or other controlled substance use may have been a factor.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Medical Information Throughout the Pupil's time as a member of the School, the School Medical Officer shall have the right to disclose confidential information about the Pupil if it is considered to be in the Pupil's own interests or necessary for the protection of other members of the School community. Such information will be given and received on a confidential, need-to-know basis.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!