Billing Deadlines. DHS may delay or deny payment to Contractor for xxxxxxxx or claims for services that do not meet the billing deadlines outlined below.
Billing Deadlines Sample Clauses
Related to Billing Deadlines
Quarterly Reporting Timeframes Quarterly reporting timeframes coincide with the State Fiscal Year as follows: Quarter 1 - (July-September) – Due by October 10 Quarter 2 - (October-December) – Due by January 10 Quarter 3 - (January-March) – Due by April 10 Quarter 4 - (April-June) – Due by July 10
Extended Reporting Period If any required insurance coverage is on a claims-made basis (rather than occurrence), Contractor shall maintain such coverage for a period of no less than three (3) years following expiration or termination of the Contract.
Registration Statement; Joint Proxy Statement (a) As promptly as practicable after the date of this Agreement, Parent and the Company shall prepare and cause to be filed with the SEC the Joint Proxy Statement and simultaneously or thereafter Parent shall prepare and cause to be filed with the SEC the Form S-4 Registration Statement, in which the Joint Proxy Statement will be included as a prospectus. Each of Parent and the Company shall use all reasonable efforts to cause the Form S-4 Registration Statement and the Joint Proxy Statement to comply with the rules and regulations promulgated by the SEC, to respond promptly to any comments of the SEC or its staff and to have the Form S-4 Registration Statement declared effective under the Securities Act as promptly as practicable after it is filed with the SEC. Parent will use all reasonable efforts to cause the Joint Proxy Statement to be mailed to Parent's stockholders, and the Company will use all reasonable efforts to cause the Joint Proxy Statement to be mailed to the Company's shareholders, as promptly as practicable after the Form S-4 Registration Statement is declared effective under the Securities Act. Each of the Company and Parent shall promptly furnish to the other all information concerning the Acquired Corporations and the Company's shareholders and the Parent Corporations, respectively, that may be required or reasonably requested in connection with any action contemplated by this Section 5.1. Each of the Company and Parent shall notify the other promptly of the receipt of any comments from the SEC or its staff and of any request by the SEC or its staff for any amendment or supplement to the Form S-4 Registration Statement or Joint Proxy Statement or for any other information and shall supply the other with copies of all correspondence between such party and the SEC or its staff or other governmental officials with respect to the S-4 Registration Statement or Joint Proxy Statement. The information supplied by each of Parent and the Company for inclusion in the Form S-4 Registration Statement and the Joint Proxy Statement shall not (i) at the time the Form S-4 Registration Statement is declared effective, (ii) at the time the Joint Proxy Statement is first mailed to the shareholders and shareholders of Parent and the Company, respectively, (iii) at the time of the Company Shareholders' Meeting and at the time of the Parent Stockholders' Meeting, and (iv) at the Effective Time, contain any untrue statement of a material fact or omit to state any material fact required to be stated therein or necessary in order to make the statements therein, in light of the circumstances under which they were made, not misleading. If Parent or the Company becomes aware of any information, that should be disclosed in an amendment or supplement to the Form S-4 Registration Statement or the Joint Proxy Statement, then Parent or the Company, as the case may be, shall promptly inform the Company or Parent thereof and shall cooperate with the other in filing such amendment or supplement with the SEC and, if appropriate, in mailing such amendment or supplement to the shareholders of the Company or the stockholders of Parent. (b) Prior to the Effective Time, Parent shall use reasonable efforts to obtain all regulatory approvals needed to ensure that the Parent Common Stock to be issued in the Merger (i) will be registered or qualified under the securities law of every jurisdiction of the
Contract Quarterly Sales Reports The Contractor shall submit complete Quarterly Sales Reports to the Department’s Contract Manager within 30 calendar days after the close of each State fiscal quarter (the State’s fiscal quarters close on September 30, December 31, March 31, and June 30). Reports must be submitted in MS Excel using the DMS Quarterly Sales Report Format, which can be accessed at xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/ state_purchasing/vendor_resources/quarterly_sales_report_format. Initiation and submission of the most recent version of the Quarterly Sales Report posted on the DMS website is the responsibility of the Contractor without prompting or notification from the Department’s Contract Manager. If no orders are received during the quarter, the Contractor must email the DMS Contract Manager confirming there was no activity.
Reporting Period Project progress including a summary of progress, findings, data, analyses, results and field-test results from all tasks carried out in the covered period.
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.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
Registration Statement; Joint Proxy Statement/Prospectus Subject to the accuracy of the representations of Parent in Section 2.13, the information supplied by the Company for inclusion in the Registration Statement shall not, at the time the Registration Statement (including any amendments or supplements thereto) is declared effective by the SEC, contain any untrue statement of a material fact or omit to state any material fact necessary in order to make the statements included therein, in light of the circumstances under which they were made, not misleading. The information supplied by the Company for inclusion in the Joint Proxy Statement/Prospectus will not, on the date the Joint Proxy Statement/Prospectus is first mailed to shareholders, at the time of the Shareholders Meetings and at the Effective Time, contain any statement which, at such time and in light of the circumstances under which it shall be made, is false or misleading with respect to any material fact, or will omit to state any material fact necessary in order to make the statements therein not false or misleading; or omit to state any material fact necessary to correct any statement in any earlier communication with respect to the solicitation of proxies for the Shareholders Meetings which has become false or misleading. If at any time prior to the Effective Time any event relating to the Company or any of its affiliates, officers or directors should be discovered by the Company which should be set forth in an amendment to the Registration Statement or a supplement to the Joint Proxy Statement/Prospectus, the Company will promptly inform Parent. The Joint Proxy Statement/Prospectus shall comply in all material respects with the requirements of the Securities Act, the Exchange Act and the rules and regulations thereunder. Notwithstanding the foregoing, the Company makes no representation or warranty with respect to any information supplied by Parent or Merger Sub which is contained or incorporated by reference in, or furnished in connection with the preparation of, the Joint Proxy Statement/Prospectus.
