Collection of Debts Owed to the Government Sample Clauses

Collection of Debts Owed to the Government. An employee will be provided due process in accordance with the appropriate debt collection and salary offset regulations, including 5 U.S.C. 5514, 5 CFR 550 Subpart K, and the Debt Collection Improvement Act (1996). These processes constitute the employee’s grievance/appeal procedures regarding the existence and amount of the debt and any resulting collection action.
AutoNDA by SimpleDocs

Related to Collection of Debts Owed to the Government

  • NO GOVERNMENT OBLIGATION TO THIRD PARTIES (1) The Department and Contractor acknowledge and agree that, notwithstanding any concurrence by the Federal Government in or approval of the solicitation or award of the underlying contract, absent the express written consent by the Federal Government, the Federal Government is not a party to this contract and shall not be subject to any obligations or liabilities to the Department, Contractor, or any other party (whether or not a party to that contract) pertaining to any matter resulting from the underlying contract.

  • Notification of Deposits Along with the delivery of each Deposit, Registry Operator will deliver to Escrow Agent and to ICANN (using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Part A, Section 9, reference 5 of this Specification (the “Interface Specification”)) a written statement (which may be by authenticated e-­‐mail) that includes a copy of the report generated upon creation of the Deposit and states that the Deposit has been inspected by Registry Operator and is complete and accurate. Registry Operator will include the Deposit’s “id” and “resend” attributes in its statement. The attributes are explained in Part A, Section 9, reference 1 of this Specification. If not already an RFC, Registry Operator will use the most recent draft version of the Interface Specification at the Effective Date. Registry Operator may at its election use newer versions of the Interface Specification after the Effective Date. Once the Interface Specification is published as an RFC, Registry Operator will implement that version of the Interface Specification, no later than one hundred eighty (180) calendar days after such publishing.

  • Calculation of Charges Contractor shall provide an invoice to the City on a monthly basis for goods delivered and/or Services completed in the immediate preceding month, unless a different schedule is set out in Appendix B, “Calculation of Charges.” Compensation shall be made for goods and/or Services identified in the invoice that the City, in his or her sole discretion, concludes has been satisfactorily performed. In no event shall the amount of this Agreement exceed [insert whole dollar amount in numbers and words -- no pennies and no “.00”]. The breakdown of charges associated with this Agreement appears in Appendix B, “Calculation of Charges.” A portion of payment may be withheld until conclusion of the Agreement if agreed to by both Parties as retainage, described in Appendix B. In no event shall City be liable for interest or late charges for any late payments. City will not honor minimum service order charges for any services covered by this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!