Settlement Base and Cycle of China Mobile Account Billing Sample Clauses

Settlement Base and Cycle of China Mobile Account Billing 
AutoNDA by SimpleDocs

Related to Settlement Base and Cycle of China Mobile Account Billing

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Account Verification Whether or not a Default or Event of Default exists, Agent shall have the right at any time, in the name of Agent, any designee of Agent or any Borrower, to verify the validity, amount or any other matter relating to any Accounts of Borrowers by mail, telephone or otherwise. Borrowers shall cooperate fully with Agent in an effort to facilitate and promptly conclude any such verification process.

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

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Direction to Account Debtors; Contracting Parties; etc Upon the occurrence and during the continuance of an Event of Default, if the Collateral Agent so directs any Grantor, such Grantor agrees (i) to cause all payments on account of the Accounts and Contracts to be made directly to a cash account held by the Collateral Agent (the “Cash Collateral Account”), (ii) that, upon concurrent notice to such Grantor, the Collateral Agent may directly notify the obligors with respect to any Accounts and/or under any Contracts to make payments with respect thereto as provided in the preceding clause (i), and (iii) that the Collateral Agent may enforce collection of any such Accounts and Contracts and may, in consultation with such Grantor, adjust, settle or compromise the amount of payment thereof, in the same manner and to the same extent as such Grantor. Without notice to or assent by any Grantor, the Collateral Agent may (at the direction of the holders of the Notes), upon the occurrence and during the continuance of an Event of Default, apply any or all amounts then in, or thereafter deposited in, the Cash Collateral Account toward the payment of the Indenture Obligations in the manner provided in Section 4.01 of the Indenture. The reasonable out-of-pocket costs and expenses of collection (including reasonable attorneys’ fees), whether incurred by a Grantor or the Collateral Agent, shall be borne by the relevant Grantor. The Collateral Agent shall deliver a copy of each notice referred to in the preceding clause (ii) to the relevant Grantor; provided, that (x) the failure by the Collateral Agent to so notify such Grantor shall not affect the effectiveness of such notice or the other rights of the Collateral Agent created by this Section 4 and (y) no such notice shall be required if an Event of Default of the type described in Sections 6.01(7) or (8) of the Indenture has occurred and is continuing.

  • Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.)

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Program Location A. Unless otherwise agreed upon in writing, the parties acknowledge and agree that the Work of this Agreement will be performed at the following Property address: Ktr Address1 Address2

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