My WebLink
|
Help
|
About
|
Sign Out
Home
Search
05-06-2019 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2019
>
05-06-2019 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/30/2021 1:08:47 PM
Creation date
5/7/2019 11:39:32 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
05/06/2019
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
189
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
The information provided here is of a general nature and is not intended to address the specific circumstances of any individual or entity. In <br />specific circumstances, the services of a professional should be sought. Baker Tilly Virchow Krause, LLP trading as Baker Tilly is a member <br />of the global network of Baker Tilly International Ltd., the members of which are separate and independent legal entities. © 2018 Baker Tilly <br />Virchow Krause, LLP <br />assistance. Analysis of the proformas include review of the development budget, projected operating revenues <br />and expenditures, and the project’s capacity to support annual debt service on the permanent financing. <br /> <br />The purpose of evaluating the operating proformas is to understand the potential returns to the developer <br />through the initial development of the project and the operation of the enterprise over a 10-year period. Ten <br />years may not be indicative of the developer’s intended investment period as the financing is for a 40-year term <br />and the developer intends to retain ownership of the project. However, when analysing the potential investment <br />and projected returns, 10 years is a reasonable term for review. <br /> <br />Generally, should the rates of return lie below a reasonable range without assistance; we could assume the <br />project as proposed would not move forward without assistance. Should the returns lie within a reasonable <br />range with the assistance, we could assume the amount of assistance tested is appropriate for the project. All <br />such estimates should be viewed as general indicators of performance and not exact forecasts. The number of <br />current and future variables affecting these estimates and actual results are great. There are no set rate of <br />return benchmarks that dictates whether a project needs TIF assistance or not; however, there are <br />market/industry standards for certain types of projects, as well as more specific investor/developer thresholds <br />that need to be achieved. <br /> <br />An additional measure of project feasibility is the Debt Coverage Ratio (DCR), which is a calculation detailing <br />the ratio by which operating income exceeds the debt-service payments for the project. If the DCR is greater <br />than 1.0 it indicates the project has operating income that is greater than the debt-service payment by some <br />margin; conversely if the DCR is less than 1.0 it indicates the project is incapable of meeting its debt-service <br />payment and would need to seek additional revenue sources in order to pay its debt. Typical lending standards <br />will require a DCR of significantly greater than 1.0 as a measure of cushion in the event actual revenues and <br />expenses are different than projected. <br /> <br />The developer has demonstrated that without assistance, it is able to obtain financing of $61 million with the <br />remaining approximately $16+ million financed by equity. Based on the annual operating revenues and <br />expenses and debt service payments on the permanent financing, it would be not be financially feasible, <br />generating below-market returns to the developer as the project is not able to support the entire $77.9 million of <br />project costs. With the tax increment as additional annual revenues, the developer would be able to obtain $66 <br />million of financing leaving approximately $11 million necessary as equity. Tax increment would provide <br />additional cash flow to support operating expenses and debt service and provide a reasonable return to the <br />developer. In addition, upon project stabilization the project is expected to have debt coverage of 1.25x. <br /> <br />Project Financing <br />There are generally two ways in which assistance can be provided for most projects, either upfront or on a pay- <br />as-you-go basis. With upfront financing, the City would finance a portion of the developer’s initial project costs <br />through the issuance of bonds or as an internal loan. Future tax increment would be collected by the City and <br />used to pay debt service on the bonds or repayment of the internal loan. With pay-as-you-go financing, the <br />developer would finance all project costs upfront and would be reimbursed over time for a portion of those costs <br />as revenues are available. <br /> <br />Pay-as-you-go-financing is generally more acceptable than upfront financing for the City because it shifts the <br />risk for repayment to the developer. If tax increment revenues are less than originally projected, the developer <br />receives less and therefore bears the risk of not being reimbursed the full amount of their financing. However, <br />in some cases pay as you go financing may not be financially feasible. With bonds, the City would still need to <br />make debt service payments and would have to use other sources to fill any shortfall of tax increment revenues. <br />With internal financing, the City reimburses the loan with future revenue collections and may risk not repaying <br />itself in full if tax increment revenues are not sufficient. The developer’s financial information includes pay-as- <br />you-go financing. <br />
The URL can be used to link to this page
Your browser does not support the video tag.