Procedure when supplemental budget changes estimated expenditures by more than 10 percent
(1)(a) If the amended estimated expenditures contained in an individual fund that is being changed by a supplemental budget made under ORS 294.471 (Supplemental budget in certain cases) differ by more than 10 percent from the expenditures in the budget as most recently amended prior to the supplemental budget, the governing body of the municipal corporation shall hold a public hearing on the supplemental budget.
(b) Notice of the hearing required under paragraph (a) of this subsection, including a summary of the changes proposed in the funds that differ by more than 10 percent from the expenditures in the budget as most recently amended prior to the supplemental budget, must be published not less than five days before the meeting.
(c) After the hearing, additional expenditures contained in the supplemental budget described in this subsection may not be made unless the governing body of the municipal corporation enacts appropriation ordinances or resolutions authorizing the expenditures. The ordinances or resolutions must state the need for and the purpose and amount of the appropriation.
(2) In counties having a tax supervising and conservation commission:
(a) The governing body of a municipal corporation may adopt a supplemental budget without submitting the budget to the commission prior to adoption.
(b) The commission is not required to hold a hearing on the budget.
(3) The Department of Revenue shall prescribe the form of the notice required under subsection (1) of this section. [2011 c.473 §22; 2013 c.420 §5]
Note: 294.473 (Procedure when supplemental budget changes estimated expenditures by more than 10 percent) was added to and made a part of 294.305 (Sections constituting Local Budget Law) to 294.565 (Failure to file copy of required budget, reports or other documents) by legislative action but was not added to any smaller series therein. See Preface to Oregon Revised Statutes for further explanation.
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.