Operating Period Monthly Reporting Requirement Sample Clauses

Operating Period Monthly Reporting Requirement. As part of its monthly Progress Report submissions made during the Operating Period pursuant to Section 4.1 of Schedule 8 (Project Administration), the Developer shall submit all reports referenced in this Schedule 15 as applicable during the Operating Period, including as necessary to comply with the Operating Period reporting requirements contained in Appendix C to this Schedule 15 and the Xxxxx-Xxxxx reporting requirements contained in Section 2.1.3 of this Schedule 15.
AutoNDA by SimpleDocs

Related to Operating Period Monthly Reporting Requirement

  • Detailed Monthly Report Vendor shall electronically provide DIR with a detailed monthly report in the format required by DIR showing the dollar volume of any and all sales under the Contract for the previous calendar month period. Reports are due on the fifteenth (15th) calendar day of the month following the month of the sale. If the 15th calendar day falls on a weekend or state or federal holiday, the report shall be due on the next business day. The monthly report shall include, per transaction: the detailed sales for the period, Customer name, invoice date, invoice number, description, quantity, MSRP or List Price, unit price, extended price, Customer Purchase Order number, contact name, Customer’s complete billing address, the estimated administrative fee for the reporting period, subcontractor name, EPEAT designation (if applicable), configuration (if applicable), contract discount percentage, actual discount percentage, negotiated contract price (if fixed price is offered instead of discount off of MSRP), and other information as required by DIR. Each report must contain all information listed above per transaction or the report will be rejected and returned to the Vendor for correction in accordance with this section. Vendor shall report in a manner required by DIR which is subject to change dependent upon DIR’s business needs. Failure to do so may result in contract termination.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.

  • Monthly Report A. A Monthly Report shall be submitted within ten (10) calendar days of the end of each calendar month of the Period of Operation. Each Monthly Report shall be signed, dated, and certified by Concessionaire, Concessionaire’s Bookkeeper, or Accountant, and contain a Statement of Total Gross Receipts, excluding New Jersey State Sales Tax, derived by Concessionaire from operation of the Concession during the previous month. Each Monthly Report shall be based on the daily “Z” tapes or Point-of-Service (POS) device equivalent for that same month showing each day’s sales activity. Failure on the part of Concessionaire to provide the Monthly Report, when due, shall constitute a material breach of this Agreement subject to Suspension of Operations and/or Termination, in accordance with the terms and conditions set forth in Paragraphs 9 and 10. Concessionaire shall provide Department with any additional written clarification and/or information necessary to confirm the accuracy of any or all of Concessionaire’s Monthly Reports.

  • Child Abuse Reporting Requirement Grantee will:

  • ADDITIONAL REPORTING REQUIREMENTS Contractor agrees to submit written quarterly reports to H-GAC detailing all transactions during the previous three (3) month period. Reports must include, but are not limited, to the following information:

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.

Time is Money Join Law Insider Premium to draft better contracts faster.