2015 ORS 295.031¹
Notice to public officials regarding adequacy of collateral

(1) Within three business days after the State Treasurer receives notice from a custodian pursuant to ORS 295.013 (Custodian's receipt) (2)(e), receives information from the Director of the Department of Consumer and Business Services or other sources under ORS 295.071 (Investigation by regulatory bodies other than State Treasurer) or 295.073 (Report to State Treasurer of actions that reduce net worth of depository), or otherwise receives information that indicates that a depository has failed to pledge adequate collateral with the depository’s custodian, the State Treasurer shall send written notice of the failure to each public official who has uninsured public funds on deposit in the depository that is the subject of the notice from the custodian or of the information the State Treasurer received.

(2) Within five business days after the State Treasurer receives notice from a custodian pursuant to ORS 295.013 (Custodian's receipt) (2)(f) that indicates that a depository has pledged adequate collateral with the depository’s custodian, the State Treasurer shall send written notice to each public official who was notified under subsection (1) of this section stating that the depository has adequate collateral. [2007 c.871 §2; 2009 c.821 §8; 2010 c.101 §9]

Atty. Gen. Opinions

Invest­ment of deferred compensa­tion funds, (1976) Vol 37, p 1284; county fair associa­tion as public corpora­tion, (1979) Vol 39, p 505

Chapter 295

Atty. Gen. Opinions

Invest­ment of funds by school district, (1974) Vol 36, p 827


1 Legislative Counsel Committee, CHAPTER 295—Depositories of Public Funds and Securities, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors295.­html (2015) (last ac­cessed Jul. 16, 2016).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2015, Chapter 295, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano295.­html (2015) (last ac­cessed Jul. 16, 2016).
 
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.