Submission of Certified Payroll Transcripts for Public Works Contracts Only Contractors and Subcontractors on public works projects must submit monthly payroll transcripts to the Authorized User that has prepared or directs the preparation of the plans and specifications for a public works project, as set forth in the Bid Specifications. For Mini-Bid solicitations, the payroll records must be submitted to the entity preparing the agency Mini-Bid project specification. For “agency specific” Bids, the payroll records should be submitted to the entity issuing the purchase order. For all other OGS Centralized Contracts, such records should be submitted to the individual agency issuing the purchase order(s) for the work. Upon mutual agreement of the Contractor and the Authorized User, the form of submission may be submitted in a specified disk format acceptable to the Department of Labor provided: 1) the Contractor/Subcontractor retains the original records; and, (2) an original signed letter by a duly authorized individual of the Contractor or Subcontractor attesting to the truth and accuracy of the records accompanies the disk. This provision does not apply to Article 9 of the Labor Law building services contracts.
Linking to the Website and Social Media Features You may link to our homepage, provided you do so in a way that is fair and legal and does not damage our reputation or take advantage of it, but you must not establish a link in such a way as to suggest any form of association, approval, or endorsement on our part. This Website may provide certain social media features that enable you to: • Link from your own or certain third-party websites to certain content on this Website. • Send emails or other communications with certain content, or links to certain content, on this Website. • Cause limited portions of content on this Website to be displayed or appear to be displayed on your own or certain third-party websites. You may use these features solely as they are provided by us, and solely with respect to the content they are displayed with, and otherwise in accordance with any additional terms and conditions we provide with respect to such features. Subject to the foregoing, you must not: • Establish a link from any website that is not owned by you. • Cause the Website or portions of it to be displayed on, or appear to be displayed by, any other site, for example, framing, deep linking, or in-line linking. • Link to any part of the Website other than the homepage. • Otherwise take any action with respect to the materials on this Website that is inconsistent with any other provision of these Terms of Use. The website from which you are linking, or on which you make certain content available, must comply in all respects with the Content Standards set out in these Terms of Use. You agree to cooperate with us in causing any unauthorized framing or linking immediately to stop. We reserve the right to withdraw linking permission without notice. We may disable all or any social media features and any links at any time without notice in our discretion.
METHODS FOR ELIMINATION OF DOUBLE TAXATION Article 23
CLEC to CLEC Conversions for Unbundled Loops 2.1.11.1 The CLEC to CLEC conversion process for Loops may be used by ITC^DeltaCom when converting an existing Loop from another CLEC for the same End User. The Loop type being converted must be included in ITC^DeltaCom’s Agreement before requesting a conversion.
Procedure as to Rejected Goods On receipt of notification of rejection, Seller will immediately arrange to receive back the goods for shipment and return. However, within 5 days, Seller may have an agent inspect such goods for nonconformity; otherwise, such inspection will be made on return to Seller's storage facility. When such goods are confirmed or acquiesced in as nonconforming, Seller will ship conforming goods within 30 days of the notice of rejection unless Buyer earlier notifies Seller to forgo such shipment.
Incorporation of Administrative Code Provisions by Reference The provisions of Chapters 12B and 12C of the San Francisco Administrative Code are incorporated in this Section by reference and made a part of this Agreement as though fully set forth herein. Contractor shall comply fully with and be bound by all of the provisions that apply to this Agreement under such Chapters, including but not limited to the remedies provided in such Chapters. Without limiting the foregoing, Contractor understands that pursuant to §§12B.2(h) and 12C.3(g) of the San Francisco Administrative Code, a penalty of $50 for each person for each calendar day during which such person was discriminated against in violation of the provisions of this Agreement may be assessed against Contractor and/or deducted from any payments due Contractor.
Reporting and Payment Procedures Risk Summary Sheets for each risk and a monthly bordereau of all risks ceded shall be submitted to the Reinsurer within (twenty) 20 working days after the last day of each month. Any premium amounts due the Reinsurer shall be paid with the bordereau. Risk Summary Sheets for each insured shall include the following information:
Audit Requirements for Recipients of State Financial Assistance For purposes of this paragraph, the word "Contractor" shall be deemed to mean "nonstate entity," as that term is defined in section 4-230 of the Connecticut General Statutes. The Contractor shall provide for an annual financial audit acceptable to the Client Agency for any expenditure of State awarded funds made by the Contractor. Such audit shall include management letters and audit recommendations. The State Auditors of Public Accounts shall have access to all records and accounts for the fiscal year(s) in which the award was made. The Contractor shall comply with federal and State single audit standards as applicable.
PROCEDURE FOR APPROVAL OF SETTLEMENT 28. Acceptance of this Settlement Agreement shall be sought at a hearing of the Central Regional Council of the MFDA on a date agreed to by counsel for Staff and the Respondent.
Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.
