Noncompliance Explanation Sample Clauses

Noncompliance Explanation. If the annuity does not comply with a specific product outline provision or if the Company has an alternate interpretation of a product outline provision, the submission letter must identify the provision and provide a complete explanation of the Company’s position on the issue. Such submissions may not be submitted through the Circular Letter 6 (2004) certified process unless the Department has given permission.
AutoNDA by SimpleDocs
Noncompliance Explanation. If the application form does not comply with a specific provision of this Outline, the SERFF Filing Description must identify the provision and provide a complete explanation of the insurer’s position on the issue. Such submissions may not be submitted through the Circular Letter 6 (2004) certified process unless the Department has given permission. Attachments

Related to Noncompliance Explanation

  • Noncompliance Standards The AGENCY shall be responsible for adhering to all terms and conditions of this Contract. Noncompliance may result in penalties as stipulated in Attachment “C”.

  • Noncompliance Except as otherwise provided for in Sections 10.1, 10.3 and 10.5(b), (a) failure or neglect of any Borrower or any Guarantor or any Person to perform, keep or observe any term, provision, condition, covenant herein contained, or contained in any Other Document or any other agreement or arrangement, now or hereafter entered into between any Borrower or any Guarantor or such Person, and Agent or any Lender, or (b) failure or neglect of any Borrower to perform, keep or observe any term, provision, condition or covenant, contained in Sections 4.6, 4.7, 4.9, 6.1, 6.3, 6.4, 9.4 or 9.6 hereof which is not cured within twenty (20) days from the occurrence of such failure or neglect;

  • GAAP Compliance Contractor maintains an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles.

  • DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).

  • OFAC Compliance (a) Tenant represents and warrants that (a) Tenant and each person or entity owning an interest in Tenant is (i) not currently identified on the Specially Designated Nationals and Blocked Persons List maintained by the Office of Foreign Assets Control, Department of the Treasury (“OFAC”) and/or on any other similar list maintained by OFAC pursuant to any authorizing statute, executive order or regulation (collectively, the “List”), and (ii) not a person or entity with whom a citizen of the United States is prohibited to engage in transactions by any trade embargo, economic sanction, or other prohibition of United States law, regulation, or Executive Order of the President of the United States, (b) none of the funds or other assets of Tenant constitute property of, or are beneficially owned, directly or indirectly, by any Embargoed Person (as hereinafter defined), (c) no Embargoed Person has any interest of any nature whatsoever in Tenant (whether directly or indirectly), (d) none of the funds of Tenant have been derived from any unlawful activity with the result that the investment in Tenant is prohibited by law or that the Lease is in violation of law, and (e) Tenant has implemented procedures, and will consistently apply those procedures, to ensure the foregoing representations and warranties remain true and correct at all times. The term “

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Reporting Violations a) When appropriate, faculty members will submit timely written communication to their immediate supervisor any condition that comes to their attention that may, in their judgment, pose a threat to the health or safety of any person associated with the District.

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