Customer Identification Program (A) To assist the Fund in complying with requirements regarding a customer identification program in accordance with applicable regulations promulgated by U.S. Department of Treasury under Section 326 of the USA PATRIOT Act ("CIP Regulations"), BNYM will do the following:
(i) Implement procedures which require that prior to establishing a new account in the Fund BNYM obtain the name, date of birth (for natural persons only), address and government-issued identification number (collectively, the "Data Elements") for the "Customer" (defined for purposes of this Agreement as provided in 31 CFR 1024.100(c)) associated with the new account.
(ii) Use collected Data Elements to attempt to reasonably verify the identity of each new Customer promptly before or after each corresponding new account is opened. Methods of verification may consist of non-documentary methods (for which BNYM may use unaffiliated information vendors to assist with such verifications) and documentary methods (as permitted by 31 CFR 1024.220), and may include procedures under which BNYM personnel perform enhanced due diligence to verify the identities of Customers the identities of whom were not successfully verified through the first- level (which will typically be reliance on results obtained from an information vendor) verification process(es).
(iii) Record the Data Elements and maintain records relating to verification of new Customers consistent with 31 CFR 1024.220(a)(3).
(iv) Regularly report to the Fund about measures taken under (i)-(iii) above.
(v) If BNYM provides services by which prospective Customers may subscribe for shares in the Fund via the Internet or telephone, BNYM will work with the Fund to notify prospective Customers, consistent with 31 CFR 1024.220(a)(5), about the program conducted by the Fund in accordance with the CIP Regulations.
(B) To assist the Fund in complying with the Customer Due Diligence Requirements for Financial Institutions promulgated by FinCEN (31 CFR § 1020.230) pursuant to the Bank Secrecy Act ("CDD Rule"), BNYM will maintain and implement written procedures that are reasonably designed to:
(i) Obtain information of a nature and in a manner permitted or required by the CCD Rule in order to identify each natural person who is a "beneficial owner" (as that term is defined in the CDD Rule) of a legal entity at the time that such legal entity seeks to open an account as a shareholder of the Fund, unless that legal entity is excluded from the CDD Rule or an exemption provided for in the CDD Rule applies; and
(ii) Verify the identity of each beneficial owner so identified according to risk based procedures to the extent reasonable and practicable, in accordance with the minimum requirements of the CDD Rule.
(C) Nothing in Section (3) shall be construed to require BNYM to perform any course of conduct that is not required for Fund compliance with the CIP Regulations or CDD Rule, including by way of illustration not limitation the collection of Data Elements or verification of identity for individuals opening Fund accounts through financial intermediaries which use the facilities of the NSCC.
(D) BNYM agrees to permit inspections relating to the CIP services provided hereunder by U.S. Federal departments or regulatory' agencies with appropriate jurisdiction and to make available to examiners from such departments or regulatory agencies such information and records relating to the CIP services provided hereunder as such examiners shall reasonably request.
No Reliance on Administrative Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Administrative Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA Patriot Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any of the Loan Parties, their Affiliates or their agents, the Loan Documents or the transactions hereunder or contemplated hereby: (i) any identity verification procedures, (ii) any recordkeeping, (iii) comparisons with government lists, (iv) customer notices or (v) other procedures required under the CIP Regulations or such other Laws.
Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.
Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers.
5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem.
5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.
Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.
Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
No Reliance on Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA PATRIOT Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any Borrower, its Affiliates or its agents, this Agreement, the Other Documents or the transactions hereunder or contemplated hereby: (1) any identity verification procedures, (2) any record-keeping, (3) comparisons with government lists, (4) customer notices or (5) other procedures required under the CIP Regulations or such other laws.
