PAYMENT OF DEBTS OR DELINQUENCY TO THE STATE OF TEXAS Sample Clauses

PAYMENT OF DEBTS OR DELINQUENCY TO THE STATE OF TEXAS. Pursuant to Sections 2107.008 and 2252.903, Texas Government Code, Contractor agrees that any payments owing to Contractor under this Agreement may be applied directly toward any debt or delinquency that Contractor owes the State of Texas or any agency of the State of Texas regardless of when it arises, until the debt or delinquency is paid in full.
AutoNDA by SimpleDocs

Related to PAYMENT OF DEBTS OR DELINQUENCY TO THE STATE OF TEXAS

  • Payment of Debt or Delinquency to the State Pursuant to §§2107.008 and 2252.903, Texas Government Code, Contractor agrees any payments owing to Contractor under this Agreement may be applied directly toward any debt or delinquency Contractor owes the State of Texas or any agency of the State of Texas, regardless of when it arises, until paid in full.

  • Requirements of the State of Kansas 1. The contractor shall observe the provisions of the Kansas Act against Discrimination (Kansas Statutes Annotated 44-1001, et seq.) and shall not discriminate against any person in the performance of work under the present contract because of race, religion, color, sex, disability, and age except where age is a bona fide occupational qualification, national origin or ancestry;

  • Project Monitoring by the State The State may conduct on-site or off-site monitoring reviews of the Project during the term of this Grant Agreement and for up to ninety (90) days after it expires or is otherwise terminated. The Grantee shall extend its full cooperation and give full access to the Project site and to relevant documentation to the State or its authorized designees for the purpose of determining, among other things:

  • Payment of Principal, Interest, Escrow Items, Prepayment Charges, and Late Charges Borrower will pay each Periodic Payment when due. Borrower will also pay any prepayment charges and late charges due under the Note, and any other amounts due under this Security Instrument. Payments due under the Note and this Security Instrument must be made in U.S. currency. If any check or other instrument received by Lender as payment under the Note or this Security Instrument is returned to Lender unpaid, Lender may require that any or all subsequent payments due under the Note and this Security Instrument be made in one or more of the following forms, as selected by Lender: (a) cash; (b) money order; (c) certified check, bank check, treasurer’s check, or cashier’s check, provided any such check is drawn upon an institution whose deposits are insured by a U.S. federal agency, instrumentality, or entity; or (d) Electronic Fund Transfer. Payments are deemed received by Lender when received at the location designated in the Note or at such other location as may be designated by Lender in accordance with the notice provisions in Section 16. Lender may accept or return any Partial Payments in its sole discretion pursuant to Section 2. Any offset or claim that Borrower may have now or in the future against Lender will not relieve Borrower from making the full amount of all payments due under the Note and this Security Instrument or performing the covenants and agreements secured by this Security Instrument.

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

  • Taxes and Fees Imposed on Purchasing Party But Collected And Remitted By Providing Party 11.3.1 Taxes and fees imposed on the purchasing Party shall be borne by the purchasing Party, even if the obligation to collect and/or remit such taxes or fees is placed on the providing Party.

  • Taxes and Fees Imposed on Providing Party But Passed On To Purchasing Party 11.4.1 Taxes and fees imposed on the providing Party, which are permitted or required to be passed on by the providing Party to its customer, shall be borne by the purchasing Party.

  • Taxes Due to the State A. Party understands and acknowledges responsibility, if applicable, for compliance with State tax laws, including income tax withholding for employees performing services within the State, payment of use tax on property used within the State, corporate and/or personal income tax on income earned within the State.

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • COLLECTION OF CHARGES 16.1 A Sector Association may request the consent of the Administrator to collect charges due from Operators to the Administrator in respect of facilities under the charging scheme.

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