Listing of Discrepancies between Escrow Data and Zone File Sample Clauses

Listing of Discrepancies between Escrow Data and Zone File. The EBERO will reconcile escrow and zone file data as part of the SRS import process, and generate a list of the discrepancies between the two sources using the algorithm described below in Section 9 Handling Discrepancies between Data Sources during Transition. The action taken on any discrepancy must be included in this listing. The listing will be both communicated to ICANN and preserved as part of the Transition-Out documentation to be provided to any Successor Operator. The format for this listing is described in Section 10.1
AutoNDA by SimpleDocs

Related to Listing of Discrepancies between Escrow Data and Zone File

  • Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.

  • Inspection Checklist (Check one)

  • Appendix A – HRIS File Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:

  • Data Escrow Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

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

  • Foreign Assets/Account Reporting Information Italian residents who, during the fiscal year, hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs) which may generate income taxable in Italy are required to report such on their annual tax returns (UNICO Form, RW Schedule) or on a special form if no tax return is due. The same reporting obligations apply to Italian residents who, even if they do not directly hold investments abroad or foreign financial assets (e.g., cash, Shares and RSUs), are beneficial owners of the investment pursuant to Italian money laundering provisions.

  • How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.

  • Customer Notification By executing this Agreement, the Advisor acknowledges that as required by the Advisers Act the Sub-Advisor has supplied to the Advisor and the Trust copies of the Sub-Advisor’s Form ADV with all exhibits and attachments (including the Sub-Advisor’s statement of financial condition) and will promptly supply to the Advisor copies of all amendments or restatements of such document. Otherwise, the Advisor’s rights under federal law allow termination of this contract without penalty within five business days after entering into this contract. U.S. law also requires the Sub-Advisor to obtain, verify, and record information that identifies each person or entity that opens an account. The Sub-Advisor will ask for the Trust’s legal name, principal place of business address, and Taxpayer Identification or other identification number, and may ask for other identifying information.

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