Normal Billing Cycle Turnaround Sample Clauses

Normal Billing Cycle Turnaround. Prior to August 1, 1997 - * hours, excluding the time from 12:01A.M. to 11:59P.M. on Saturday, Sunday, and CSC holidays, as detailed in Appendix E. In the event CSC is unable to deliver Customer's Subscriber Billing Services statements to the U.S. Postal Service within this timeframe, CSC shall provide to Customer a credit as determined in Section 12.2 d. below. Beginning August 1, 1997 - * hours, excluding the time from 12:01A.X.xx 00:59P.M.on CSC holidays, as detailed in Appendix E. In the event CSC is unable to deliver Customer's Subscriber Billing Services statements to the U.S. Postal Service within this time frame, CSC shall provide to Customer a credit as determined in Section 12.2 d. below.
AutoNDA by SimpleDocs

Related to Normal Billing Cycle Turnaround

  • Billing Cycle The billing on each matter shall be submitted on a calendar month basis (30 day cycle). A final bill for all outstanding charges should be forwarded immediately by the Firm upon the conclusion of each matter. Citizens has sole discretion to consider billing for work performed which is submitted late to Citizens. Late is defined as billed events that occurred more than 60 days prior to it being initially submitted to Citizens for payment. Citizens will not honor interest fees or other late fees assessed by any Firm or Vendor for any invoice submitted for payment. Billing submitted late to Citizens will not be given priority review.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

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

  • Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

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