Annual Officer’s Certificate; Notice of Servicer Replacement Event (a) The Servicer will deliver to the Issuer, with a copy to the Indenture Trustee, on or before March 30th of each year, beginning on March 30, 2019, an Officer’s Certificate, dated as of December 31 of the immediately preceding year, providing such information as is required under Item 1123 of Regulation AB. (b) The Servicer will deliver to the Issuer, with a copy to the Indenture Trustee within five (5) Business Days after having obtained knowledge thereof written notice in an Officer’s Certificate of any event which with the giving of notice or lapse of time, or both, would become a Servicer Replacement Event. Except to the extent set forth in this Section 3.9(b), Section 7.2 and Section 9.22 of this Agreement and Section 3.12 and Section 6.5 of the Indenture, the Transaction Documents do not require any policies or procedures to monitor any performance or other triggers and events of default. (c) The Servicer will deliver to the Issuer, on or before March 30th of each year, beginning on March 30, 2019, a report regarding the Servicer’s assessment of compliance with the Servicing Criteria specified in Exhibit C as applicable to the Servicer during the immediately preceding calendar year, including disclosure of any material instance of non-compliance identified by the Servicer, as required under paragraph (b) of Rule 13a-18, or Rule 15d-18 of the Exchange Act and Item 1122 of Regulation AB, or such other criteria as mutually agreed upon by the Seller and the Servicer.
Monthly Servicer’s Certificate On or before the Determination Date immediately preceding each Distribution Date, the Servicer shall deliver to the Depositor, the Seller, the Owner Trustee, the Indenture Trustee and each Paying Agent, with a copy to the Rating Agencies, a certificate of a Servicing Officer substantially in the form of Exhibit A (a “Servicer’s Certificate”) and attached to a Servicer’s report containing all information necessary to make the transfers and distributions pursuant to Sections 4.5, 4.6 and 4.7, together with the written statements to be furnished by the Indenture Trustee to the Certificateholders pursuant to Section 4.9 and by the Indenture Trustee to the Noteholders pursuant to Section 4.9 and pursuant to Section 6.6 of the Indenture. The Servicer shall separately identify (by account number) in a written notice to the Depositor, the Owner Trustee and the Indenture Trustee the Receivables to be repurchased by the Depositor or to be purchased by the Servicer, as the case may be, on the Business Day preceding such Distribution Date, and, upon request of one of the foregoing parties, each Receivable which became a Defaulted Receivable during the related Collection Period. The Servicer shall deliver to the Rating Agencies any information, to the extent it is available to the Servicer, that the Rating Agencies reasonably request (and the initial Servicer shall specify in writing to the successor Servicer any such requests that remain unsatisfied during the servicing transition to the successor Servicer) in order to monitor the Trust.
SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO. 4.2 The Authority reserves the right (acting reasonably) to specify that the MI Report be submitted by the Supplier using an alternative communication to that specified in paragraph 4.1 above such as email. The Supplier agrees to comply with any such instructions provided they do not materially increase the burden on the Supplier.
Actual Settlement Date Accounting With respect to any sale or purchase transaction that is not posted to the Account on the contractual settlement date as referred to in Section 2.5, Bank shall post the transaction on the date on which the cash or Financial Assets received as consideration for the transaction is actually received by Bank.
Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐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 per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.