Payments Subject to Section 409A (a) Subject to this Section 4.3, payments or benefits under Section 4.1 shall begin only upon the date of a “separation from service” of the Executive (determined as set forth below) that occurs on or after the termination of the Executive’s employment. The following rules shall apply with respect to distribution of the payments and benefits, if any, to be provided to the Executive under Section 4.1: (i) It is intended that each installment of the payments and benefits provided under Section 4.1 shall be treated as a separate “payment” for purposes of Section 409A of the Code and the guidance issued thereunder (“Section 409A”). Neither the Company nor the Executive shall have the right to accelerate or defer the delivery of any such payments or benefits except to the extent specifically permitted or required by Section 409A. (ii) If, as of the date of the “separation from service” of the Executive from the Company, the Executive is not a “specified employee” (within the meaning of Section 409A), then each installment of the payments and benefits shall be made on the dates and terms set forth in Section 4.1. (iii) If, as of the date of the “separation from service” of the Executive from the Company, the Executive is a “specified employee” (within the meaning of Section 409A), then: (A) Each installment of the severance payments and benefits due under Section 4.1 that, in accordance with the dates and terms set forth herein, will in all circumstances, regardless of when the separation from service occurs, be paid within the short-term deferral period (as defined in Section 409A) shall be treated as a short-term deferral within the meaning of Treasury Regulation Section 1.409A-1(b)(4) to the maximum extent permissible under Section 409A; and (B) Each installment of the payments and benefits due under Section 4.1 that is not described in Section 4.3(a)(iii)(A) and that would, absent this subsection, be paid within the six-month period following the “separation from service” of the Executive from the Company shall not be paid until the date that is six months and one day after such separation from service (or, if earlier, the Executive’s death), with any such installments that are required to be delayed being accumulated during the six-month period and paid in a lump sum on the date that is six months and one day following the Executive’s separation from service and any subsequent installments, if any, being paid in accordance with the dates and terms set forth herein; provided, however, that the preceding provisions of this sentence shall not apply to any installment of payments and benefits if and to the maximum extent that that such installment is deemed to be paid under a separation pay plan that does not provide for a deferral of compensation by reason of the application of Treasury Regulation 1.409A-1(b)(9)(iii) (relating to separation pay upon an involuntary separation from service). Any installments that qualify for the exception under Treasury Regulation Section 1.409A-1(b)(9)(iii) must be paid no later than the last day of the Executive’s second taxable year following his taxable year in which the separation from service occurs. (b) The determination of whether and when a separation from service of the Executive from the Company has occurred shall be made in a manner consistent with, and based on the presumptions set forth in, Treasury Regulation Section 1.409A-1(h). Solely for purposes of this Section 4.3(b), “Company” shall include all persons with whom the Company would be considered a single employer as determined under Treasury Regulation Section 1.409A-1(h)(3).
Payments to Specified Employees Notwithstanding any other Section of this Agreement, if the Employee is a Specified Employee at the time of the Employee’s Separation from Service, payments or distribution of property to the Employee provided under this Agreement, to the extent considered amounts deferred under a non-qualified deferred compensation plan (as defined in Code Section 409A) shall be deferred until the six (6) month anniversary of such Separation from Service to the extent required in order to comply with Code Section 409A and Treasury Regulation 1.409A-3(i)(2).
How Are Contributions to a Xxxx XXX Reported for Federal Tax Purposes You must file Form 5329 with the IRS to report and remit any penalties or excise taxes. In addition, certain contribution and distribution information must be reported to the IRS on Form 8606 (as an attachment to your federal income tax return.)
How do the RMD Rules Impact my Designated Beneficiary or Beneficiaries The RMD rules provide for the determination of your designated beneficiary or beneficiaries as of September 30 of the year following your death. Consequently, any beneficiary may be eliminated for purposes of calculating the RMD by the distribution of that beneficiary’s benefit, through a valid disclaimer between your death and the end of September following the year of your death, or by dividing your IRA account into separate accounts for each of several designated beneficiaries you may have designated.
Public Benefit It is Reaction Retail’s understanding that the commitments it has agreed to herein, and actions to be taken by Reaction Retail under this Settlement Agreement, would confer a significant benefit to the general public, as set forth in Code of Civil Procedure § 1021.5 and Cal. Admin. Code tit. 11, § 3201. As such, it is the intent of Reaction Retail that to the extent any other private party initiates an action alleging a violation of Proposition 65 with respect to Reaction Retail’s failure to provide a warning concerning exposure to DEHP prior to use of the Products it has manufactured, distributed, sold, or offered for sale in California, or will manufacture, distribute, sell, or offer for sale in California, such private party action would not confer a significant benefit on the general public as to those Products addressed in this Settlement Agreement, provided that Reaction Retail is in material compliance with this Settlement Agreement.
File Management and Record Retention relating to CRF Eligible Persons or Households Grantee must maintain a separate file for every applicant, Eligible Person, or Household, regardless of whether the request was approved or denied. a. Contents of File: Each file must contain sufficient and legible documentation. Documents must be secured within the file and must be organized systematically.
Agreement Subject to Plan This Agreement is subject to the Plan. The terms and provisions of the Plan (including any subsequent amendments thereto) are hereby incorporated herein by reference thereto. In the event of a conflict between any term or provision contained herein and a term or provision of the Plan, the applicable terms and provisions of the Plan will govern and prevail. All definitions of words and terms contained in the Plan shall be applicable to this Agreement.
Traffic Not Subject to Reciprocal Compensation 7.2.1 Reciprocal Compensation shall not apply to interstate or intrastate Exchange Access (including, without limitation, Virtual Foreign Exchange Traffic (i.e., V/FX Traffic), Information Access, or exchange services for Exchange Access or Information Access. 7.2.2 Reciprocal Compensation shall not apply to Internet Traffic. 7.2.3 Reciprocal Compensation shall not apply to Toll Traffic, including, but not limited to, calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis. 7.2.4 Reciprocal Compensation shall not apply to Optional Extended Local Calling Scope Arrangement Traffic. 7.2.5 Reciprocal Compensation shall not apply to special access, private line, or any other traffic that is not switched by the terminating Party. 7.2.6 Reciprocal Compensation shall not apply to Tandem Transit Traffic. 7.2.7 Reciprocal Compensation shall not apply to Voice Information Service Traffic (as defined in Section 5 of the Additional Services Attachment). 7.2.8 Reciprocal Compensation shall not apply to traffic that is not subject to Reciprocal Compensation under Section 251(b)(5) of the Act. 7.2.9 Reciprocal Compensation shall not apply to Virtual Foreign Exchange Traffic (i.e., V/FX Traffic). As used in this Agreement, “Virtual Foreign Exchange Traffic” or “V/FX Traffic” is defined as calls in which an Onvoy Customer is assigned a telephone number with an NXX Code (as set forth in the LERG) associated with an exchange that is different than the exchange (as set forth in the LERG) associated with the actual physical location of such Customer’s station. For the avoidance of any doubt, Onvoy shall pay Frontier’s originating access charges for all V/FX Traffic originated by a Frontier Customer, and Onvoy shall pay Frontier’s terminating access charges for all V/FX Traffic originated by an Onvoy Customer.
Public Benefits 5.1 Developer to provide Public Benefits The Developer must, at its cost and risk, provide the Public Benefits to the City in accordance with this document.
Agreement Subject to Appropriation The City is obligated only to pay its obligations set forth in this Agreement as may lawfully be made from funds appropriated and budgeted for that purpose during the City’s then current fiscal year. The City’s obligations under this Agreement are current expenses subject to the “budget law” and the unfettered legislative discretion of the City concerning budgeted purposes and appropriation of funds. Should the City elect not to appropriate and budget funds to pay its Agreement obligations, this Agreement shall be deemed terminated at the end of the then-current fiscal year term for which such funds were appropriated and budgeted for such purpose and the City shall be relieved of any subsequent obligation under this Agreement. The parties agree that the City has no obligation or duty of good faith to budget or appropriate the payment of the City’s obligations set forth in this Agreement in any budget in any fiscal year other than the fiscal year in which this Agreement is executed and delivered. The City shall be the sole judge and authority in determining the availability of funds for its obligations under this Agreement. The City shall keep Consultant informed as to the availability of funds for this Agreement. The obligation of the City to make any payment pursuant to this Agreement is not a general obligation or indebtedness of the City. Consultant hereby waives any and all rights to bring any claim against the City from or relating in any way to the City’s termination of this Agreement pursuant to this section.