My WebLink
|
Help
|
About
|
Sign Out
15
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2011
>
041911
>
15
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/13/2011 12:30:24 PM
Creation date
4/13/2011 12:30:21 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
4/19/2011
DESTRUCT DATE
15Y
DOCUMENT NO
15
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
22
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
BACKGROUND <br /> Beginning in 1984, public entities were required to provide an annual accounting <br /> concerning the collection and use of all development impact fees. Effective January 1, <br /> 1989, AB1600 (Government Code Section 66000 et seq.) established new accounting <br /> guidelines regarding the imposition and use of development impact fees. Effective <br /> January 1, 1997, SB1693 made certain changes to AB1600 and clarified and expanded <br /> the responsibilities of local agencies. <br /> One of the mandated accounting guidelines, as stated in Government Code Section <br /> 66006(a), provides that a local agency shall establish separate capital facility accounts <br /> for each improvement funded by development impact fees. Any interest income earned <br /> by funds in such an account shall also be deposited in that account. Each local agency <br /> is required within 180 days after the financial year is closed, (the books for fiscal year <br /> ending June 30, 2010 were closed on January 13, 2011) to make available to the public <br /> the following information for each separate account: (1) the account's beginning and <br /> ending balance; (2) the amount of fees, interest, and other income in the account; (3) <br /> the amount of expenditure for each public facility or improvement made from the <br /> account; (4) the total percentage of the cost of the improvement that was funded with <br /> the fees; (5) the date construction will commence if sufficient funds have been collected; <br /> (6) a description of any interfund transfers or loans made from an account; and (7) the <br /> amount of refunds made from the account. Appendix A provides this information for <br /> funds held on June 30, 2010. Appendix B provides the Master Fee Schedule for the <br /> development impact fees that are subject to AB1600 and SB1693. <br /> In addition, Government Code 66006 Section (b)(2) requires the report to be included <br /> on the agenda at a public meeting not less than fifteen (15) days after the information <br /> was made available to the public. Staff made the information available to the public <br /> starting on April 1, 2011 and also published the public hearing notice in the Valley <br /> Times on that date. Staff also mailed the notice of the public hearing and a copy of the <br /> report to interested parties who had filed a written request with the City for the mailed <br /> notice. <br /> DISCUSSION <br /> The City uses Fund Accounting to segregate development impact fees subject to <br /> AB1600 from other City funds. Interest income is allocated to each individual fund <br /> based on its own cash balance. The City utilizes the following funds to track <br /> development related revenues: <br /> Miscellaneous Capital Improvement Fund (Fund 154) — This fund is utilized to account <br /> for the Public Facilities fee. Facilities projects and equipment required to service new <br /> development are funded from this fee. When a project serves both new and existing <br /> development, only the portion related to new development is charged against this fund. <br /> The other portions of the project are funded by other sources, such as the General <br /> Fund. Fund balance, revenues, expenditures and transfers for this fund for fiscal years <br /> 2005/06 through 2009/10 are detailed in Appendix A. <br /> Page 2 of 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.