Local Church’s Payment Obligations At Closing or otherwise prior to or on the Disaffiliation Date, Local Church shall pay to the Annual Conference, in a manner specified by Annual Conference, the following:
Repayment Obligation In the event that any State and/or federal funds are deferred and/or disallowed as a result of any audits or expended in violation of the laws applicable to the expenditure of such funds, the Contractor shall be liable to the Agency for the full amount of any claim disallowed and for all related penalties incurred. The requirements of this paragraph shall apply to the Contractor as well as any subcontractors.
Client Obligations 3.1 The Client shall:
Recipient Obligations 2.1 The Recipient agrees to support the Project in accordance with this Agreement.
Payment Obligation (a) The Subscriber shall bear the obligation to pay the Service Fee to SORACOM from the day when SORACOM starts to provide the Subscriber with the telecommunication channel pursuant to this Agreement.
Merchant Obligations (1) Merchant shall provide a valid, working administrative email address on enrolment. Any changes to Merchant’s account must be made via the administrative email address provided upon enrolment. The security of Merchant’s account is dependent in part upon Merchant maintaining the security of such administrative email address. Merchant shall be fully and solely responsible for any unauthorized changes to Merchant’s account via this email address. (2) Merchant will be given an ID code and password to allow Merchant to have access to Gateway Services. Merchant shall be fully and solely responsible for the establishment and maintenance of procedures to insure the control and confidentiality of identification codes and passwords and other access procedures (“Codes”). FAILURE TO PROTECT THE CODES MAY ALLOW UNAUTHORIZED PARTIES TO ACCESS THE GATEWAY SERVICES. Merchant is required to put in place internal procedures to limit such risk, including, but not limited to (a) changing the password at least once every 120 calendar days; (b) keeping every identification code under secure conditions; and (c) not keeping, in any form or in any place, any list of passwords. Merchant agrees to comply with any access or identification procedures and security protocols established from time to time by ISO, and if Merchant believes that any Code or security procedures has or may have become known by an unauthorized person (whether employed by Merchant or not), Merchant shall immediately notify ISO by telephone and confirm to ISO in writing such oral notification within 24 hours.
Joint Obligations A. The University and the student share the responsibility for ensuring the quality of life within the residence halls, their maintenance, furnishings and facilities, and for a physical environment secure from fire and other hazards. The University will work with students to promote effective security of persons and property in the residence halls.
City Obligations 26.1 City shall provide full information in a timely manner regarding requirements for and limitations on projects and work tasks. With regard to subcontractor liens, City shall furnish to Engineer, within fifteen (15) days after receipt of a written request, information necessary and relevant for Engineer to evaluate, give notice of, or enforce lien.