Billing Specifications Sample Clauses

Billing Specifications. 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).
AutoNDA by SimpleDocs
Billing Specifications. 49.5.1 The Parties will bill each other in a timely manner.
Billing Specifications. The Parties agree that billing requirements and outputs will be consistent with the Bellcore Billing Output Specifications (BOS).
Billing Specifications. The Parties agree that billing requirements and outputs will be consistent with the Telcordia Technologies Billing Output Specifications (BOS). Usage measurement for calls shall begin when Answer Supervision or equivalent SS7 message is received from the terminating office and shall end at the time of call disconnect by the calling or called subscriber, whichever occurs first. Minutes of use (“MOU”), or fractions thereof, shall not be rounded upward on a per-call basis, but will be accumulated over the billing period. At the end of the billing period, any remaining fraction shall be rounded up to the nearest whole minute to arrive at total billable minutes for each interconnection. MOU shall be collected and measured in minutes, seconds, and tenths of seconds. In the event detailed billing records are not available (e.g. indirect interconnection), summary billing reports may be utilized.
Billing Specifications. IV-1 3.1 Traffic to be exchanged..................................................................................... IV-2
Billing Specifications. Minute of Use charges for transport and termination of Local Traffic shall be billed by each Party to the other Party in arrears. The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).
AutoNDA by SimpleDocs

Related to Billing Specifications

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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