Collection and Application of Project Revenues Sample Clauses

Collection and Application of Project Revenues 

Related to Collection and Application of Project Revenues

  • Authorization and Application of Overtime An employee who is required to work overtime shall be entitled to overtime compensation when the overtime worked is authorized in advance.

  • Data Collection and Usage The Company and the Service Recipient collect, process and use certain personal information about Participant, including, but not limited to, Participant’s name, home address, telephone number, email address, date of birth, social insurance number, passport or other identification number, salary, nationality, job title, any shares or directorships held in the Company, details of all awards granted under the Plan or any other entitlement to shares awarded, canceled, exercised, vested, unvested or outstanding in Participant’s favor (“Data”), for purposes of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is Participant’s consent.

  • COLLECTION OF CHARGES 16.1 A Sector Association may request the consent of the Administrator to collect charges due from Operators to the Administrator in respect of facilities under the charging scheme. 16.2 If a Sector Association wishes to collect charges due from an Operator to the Administrator under the charging scheme, the Sector Association may serve a notice in writing on the Administrator by the last working day in February in the calendar year in which the charges fall due. 16.3 A notice served under Rule 16.2 must specify the facilities in respect of which the Sector Association intends to collect charges, being not fewer than 50% of the facilities covered by an umbrella agreement. 16.4 Following receipt of the notice, the Administrator must: 16.4.1 consent to the Sector Association collecting charges; or 16.4.2 refuse consent to the Sector Association collecting charges, giving reasons for the decision. 16.5 If the Administrator consents to the Sector Association collecting charges the Sector Association must: 16.5.1 itemise charges separately in any invoices that it issues in respect of charges; 16.5.2 collect and remit all charges collected to the Administrator without deduction or set off by the last working day in September in each year; 16.5.3 prepare an annual report to the Administrator by the last working day in October in the year in which it has collected charges setting out which Operators it has collected charges from and which Operators have failed to pay charges due to the Sector Association. 16.6 A Sector Association must not actively pursue any outstanding charges after the last working day in September in any year in which they fall due. If a Sector Association receives charges after this date the Sector Association must accept the payment and remit this to the Environment Agency along with information identifying the Operator making the payment. 16.7 If a Sector Association fails to comply with any of its obligations under this Rule the Administrator may serve a notice on the Sector Association that consent to the Sector Association continuing to collect charges is withdrawn at the expiry of 20 working days from the date of the notice.

  • Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned Hospital location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE) when reporting on beds utilized at the Hospital. 2. Grantee shall budget and report expenditure data on the CARE Report III, incorporated by reference and posted at: ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇.▇▇▇/doing-business-hhs/provider- portals/behavioral-health-services-providers/behavioral-health-provider- resources/community-mental-health-contracts, within the Community Hospital strategy C.2.1.1 using line 764 - Project Private Beds. 3. Grantee shall ensure that patient registration, diagnostics, admission and discharge data is reported by using the CARE screens and action codes listed below: a. Screen: Campus-Based Assignments (Add/Change/Delete), Action Code: 305; b. Screen: Campus-Based Discharge/Community Placement (Add/Change/Delete), Action Code: 310; c. Screen: Joint Community Support Plan (Add/Change/Delete), Action Code: 312; d. Screen: Register Client, Action Code: 325; e. Screen: Diagnostics (Add/Change/Delete), Action Code: 330; f. Screen: Voluntary Admission and Commitment (Add/Change/Delete), Action Code 332; g. Screen: Campus-Based Residential ▇▇▇▇/Dorm (Add/Change/Delete), Action Code 615; and h. Screen: MH Bed Allocation Exception (Add/Change/Delete), Action Code 345. 4. For details related to the use of these screens and action codes, Grantee can refer to the CARE Reference Manual which can be found under the CARE (WebCARE) section on the portal at: ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇▇▇▇.▇▇.▇▇/helpGuide/Content/16_CARE/CAREWebCARE%20Refere nce%20Manual.htm

  • Application of Payments and Collections All items of payment received by Agent by 12:00 noon, Chicago, Illinois, time, on any Business Day shall be deemed received on that Business Day. All items of payment received after 12:00 noon, Chicago, Illinois, time, on any Business Day shall be deemed received on the following Business Day. Borrower irrevocably waives the right to direct the application of any and all payments and collections at any time or times hereafter received by Agent from or on behalf of Borrower, and Borrower does hereby irrevocably agree that Agent shall have the continuing exclusive right to apply and reapply any and all such payments and collections received at any time or times hereafter by Agent or its agent against the Obligations, in such manner as Agent may deem advisable, notwithstanding any entry by Agent or any Lender upon any of its books and records. Amounts received by the Agent shall be for further credit to the accounts of Lenders pursuant to the settlement procedures contained in subsection 3.1.3 of this Agreement. Notwithstanding the foregoing, payments and collections shall not be applied to Obligations consisting of Derivative Obligations or Product Obligations at any time that any other Obligations are then due and payable. If as the result of collections of Accounts as authorized by subsection 6.2.4 hereof or otherwise, a credit balance exists in the Loan Account, such credit balance shall not accrue interest in favor of Borrower, but shall be disbursed to Borrower or otherwise at Borrower's direction in the manner set forth in subsection 3.1.2, upon Borrower's request at any time, so long as no Default or Event of Default then exists. Agent may at its option, offset such credit balance against any of the Obligations upon and during the continuance of an Event of Default.