E-VERIFY CERTIFICATION Pursuant to Executive Order RP-80, Engineer certifies and ensures that for all contracts for services, Engineer shall, to the extent permitted by law, utilize the United States Department of Homeland Security’s E-Verify system during the term of this agreement to determine the eligibility of:
1. All persons employed by Engineer during the term of this agreement to perform duties within the State of Texas; and
2. All persons, including subcontractors, assigned by Engineer to perform work pursuant to this agreement. Violation of this provision constitutes a material breach of this agreement.
AS9100 Certification AS9100 Certification, specifies requirements for a quality management system to demonstrate the Contractor’s ability to consistently meet the customer requirements as well as statutory and regulatory requirements for the aerospace industry. An AS9100 Certification, is not mandatory; however, Contractors who desire to compete for work within the aerospace industry are encouraged to have AS9100 Certification, during the entire term of OASIS. The Contractor shall notify the OASIS CO, in writing, if there are any changes in the status of their AS9100 Certification, and provide the reasons for the change and copies of audits from an AS9100 Certification Body, as applicable. If only part of a Contractor’s organization is AS9100, certified, the Contractor shall make the distinction between which business units or sites and geographic locations have been certified.
Contractor Certification The Department may, at its option, terminate the Contract if the Contractor is found to have submitted a false certification as provided under section 287.135(5), F.S., or been placed on the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List, or been engaged in business operations in Cuba or Syria, or to have been placed on the Scrutinized Companies that Boycott Israel List or is engaged in a boycott of Israel.
Contractor Certification Clauses Contractor represents and warrants that the following statements are true. During the term of the Agreement, Contractor shall not take an action, or omit to perform any act, that results in a representation and warranty becoming untrue. Contractor shall promptly notify the Judicial Council if any representation and warranty becomes untrue.
A. No Gratuities. Contractor has not directly or indirectly offered or given any gratuities (in the form of entertainment, gifts, or otherwise) to any Judicial Council personnel with a view toward securing this Agreement or securing favorable treatment with respect to any determinations concerning the performance of this Agreement.
Certification Requirements The hospice program certifies and attaches hereto documentation that:
(a) it is Medicare approved and meets all Medicare conditions of participation (42 CFR 418); and
(b) is licensed pursuant to any applicable state or local law.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
Certification of Compliance San Diego Municipal Code section 22.4225 requires each Bidder to fill out and file a living wage certification with the Living Wage Program Manager within thirty (30) days of Award of the Contract.
Accountants' Certification together with each delivery of consolidated financial statements of Company and its Subsidiaries pursuant to subdivision (iii) above, a written statement by the independent certified public accountants giving the report thereon (a) stating that their audit examination has included a review of the terms of this Agreement and the other Loan Documents as they relate to accounting matters, (b) stating whether, in connection with their audit examination, any condition or event that constitutes an Event of Default or Potential Event of Default has come to their attention and, if such a condition or event has come to their attention, specifying the nature and period of existence thereof; provided that such accountants shall not be liable by reason of any failure to obtain knowledge of any such Event of Default or Potential Event of Default that would not be disclosed in the course of their audit examination, and (c) stating that based on their audit examination nothing has come to their attention that causes them to believe either or both that the information contained in the certificates delivered therewith pursuant to subdivision (iv) above is not correct or that the matters set forth in the Compliance Certificates delivered therewith pursuant to clause (b) of subdivision (iv) above for the applicable Fiscal Year are not stated in accordance with the terms of this Agreement;
Owner Certification During the term of this Contract, the Owner certifies that:
a) The Owner will, at all times, maintain the Unit and premises, including common areas accessible to the Tenant, in decent, safe, and sanitary condition and compliant with applicable state or local codes and rental housing requirements; and
b) The Owner will comply in all material respects with this Contract; and
c) The Unit is leased to and, to the best of the Owner’s knowledge, is occupied by the Tenant; and,
d) Owner has taken no action and will not take any action to terminate the Lease and cause the Tenant to vacate the Unit without providing written notice of such action to the Tenant and the Program Administrator; and
e) Other than the Tenant’s Contribution, the Owner has not received and will not receive any payments or other consideration (from the Tenant, HUD, or any other public or private source) for rental of the Unit during the Term of this Contract except as identified in Exhibit A; and
f) To the best of the Owner’s knowledge, the Unit is used solely as the Tenant’s principal place of residence; and
g) The Tenant does not own or have any interest in the Unit; and
h) The Owner (including a principal or other interested party) is not the parent, child, grandparent, grandchild, sister, or brother of any member of the family of the Tenant, unless the Program Administrator has determined (and has notified the Owner and the Tenant of such determination) that approving rental of the unit, notwithstanding such relationship, would provide reasonable accommodation for a family member who is a person with disabilities.
CHILD SUPPORT CERTIFICATION Under Section 231.006, Texas Family Code, the Engineer certifies that the individual or business entity named in this contract, bid, or application is not ineligible to receive the specified grant, loan, or payment and acknowledges that this contract may be terminated and payment may be withheld if this certification is inaccurate. If the above certification is shown to be false, the Engineer is liable to the state for attorney’s fees, the cost necessary to complete the contract, including the cost of advertising and awarding a second contract, and any other damages provided by law or the contract. A child support obligor or business entity ineligible to receive payments because of a payment delinquency of more than thirty (30) days remains ineligible until: all arrearages have been paid; the obligor is in compliance with a written repayment agreement or court order as to any existing delinquency; or the court of continuing jurisdiction over the child support order has granted the obligor an exemption from Subsection (a) of Section 231.006, Texas Family Code, as part of a court- supervised effort to improve earnings and child support payments.
