Elawyers Elawyers
Ohio| Change
Find Similar Cases by Filters
You can browse Case Laws by Courts, or by your need.
Find 47 similar cases
MARIAN TOWERS, LTD. vs FLORIDA HOUSING FINANCE CORPORATION, 16-004133BID (2016)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Jul. 22, 2016 Number: 16-004133BID Latest Update: Nov. 28, 2016

The Issue The issue for determination in this consolidated bid protest proceeding is whether the Florida Housing Finance Corporation’s (“FHFC”) intended award of tax credits for the preservation of existing affordable housing developments was clearly erroneous, contrary to competition, arbitrary, or capricious.

Findings Of Fact FHFC and Affordable Housing Tax Credits FHFC is a public corporation that finances affordable housing in Florida by allocating and distributing low income housing tax credits. See § 420.504(1), Fla. Stat. (providing that FHFC is “an entrepreneurial public corporation organized to provide and promote the public welfare by administering the governmental function of financing or refinancing housing and related facilities in this state.”); § 420.5099(2), Fla. Stat. (providing that “[t]he corporation shall adopt allocation procedures that will ensure the maximum use of available tax credits in order to encourage development of low-income housing in the state, taking into consideration the timeliness of the application, the location of the proposed housing project, the relative need in the area for low-income housing and the availability of such housing, the economic feasibility of the project, and the ability of the applicant to proceed to completion of the project in the calendar year for which the credit is sought.”). The tax credits allocated by FHFC encourage investment in affordable housing and are awarded through competitive solicitations to developers of qualifying rental housing. Tax credits are not tax deductions. For example, a $1,000 deduction in a 15-percent tax bracket reduces taxable income by $1,000 and reduces tax liability by $150. In contrast, a $1,000 tax credit reduces tax liability by $1,000. Not surprisingly, the demand for tax credits provided by the federal government exceeds the supply. A successful applicant/developer normally sells the tax credits in order to raise capital for a housing development. That results in the developer being less reliant on debt financing. In exchange for the tax credits, a successful applicant/developer must offer affordable rents and covenant to keep those rents at affordable levels for 30 to 50 years. The Selection Process FHFC awards tax credits through competitive solicitations, and that process is commenced by the issuance of a Request for Applications (“RFA”). Florida Administrative Code Rule 67-60.009(2) provides that unsuccessful applicants for tax credits “may only protest the results of the competitive solicitation process pursuant to the procedures set forth in Section 120.57(3), F.S., and Chapter 28-110, F.A.C.” For purposes of section 120.57(3), an RFA is equivalent to a “request for proposal.” See Fla. Admin. Code R. 67.60.009(4), F.A.C. FHFC issued RFA 2015-111 on October 23, 2015, and responses from applicants were due on December 4, 2015. Through RFA 2015-111, FHFC seeks to award up to $5,901,631 of tax credits to qualified applicants that commit to preserve existing affordable multifamily housing developments for the demographic categories of “Families,” “the Elderly,” and “Persons with a Disability.” FHFC only considered an application eligible for funding from RFA 2015-111, if that particular application complied with certain content requirements. FHFC ranked all eligible applications pursuant to an “Application Sorting Order” set forth in RFA 2015-111. The first consideration was the applicants’ scores. Each application could potentially receive up to 23 points based on the developer’s experience and the proximity to services needed by the development’s tenants. Applicants demonstrating that their developments received funding from a U.S. Department of Agriculture (“USDA”) Rural Development program known as RD 515 were entitled to a 3.0 point proximity score “boost.” That proximity score boost was important because RFA 2015-111 characterized counties as small, medium, or large. Applications associated with small counties had to achieve at least four proximity points to be considered eligible for funding. Applications associated with medium-sized counties and those associated with large counties had to achieve at least seven and 10.25 proximity points respectively in order to be considered eligible for funding. Because it is very common for several tax credit applicants in a particular RFA to receive identical scores, FHFC incorporated a series of “tie-breakers” into RFA 2015-111. The tie-breakers for RFA 2015-111, in order of applicability, were: First, by Age of Development, with developments built in 1985 or earlier receiving a preference over relatively newer developments. Second, if necessary, by a Rental Assistance (“RA”) preference. Applicants were to be assigned an RA level based on the percentage of units receiving rental assistance through either a U.S. Department of Housing and Urban Development (“HUD”) or USDA Rural Development program. Applicants with an RA level of 1, 2, or 3 (meaning at least 75 percent of the units received rental assistance) were to receive a preference. Third, by a Concrete Construction Funding Preference, with developments incorporating certain specified concrete or masonry structural elements receiving the preference. Fourth, by a Per Unit Construction Funding Preference, with applicants proposing at least $32,500 in Actual Construction Costs per unit receiving the preference. Fifth, by a Leveraging Classification favoring applicants requiring a lower amount in housing credits per unit than other applicants. Generally, the least expensive 80 percent of eligible applicants were to receive a preference over the most expensive 20 percent. Sixth, by an Applicant’s specific RA level, with Level 1 applicants receiving the most preference and Level 6 the least. Seventh, by a Florida Job Creation Preference, which estimated the number of jobs created per $1 million of housing credit equity investment the developments were to receive based on formulas contained in the RFA. Applicants achieving a Job Creation score of at least 4.0 were to receive the preference. Eighth, by lottery number, with the lowest (smallest) lottery number receiving the preference. Rental assistance from the USDA or HUD is provided to existing developments in order to make up for shortfalls in monthly rent paid by tenants. For example, if an apartment’s base rent is $500 per month and the tenant’s income limits him or her to paying only $250 towards rent, then the USDA or HUD rental assistance pays the other $250 so that the total rent received by the development is $500. As evident from the tie-breakers incorporated into RFA 2015-111, the amount of rental assistance, or “RA Level,” played a prominent role in distinguishing between RFA 2015-111 applicants having identical scores. RFA 2015-111 required that applicants demonstrate RA Levels by providing a letter containing the following information: (a) the development’s name; (b) the development’s address; (c) the year the development was built; (d) the total number of units that currently receive PBRA and/or ACC;/3 (e) the total number of units that would receive PBRA and/or ACC if the proposed development were to be funded; (f) all HUD or RD financing program(s) originally and/or currently associated with the existing development; and (g) confirmation that the development had not received financing from HUD or RD after 1995 when the rehabilitation was at least $10,000 per unit in any year. In order to determine an applicant’s RA Level Classification, RFA 2015-111 further stated that Part of the criteria for a proposed Development that qualifies as a Limited Development Area (LDA) Development to be eligible for funding is based on meeting a minimum RA Level, as outlined in Section Four A.7.c of the RFA. The total number of units that will receive rental assistance (i.e., PBRA and/or ACC), as stated in the Development Category qualification letter provided as Attachment 7, will be considered to be the proposed Development’s RA units and will be the basis of the Applicant’s RA Level Classification. The Corporation will divide the RA units by the total units stated by the Applicant at question 5.e. of Exhibit A, resulting in a Percentage of Total Units that are RA units. Using the Rental Assistance Level Classification Chart below, the Corporation will determine the RA Level associated with both the Percentage of Total Units and the RA units. The best rating of these two (2) levels will be assigned as the Application’s RA Level Classification. RFA 2015-111 then outlined a Rental Assistance Level Classification Chart to delineate between the RA Levels. That chart described six possible RA Levels, with one being developments that have the most units receiving rental assistance and six pertaining to developments with the fewest units receiving rental assistance. A development with at least 100 rental assistance units and greater than 50 percent of the total units receiving rental assistance was to receive an RA Level of 1. FHFC also utilized a “Funding Test” to assist in the selection of applications for funding. The Funding Test required that the amount of unawarded housing credits be enough to satisfy any remaining applicant’s funding request. In other words, FHFC prohibited partial funding. In addition, RFA 2015-111 applied a “County Award Tally” designed to prevent a disproportionate concentration of funded developments in any one county. As a result, all other applicants from other counties had to receive an award before a second application from a particular county could be funded. After ranking of the eligible applicants, RFA 2015-111 set forth an order of funding selection based on county size, demographic category, and the receipt of RD 515 financing. The Order was: One RD 515 Development (in any demographic category) in a medium or small county; One Non-RD 515 Development in the Family Demographic Category (in any size county); The highest ranked Non-RD 515 application or applications with the demographic of Elderly or Persons with a Disability; and If funding remains after all eligible Non- RD 515 applicants are funded, then the highest ranked RD 515 applicant in the Elderly demographic (or, if none, then the highest ranked RD 515 applicant in the Family demographic). Draft versions of every RFA are posted on-line in order for stakeholders to provide FHFC with their comments. In addition, every RFA goes through at least one workshop prior to being finalized. FHFC often makes changes to RFAs based on stakeholder comments. No challenge was filed to the terms, conditions, or requirements of RFA 2015-111. A review committee consisting of FHFC staff members reviewed and scored all 24 applications associated with RFA 2015-111. During this process, FHFC staff determined that none of the RD-515 applicants satisfied all of the threshold eligibility requirements. On June 24, 2016, FHFC’s Board of Directors announced its intention to award funding to five applicants, subject to those applicants successfully completing the credit underwriting process. Pineda Village in Brevard County was the only successful applicant in the Non-RD 515 Family Demographic. The four remaining successful applicants were in the Non-RD 515 Elderly or Persons with Disability Demographic: Three Round Tower in Miami-Dade County; Cathedral Towers in Duval County; Isles of Pahokee in Palm Beach County; and Lummus Park in Miami- Dade County. The randomly-assigned lottery number tie-breaker played a role for the successful Non-RD 515 applicants with Three Round Tower having lottery number one, Cathedral Towers having lottery number nine, and Isles of Pahokee having lottery number 18. While Lummus Park had a lottery number of 12, the County Award Tally prevented it from being selected earlier because Three Round Tower had already been selected for funding in Miami-Dade County. However, after the first four applicants were funded, only $526,880 of credits remained, and Lummus Park was the only eligible applicant with a request small enough to be fully funded. All Petitioners timely filed Notices of Protest and petitions for administrative proceedings. The Challenge by Woodcliff, Colonial, and St. Johns Woodcliff is seeking an award of tax credits in order to acquire and preserve a 34-unit development for elderly residents in Lake County.4/ Colonial is seeking an award of tax credits in order to acquire and preserve a 30-unit development for low-income families in Lake County.5/ St. Johns is seeking an award of tax credits to acquire and preserve a 48-unit development for elderly residents in Putnam County.6/ FHFC deemed Woodcliff, Colonial and St. Johns to be ineligible because of a failure to demonstrate the existence or availability of a particular source of financing relied upon in their applications. Specifically, FHFC determined that the availability of USDA RD 515 financial assistance was not properly documented. For applicants claiming the existence of RD 515 financing, RFA 2015-111 stated: If the proposed Development will be assisted with funding under the United States Department of Agriculture RD 515 Program and/or RD 538 Program, the following information must be provided: Indicate the applicable RD Program(s) at question 11.b.(2) of Exhibit A. For a proposed Development that is assisted with funding from RD 515 and to qualify for the RD 515 Proximity Point Boost (outlined in Section Four A.6.b.(1)(b) of the RFA), the Applicant must: Include the funding amount at the USDA RD Financing line item on the Development Funding Pro Forma (Construction/Rehab Analysis and/or Permanent Analysis); and Provide a letter from RD, dated within six (6) months of the Application Deadline, as Attachment 17 to Exhibit A, which includes the following information for the proposed Preservation Development: Name of existing development; Name of proposed Development; Current RD 515 Loan balance; Acknowledgment that the property is applying for Housing Credits; and Acknowledgment that the property will remain in the USDA RD 515 loan portfolio. (emphasis added). FHFC was counting on the letter mentioned directly above to function as proof that: (a) there was RD 515 financing in place when the letter was issued; and that (b) the RD 515 financing would still be in place as of the application deadline for RFA 2015-111. FHFC deemed Woodcliff, Colonial and St. Johns ineligible because their RD letters were not dated within six months of the December 4, 2015, deadline for RFA 2015-111 applications. The Woodcliff letter was dated May 15, 2015, the Colonial letter was dated May 15, 2015, and the St. Johns letter was dated May 5, 2015. FHCA had previously issued RFA 2015-104, which also proposed to award Housing Credit Financing for the Preservation of Existing Affordable Multifamily Housing Developments. The deadline for RFA 2015-104 was June 23, 2015, and Woodcliff, Colonial, and St. Johns applied using the same USDA letter that they used in their RFA 2015-111 applications. Woodcliff, Colonial, and St. Johns argued during the final hearing that FHFC should have accepted their letters because: (a) they gained no competitive advantage by using letters that were more than six months old; (b) waiving the six- month “shelf life” requirement would enable FHFC to satisfy one of its stated goals for RFA 2015-111, i.e., funding of an RD 515 development; and (c) other forms of financing (such as equity investment) have no “freshness” or “shelf life” requirement. However, it is undisputed that no party (including Woodcliff, Colonial, and St. Johns) challenged any of the terms, conditions, or requirements of RFA 2015-111. In addition, Kenneth Reecy (FHFC’s Director of Multifamily Programs) testified that there must be a point at which FHFC must ensure the viability of the information submitted by applicants. If the information is “too old,” then it may no longer be relevant to the current application process. Under the circumstances, it was not unreasonable for FHFC to utilize a six-month shelf life for USDA letters.7/ Furthermore, Mr. Reecy testified that excusing Woodcliff, Colonial, and St. Johns’ noncompliance could lead to FHFC excusing all deviations from all other date requirements in future RFAs. In other words, applicants could essentially rewrite those portions of the RFA, and that would be an unreasonable result. Excusing the noncompliance of Woodcliff, Colonial, and St. Johns could lead to a “slippery slope” in which any shelf- life requirement has no meaning. The letters utilized by Woodcliff, Colonial, and St. Johns were slightly more than six months old. But, exactly when would a letter become too old to satisfy the “shelf life” requirement? If three weeks can be excused today, will four weeks be excused next year? St. Elizabeth’s and Marian Towers’ Challenge St. Elizabeth is seeking low-income housing tax credit financing in order to acquire and preserve a 151-unit development for elderly residents in Broward County, Florida. Marian Towers is an applicant for RFA 2015-111 funding seeking low-income housing tax credits to acquire and preserve a 220-unit development for elderly residents in Miami-Dade County, Florida. The same developer is associated with the St. Elizabeth and Marian Towers projects. In its scoring and ranking process, FHFC assigned St. Elizabeth an RA Level of two. RFA 2015-111 requires that Applicants demonstrate RA Levels by providing a letter from HUD or the USDA with specific information. That information is then used to establish an RA Level for the proposed development. As noted above, the RFA requires the letter to contain several pieces of information, including: (a) the total number of units that currently receive PBRA and/or ACC; and (b) the total number of units that will receive PBRA and/or ACC if the proposed development is funded. RFA 2015-111 provided that a development with at least 100 rental units would receive an RA Level of one. St. Elizabeth included with its application a letter from HUD’s Miami field office stating in pertinent part that: Total number of units that currently receive PBRA and/or ACC: 99 units. Total number of units that will receive PBRA and/or ACC if the proposed Development is funded: 100 units*. The asterisk in the preceding paragraph directed readers of St. Elizabeth’s HUD letter to a paragraph stating that: HUD is currently processing a request from the owner to increase the number of units subsidized under a HAP Contract to 100 by transferring budget authority for the one additional unit from another Catholic Housing Services Section 8 project under Section 8(bb) in accordance with Notice H-2015-03. Because of the foregoing statement from HUD, FHFC concluded that St. Elizabeth did not have 100 units receiving rental assistance as of the application deadline. Accordingly, FHFC used 99 units as the total number of units that would receive rental assistance when calculating St. Elizabeth’s RA Level, and that led to FHFC assigning an RA Level of two to St. Elizabeth’s application.8/ If St. Elizabeth had been deemed eligible and if FHFC had used 100 units as the total number of units that would receive rental assistance, then St. Elizabeth would have received an RA Level of one. Given the application sorting order and the selection process outlined in RFA 2015-111, St. Elizabeth (with a lottery number of six) would have been recommended for funding by FHFC, and that outcome would have resulted in Intervenors Isles of Pahokee and Lummus Park losing their funding. St. Elizabeth asserted during the final hearing that the 100th unit had obtained rental assistance financing since the application deadline on December 4, 2015. However, FHFC could only review, score, and calculate St. Elizabeth’s RA Level based on the information available as of the application deadline. While St. Elizabeth argues that the asterisk paragraph sets forth a “condition,” Kenneth Reecy (FHFC’s Director of Multifamily Housing) agreed during the final hearing that the asterisk paragraph was more akin to information that was not explicitly required by RFA 2015-111. FHFC did not use that additional information to declare St. Elizabeth’s application ineligible for funding. Despite being assigned an RA Level of two, St. Elizabeth’s application still could have been selected for funding because RFA 2015-111 merely established RA Level as a basis for breaking ties among competing applications. However, too many applicants for RFA 2015-111 had identical scores, and RFA 2015-111’s use of RA Level as a tiebreaker forced St. Elizabeth’s application out of the running. Under the circumstances, FHFC’s treatment of St. Elizabeth’s application was not clearly erroneous, contrary to competition, arbitrary, or capricious. As noted above, tie- breakers are very important, because there is often very little to distinguish one application for tax credits from another. Given that there was a degree of uncertainty about whether St. Elizabeth’s would have 100 qualifying units, FHFC acted reasonably by assigning St. Elizabeth’s application an RA Level of two for this tie-breaker rather than an RA Level of one. St. Elizabeth and Marian Towers argue that other applications contained language that indicated a degree of uncertainty. Nevertheless, those other applications received an RA Level of one. For example, FHFC assigned an RA Level of one to Three Round and Haley Sofge even though their HUD letters stated that both developments would be “subject to a Subsidy Layering Review to be conducted by HUD.” Marian Towers argued that if FHFC does not accept HUD or RD letters containing conditional language about the number of units that will be subsidized, then FHFC should have assigned an RA Level of six to Three Round and Haley Sofge. If Three Round and Haley Sofge had been assigned an RA Level of six, then Marian Towers (with a lottery number of five) would have been recommended for funding. St. Elizabeth and Marian Towers cited another instance in which an application received an RA Level of one, even though its application contained a letter from the RD program stating that “USDA Rural Development will consent to the transfer if all regulatory requirements are met.” (emphasis added). However, St. Elizabeth and Marian Towers failed to demonstrate that the language cited above applied only to those particular applications rather than to all applications for tax credits. For example, if all applications are subject to a subsidy layering review and compliance with all regulatory requirements, then inclusion of such language in a HUD letter (in and of itself) should not prevent an applicant from being assigned an RA Level of one. St. Elizabeth and Marian Towers also cited a HUD Letter used in another recent RFA by an applicant that received an RA Level of one. The HUD letter in question contained an asterisk followed by the following statement: “It is HUD’s understanding that two separate applications are being submitted – one for each tower comprising St. Andrew Towers. If funded, HUD will consider a request from the owner to bifurcate the St. Andrew Towers HAP contract in order to facilitate the separate financing of each tower.” However, St. Elizabeth and Marian Towers failed to demonstrate why the language quoted directly above should have resulted in the applicant in question being awarded an RA Level less than one. There is no indication that the total number of units receiving rental assistance would change.

Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Florida Housing Finance Corporation enter a final order awarding funding to Three Round Tower A, LLC; Cathedral Towers, Ltd; Isles of Pahokee Phase II, LLC; SP Manor, LLC; and Pineda Village. DONE AND ENTERED this 18th day of October, 2016, in Tallahassee, Leon County, Florida. S G.W. CHISENHALL Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 18th day of October, 2016.

Florida Laws (6) 120.52120.569120.57120.68420.504420.509 Florida Administrative Code (1) 67-60.009
# 1
ELMWOOD TERRACE LIMITED PARTNERSHIP vs FLORIDA HOUSING FINANCE CORPORATION, 10-002799RX (2010)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida May 21, 2010 Number: 10-002799RX Latest Update: Feb. 03, 2012

The Issue The issue in this case is whether a portion of Florida Administrative Code Rule 67-48.0072 is an invalid exercise of delegated legislative authority.

Findings Of Fact The Petitioner is a limited partnership and developer of affordable housing in Florida. The Petitioner is seeking to construct a 116-unit affordable housing family apartment complex ("Elmwood Terrace") in Fort Myers, Lee County, Florida. The Petitioner has standing to initiate and participate in this proceeding. The Respondent is a public corporation organized under Chapter 420, Florida Statutes (2010), to administer state programs that provide financial support to developers seeking to construct affordable housing. Such support is provided through a variety of mechanisms, including the use of federal tax credits. The federal tax credit program was created in 1986 to promote the construction and operation of privately-developed affordable housing. The tax credits relevant to this proceeding provide a dollar-for-dollar credit against federal tax liabilities for a period of ten years. The Respondent is the designated Florida agency responsible for distribution of the federal tax credits. The tax credits are awarded pursuant to a "Qualified Allocation Plan" (QAP) that must be annually approved by the Governor and adopted as an administrative rule by the Respondent. As a matter of course, developers receiving the federal tax credits sell them through syndicators for discounted cash. The sale of the tax credits generates debt-free cash equity for developers. Developers seeking financial support to build affordable housing units submit applications to the Respondent during an annual competitive process known as the "Universal Cycle." Every three years, the Respondent commissions a study (the "Shimberg Report"), which measures, within each Florida county, the number of "cost-burden" renters earning 60 percent or less of an area's median income (AMI) who pay more than 40 percent of their income in rent. The AMI is determined by the federal government. The cost-burden households are further classified into four groups: families, the elderly, farm workers, and commercial fishermen. The Shimberg Report also assesses needs related to homeless people in the state. Developers seeking to obtain affordable housing financing are required to set aside a portion of the proposed units for income-limited residents. Access to affordable housing units is generally targeted towards persons receiving no more than 60 percent of the AMI. The Universal Cycle process allows the Respondent to target specific housing deficiencies in terms of geographic availability and population demographics and to preserve the stock of existing affordable housing. During the Universal Cycle process, the Respondent identifies areas where additional affordable housing is unnecessary, to discourage additional development in weak markets and to encourage development in those locations where there is a lack of access to affordable housing. The Respondent classifies areas where there is little need for additional affordable housing as "Location A" areas. Each application filed during the Universal Cycle is evaluated, scored, and competitively ranked against other applications filed during the same Universal Cycle. After the Respondent completes the competitive ranking of the applications submitted in the Universal Cycle, the applicants are provided with an opportunity to review and comment on the evaluation and scoring of the proposals. Applicants may also cure defects in their own proposals. After the close of the review and comment period, the Respondent publishes a revised competitive ranking of the proposals. Developers may challenge the second ranking through an administrative hearing. After the second ranking process is final, developers achieving an acceptable score receive preliminary funding commitments and proceed into a "credit underwriting" evaluation process. The credit underwriting process is governed by Florida Administrative Code Rule 67-48.0072. The Respondent selects an independent credit underwriter who reviews each proposal according to requirements set forth by administrative rule (the "Credit Underwriting Rule"). The cost of the credit underwriting review is paid by the developer. The credit underwriter considers all aspects of the proposed development, including financing sources, plans and specifications, cost analysis, zoning verification, site control, environmental reports, construction contracts, and engineering and architectural contracts. The responsibility for the market study is assigned by the credit underwriter to an independent market analyst. The credit underwriter prepares a report for each applicant invited into the process. The reports are submitted to the Respondent's nine-member, statutorily-created Board of Directors (Board). The Board approves or denies each application for financial support. The Petitioner applied for funds for the Elmwood Terrace project during the 2007 Universal Cycle. The Petitioner's application received a perfect score, maximum points, and was allocated tax credits in the amount of $1,498,680. The Petitioner thereafter entered the credit underwriting process. The credit underwriting analysis was performed by Seltzer Management Group (SMG). SMG contracted with a market analyst, Vogt, Williams & Bowen Research, Inc. (VWB), to prepare the required market study. The affordable units at Elmwood Terrace were initially intended for persons receiving incomes no more than 60 percent of the AMI. The VWB research indicated that the Elmwood Terrace project would adversely affect the existing affordable housing developments, if the Elmwood Terrace units were available to the 60 percent AMI population. The existing affordable housing developments, also serving the 60 percent AMI population, included two developments that had participated in the Respondent's "Guarantee Fund" program, addressed elsewhere herein. VWB determined that the impact of the Elmwood Terrace project on the existing developments could be ameliorated were some of the Elmwood Terrace units targeted during "lease-up" to persons at income levels of not more than 50 percent of the AMI. The lease-up period is the time required for a new development to reach anticipated occupancy levels. The issue was the subject of discussions between the Petitioner, VWB, and SMG. To resolve the anticipated negative impact on the existing affordable housing developments, the Petitioner agreed to target the 50 percent AMI population. In September 2008, the credit underwriter issued his report and recommended that the Petitioner receive the previously-allocated tax credits. On September 22, 2008, the Respondent's Board accepted the credit underwriting report and followed the recommendation. In the fall of 2008, after the Petitioner received the tax credits, the nation's economic environment deteriorated considerably. As a result, the syndicator with whom the Petitioner had been working to sell the tax credits advised that the sale would not occur. The Petitioner was unable to locate an alternate purchaser for the tax credits. The Petitioner considered altering the target population of the project in an attempt to attract a buyer for the tax credits, and there were discussions with the Respondent about the option, but there was no credible evidence presented that such an alteration would have resulted in the sale of the Petitioner's tax credits. Lacking a buyer for the tax credits, the Petitioner was unable to convert the credits to cash, and they were of little value in providing funds for the project. The Petitioner was not alone in its predicament, and many other developers who received tax credits in the 2007 and 2008 Universal Cycles found themselves unable to generate cash through the sale of their tax credits. In early 2009, Congress adopted the American Recovery and Reinvestment Act of 2009 (PL 111-5), referred to herein as ARRA, which incorporated a broad range of economic stimulus activities. Included within the ARRA was the "Tax Credit Exchange Program" that provided for the return by the appropriate state agency of a portion of the unused tax credits in exchange for a cash distribution of 85 percent of the tax credit value. The State of Florida received $578,701,964 through the Tax Credit Exchange Program. The ARRA also provided additional funds to state housing finance agencies through a "Tax Credit Assistance Program" intended to "resume funding of affordable housing projects across the nation while stimulating job creation in the hard-hat construction industry." On July 31, 2009, the Respondent issued a Request for Proposals (RFP 2009-04) to facilitate the distribution of the ARRA funds. The Respondent issued the RFP because the 2009 QAP specifically required the Respondent to allocate the relevant federal funds by means of a "competitive request for proposal or competitive application process as approved by the board." The 2009 QAP was adopted as part of the 2009 Universal Cycle rules. Projects selected for funding through the RFP would be evaluated through the routine credit underwriting process. Participation in the RFP process was limited to developers who held an "active award" of tax credits as of February 17, 2009, and who were unable to close on the sale of the credits. The RFP included restrictions against proposals for development within areas designated as "Location A." Although the location of the Elmwood Terrace project had not been within an area designated as "Location A" during the 2007 Universal Cycle process, the Respondent had subsequently designated the area as "Location A" by the time of the 2009 Universal Cycle. The RFP also established occupancy standards for projects funded under the RFP that exceeded the standards established in the Universal Cycle instructions and an evaluation process separate from the Universal Cycle requirements. Although the restrictions in the RFP would have automatically precluded the Petitioner from being awarded funds, the Petitioner submitted a response to the RFP and then filed a successful challenge to the RFP specifications (DOAH Case No. 09-4682BID). In a Recommended Order issued on November 12, 2009, the Administrative law Judge presiding over the RFP challenge determined that certain provisions of the RFP, including the automatic rejection of Location A projects, the increased occupancy standards, and the RFP evaluation criteria, were invalid. The Respondent adopted the Recommended Order by a Final Order issued on December 4, 2009, and invited the Petitioner into the credit underwriting process by a letter dated December 9, 2009. The credit underwriter assigned to analyze the Petitioner's project was SMG, the same credit underwriter that performed the original analysis of the Petitioner's project during the 2007 Universal Cycle. SMG retained Meridian Appraisal Group, Inc. (Meridian), to prepare the required market study. The Respondent was not consulted regarding the SMG decision to retain Meridian for the market analysis. The decision to retain Meridian for the market analysis was entirely that of SMG. The Respondent did not direct SMG or Meridian in any manner regarding the assessment or evaluation of any negative impact of the proposed project on existing affordable housing developments. Meridian completed the market study and forwarded it to SMG on January 26, 2010. The Meridian market analysis included a review of the relevant data as well as consideration of the actual economic conditions experienced in Lee County, Florida, including the extremely poor performance of the existing housing stock, as well as significant job losses and considerable unemployment. The Meridian market analysis determined that the Elmwood Terrace development would have a negative impact on two existing affordable housing apartment developments that were underwritten by the Respondent through a Guarantee Fund created at Section 420.5092, Florida Statutes, by the Florida Legislature in 1992. The existing Guarantee Fund properties referenced in the SMG recommendation are "Bernwood Trace" and "Westwood," both family-oriented apartment developments within five miles of the Elmwood Terrace location. The Guarantee Fund essentially obligates the Respondent to satisfy mortgage debt with the proceeds of Florida's documentary stamp taxes, if an affordable housing development is unable to generate sufficient revenue to service the debt. Because the Guarantee Fund program essentially serves to underwrite the repayment of mortgage debt for a "guaranteed" affordable housing development, the program increases the availability, and lowers the cost, of credit for developers. The Guarantee Fund program has participated in the financing of more than 100 projects, most of which closed between 1999 and 2002. Since 2005, the Respondent has not approved any additional Guarantee Fund participation in any affordable housing developments. The Respondent's total risk exposure through the Guarantee Fund is approximately 750 million dollars. Prior to October 2008, no claims were made against the Guarantee Fund. Since November 2008, there have been eight claims filed against the Guarantee Fund. Affordable housing financing includes restrictions that mandate the inclusion of a specific number of affordable housing units. Such restrictions are eliminated through foreclosure proceedings, and, accordingly, access to affordable housing units can be reduced if a development fails. Presuming that the eight claims pending against the Guarantee Fund eventually proceeded through foreclosure, as many as 2,300 residential units could be deducted from the stock of affordable housing. When there is a claim on the Guarantee Fund, the Respondent has to assume payment of the mortgage debt. The claims are paid from the Guarantee Fund capital, which is detrimental to the Respondent's risk-to-capital ratio. The risk-to-capital ratio is presently four to one. The maximum risk-to-capital ratio acceptable to rating agencies is five to one. The eight claims against the Guarantee Fund have ranged between ten and 18 million dollars each. The Respondent's bond rating has declined because of the eight claims. A continued decline in the Respondent's bond rating could result in documentary stamp tax receipts being used for payment of Guarantee Fund claims and directed away from the Respondent's programs that are intended to support the creation of affordable housing. In an effort to prevent additional claims against the Guarantee Fund, the Respondent has created the "Subordinate Mortgage Initiative" to provide assistance in the form of two- year loans to troubled Guarantee Fund properties. When preparing the 2010 market study, Meridian did not review the VWB market analysis performed as part of the 2007 application. Although the Petitioner has asserted that Meridian should have reviewed the 2007 VWB analysis, there is no evidence that Meridian's decision to conduct an independent market study without reference to the prior market review was inappropriate. On February 8, 2010, SMG issued a recommendation that the Petitioner's funding request be denied "because of the proposed development's potential financial impacts on developments in the area previously funded by Florida Housing and an anticipated negative impact to the two Guarantee Fund properties located within five miles of the proposed development." There is no evidence that the Meridian analysis was inadequate or improperly completed. There is no evidence that the SMG's reliance on the Meridian analysis was inappropriate. For purposes of this Order, the Meridian analysis and the SMG credit underwriting report have been accepted. Elmwood Terrace, a newer development with newer amenities, would compete for residents with the Bernwood Trace and Westwood developments. The financing for Bernwood Trace and Westwood was premised on projections that the affordable housing units would be leased to the 60 percent AMI population; however, the developments have been unable to maintain full occupancy levels, even though a number of units in the two properties are leased at reduced rates based on 50 percent AMI income levels. A rent reduction implemented by an existing development, whether based on economic conditions or resulting from competition, constitutes a negative impact on the development. There is no credible evidence that the occupancy rates are attributable to any difficulty in management of the two developments. It is reasonable to conclude that the leasing issues are related to economic conditions present in Lee County, Florida. In January 2010, VWB conducted an alternative market analysis. The VWB analysis was not provided to SMG or to the Respondent at any time during the credit underwriting process. Based on the 2010 VWB analysis, the Petitioner asserted that economic conditions in Lee County, Florida, have improved since the first credit underwriting report was completed in 2008 and that the improvement is expected to continue. There is no noteworthy evidence that economic conditions have improved or will significantly improve in the Lee County, Florida, market in the predictable future, and the VWB analysis is rejected. The Petitioner offered to mitigate any negative impact on the Guarantee Fund properties by committing affordable units to 50 percent AMI income levels. Given the existing economic and rental market conditions in Lee County, Florida, the evidence fails to establish that the offer would actually alleviate the negative impact on the affected Guarantee Fund developments. The 2010 VWB analysis states that there is substantial unmet demand for housing at 50 percent AMI and that there will be no impact on the Guarantee Fund units if the Elmwood Terrace units were set aside for such individuals. There is no credible evidence that there is a substantial and relevant unmet affordable housing demand in Lee County, Florida. The VWB analysis is rejected. Following the completion of each annual Universal Cycle process, the Respondent actively solicits feedback from developers and the public and then amends the Universal Cycle requirements to address the issues raised, as well as to reflect existing affordable housing needs and general concerns of the Board. The amendments are applicable for the following Universal Cycle. In 2009, the Respondent amended subsection (10) of the Credit Underwriting Rule as part of the annual revisions to the Universal Cycle process. The relevant amendment (referred to by the parties as the "Impact Rule") added this directive to the credit underwriter: The Credit Underwriter must review and determine whether there will be a negative impact to Guarantee Fund Developments within the primary market area or five miles of the proposed development, whichever is greater. The amendment was prompted by the Respondent's experience in the fall of 2008 when considering two separate applications for affordable housing financing. The potential negative impact of a proposed development on an existing Guarantee Fund property was central to the Board's consideration of one application, and the Board ultimately denied the application. In the second case, the Board granted the application, despite the potential negative impact on a competing development that was not underwritten by the Guarantee Fund. The intent of the language was to advise developers that the existence of Guarantee Fund properties within the competitive market area would be part of the credit underwriting evaluation and the Board's consideration. Notwithstanding the language added to the rule, the credit underwriter is charged with reviewing the need for additional affordable housing. Even in absence of the added language, consideration of any negative impact to competing developments based on inadequate need for additional affordable housing would be appropriate. In rendering the 2010 credit underwriting report on Elmwood Terrace, the credit underwriter complied with the directive. Prior to determining that the Petitioner's funding application should be denied, the Respondent's Board was clearly aware of the Petitioner's application, the credit underwriting report and market analysis, and the economic conditions in Lee County, Florida. There is no credible evidence of any need for additional affordable housing in Lee County, Florida. There is no credible evidence that the Lee County, Florida, market can sustain the addition of the units proposed by the Petitioner without adversely affecting the financial feasibility of the existing Guarantee Fund developments. The Board was aware that the Elmwood Terrace development could attract residents from the nearby Guarantee Fund properties and that local economic conditions threatened the financial viability of the properties. Given current economic conditions, approval of the application at issue in this proceeding would reasonably be expected to result in a negative impact to existing affordable housing developments. The protection of Guarantee Fund developments is necessary to safeguard the resources used to support the creation and availability of affordable housing in the state.

Florida Laws (8) 120.52120.56120.57120.68420.507420.5087420.5092420.5099 Florida Administrative Code (1) 67-48.0072
# 2
TOWN CENTER PHASE TWO, LLC vs FLORIDA HOUSING FINANCE CORPORATION, 14-001400BID (2014)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Mar. 25, 2014 Number: 14-001400BID Latest Update: Jun. 13, 2014

The Issue The issue for determination is whether Respondent's intended decision to award low-income housing tax credits in Miami-Dade County through Request for Applications 2013-003 to HTG Miami-Dade 5, LLC, and Allapattah Trace Apartments, Ltd., is contrary to governing statutes, the corporation’s rules or policies, or the solicitation specifications.

Findings Of Fact Overview FHFC is a public corporation created pursuant to section 420.504, Florida Statutes (2013).1/ Its purpose is to promote the public welfare by administering the governmental function of financing affordable housing in Florida. Pursuant to section 420.5099, FHFC is designated as the housing credit agency for Florida within the meaning of section 42(h)(7)(A) of the Internal Revenue Code and has the responsibility and authority to establish procedures for allocating and distributing low-income housing tax credits. The low-income housing tax credit program was enacted by Congress in 1986 to incentivize the private market to invest in affordable rental housing. Tax credits are competitively awarded to housing developers in Florida for qualified rental housing projects. Developers then sell these credits to investors to raise capital (or equity) for their projects, which reduces the debt that the developer would otherwise have to borrow. Because the debt is lower, a tax credit property can offer lower, more affordable rents. Provided the property maintains compliance with the program requirements, investors receive a dollar-for-dollar credit against their federal tax liability each year over a period of 10 years. The amount of the annual credit is based on the amount invested in the affordable housing. These are tax credits and not tax deductions. For example, a $1,000 deduction in a 15 percent tax bracket reduces taxable income by $1,000 and reduces tax liability by $150. However, a $1,000 tax credit reduces tax liability by $1,000. Developers that are awarded tax credits can use them directly. However, most sell them to raise equity capital for their projects.2/ Developers sell these credits for up-front cash. A developer typically sets up a limited partnership or limited liability company to own the apartment complex. The developer maintains a small interest but is responsible for building the project and managing (or arranging for the management) of the project. The investors have the largest ownership interest but are typically passive investors with regard to development and management.3/ Because the tax credits can be used by the investors that provide the equity for 10 years, they are very valuable. When sold to the investors, they provide equity which reduces the debt associated with the project. With lower debt, the affordable housing tax credit property can (and must) offer lower, more affordable rent. The demand for tax credits provided by the federal government far exceeds the supply. FHFC has adopted Florida Administrative Code Rule chapter 67-60, to govern the competitive solicitation process for several different programs, including the one for tax credits. Chapter 67-60 was newly enacted on August 20, 2013. It replaced prior procedures used by FHFC for the competitive process for allocating tax credits. FHFC has now adopted the bid protest provisions of section 120.57(3), Florida Statutes, as its process for allocating tax credits.4/ The Competitive Application Process Tax credits are made available annually. FHFC begins the competitive application process through the issuance of a Request for Applications.5/ In this case, that document is Request for Applications 2013-003. A copy of the RFA, including its Questions & Answers, is Joint Exhibit 1. The RFA was issued September 19, 2013 and responses were due November 12, 2013. According to the RFA, FHFC expected to award up to approximately $10,052,825 in tax credits for qualified affordable housing projects in Miami-Dade, Broward, and Palm Beach Counties. Knowing that there would be far more applications than available credits, FHFC established an order for funding in the three counties: The Applications will be considered for funding in the following funding order: first the highest scoring eligible Application located in Miami-Dade County that can meet the Funding Test, then the highest scoring eligible Application located in Broward County that can meet the Funding Test, then the highest scoring eligible Application located in Palm Beach County that can meet the Funding Test, then the highest scoring eligible unfunded Application located in Miami-Dade County that can meet the Funding Test and then the highest scoring eligible unfunded Application located in Broward County regardless of the Funding Test. If there is not enough funding available to fully fund this last Broward County Application, the Application will be entitled to receive a Binding Commitment for the unfunded balance. No further Applications will be considered for funding and any remaining funding will be distributed as approved by the Board. RFA at page 36. Applications were scored using a 27-point scale based on criteria in the RFA. RFA at page 37. This process was described in the RFA as follows: The highest scoring Applications will be determined by first sorting all eligible Applications from highest score to lowest score, with any scores that are tied separated first by the Application’s eligibility for the Development Category Funding Preference which is outlined in Section Four A.4.c.(1)(a) of the RFA (with Applications that qualify for the preference listed above Applications that do not qualify for the preference), then by the Application’s eligibility for the Per Unit Construction Funding Preference which is outlined in Section Four A.9.e. of the RFA, (with Applications that qualify for the preference listed above Applications to [sic] do not qualify for the preference), then by the Application’s Leveraging Classification (applying the multipliers outlined in Exhibit C below and having the Classification of A be the top priority), then by the Application’s eligibility for the Florida Job Creation Preference which is outlined in Exhibit C below (with Applications that qualify for the preference listed above Applications that do not qualify for the preference), and then by lottery number, resulting in the lowest lottery number receiving preference. RFA at page 36 (emphasis added). The way this process works in reality is that the developers know that they must first submit a project that meets all the eligibility criteria and does not have any significant omissions or errors.6/ Developers also strive to submit projects structured to receive all 27 points. The tiebreaker is then the luck-of-the-draw. At the time each application is filed, it is randomly assigned a lottery number7/ used to break the ties. The role of the lottery numbers is demonstrated by the following facts. One hundred and nineteen applications were filed in response to the RFA. All but six received the maximum score of 27 points. Seventy of the 119 were deemed eligible. Of those 70, 69 received the maximum score of 27 points. A copy of the RFA Sorting Order is Joint Exhibit 2.8/ As such, the lottery numbers are a big factor in deciding the winners and, concomitantly, the challengers are (1) the projects with high lottery numbers that were deemed ineligible; and (2) those with lottery numbers outside the funding range that are trying to displace those with lower lottery numbers. A copy of the final Review Committee Recommendations is Joint Exhibit 3. This document shows the developers selected, the county and the lottery number. The two Miami-Dade projects selected for funding are: HTG Miami-Dade 5, LLC d/b/a Wagner Creek - lottery number 3 Allapattah Trace Apartments, Ltd. - lottery number 6 The Petitioners/Intervenors in these consolidated proceedings are: Town Center Phase Two, LLC - lottery number 7 Pinnacle Rio, LLC - lottery number 9 APC Four Forty Four, Ltd. - deemed ineligible and with a lottery number of 10 The protests here center upon whether various applicants were correctly deemed eligible or ineligible. Applications are competitively reviewed, and so determinations as to one applicant affect other applicants’ positions. Each application, and the allegations against it, will be considered in turn. HTG’s Application APC argues that HTG should be found ineligible for allocation of tax credits because HTG failed to disclose its principals and those of its developer, as required by the RFA. The RFA at Section Four A.2.d. provides, in part, that each applicant will submit an application that identifies: d. Principals for the Applicant and for each Developer. All Applicants must provide a list, as Attachment 3 to Exhibit A, identifying the Principals for the Applicant and for each Developer, as follows: * * * (2) For a Limited Liability Company, provide a list identifying the following: (i) the Principals of the Applicant as of the Application Deadline and (ii) the Principals for each Developer as of the Application Deadline. This list must include warrant holders and/or option holders of the proposed Development. * * * This eligibility requirement may be met by providing a copy of the list of Principals that was reviewed and approved by the Corporation during the advance-review process. To assist the Applicant in compiling the listing, the Corporation has included additional information at Item 3 of Exhibit C. RFA at page 5. The RFA goes on to provide in Exhibit C 3.: 3. Principal Disclosures for Applicants and Each Developer The Corporation is providing the following charts and examples to assist the Applicant in providing the required list identifying the Principals for the Applicant and for each Developer. The term Principals is defined in Section 67-48.002, F.A.C. a. Charts: (1) For the Applicant: * * * (b) If the Applicant is a Limited Liability Company: Identify All Managers and Identify All Members and For each Manager that is a Limited Partnership: For each Manager that is a Limited Liability Company: For each Manager that is a Corporation: Identify each General Partner Identify each Manager Identify each Officer and and and Identify each Limited Partner Identify each Member Identify each Director and Identify each Shareholder and For each Member that is a Limited Partnership: For each Member that is a Limited Liability Company: For each Member that is a Corporation: Identify each General Partner Identify each Manager Identify each Officer and and and Identify each Limited Partner Identify each Member Identify each Director and Identify each Shareholder For any Manager and/or Member that is a natural person (i.e., Samuel S. Smith), no further disclosure is required. RFA at page 61. The RFA at Section Three F.3. Provides: 3. Requirements. Proposed Developments funded with Housing Credits will be subject to the requirements of the RFA, the Application requirements outlined in Rule Chapter 67-60, F.A.C., the credit underwriting and HC Program requirements outlined in Rule Chapter 67-48, F.A.C., and the Compliance requirements of Rule Chapter 67-53, F.A.C. RFA at page 3. The term “principal” is defined by rule 67-48.002(89)9/, as follows: (89) “Principal” means: (a) Any general partner of an Applicant or Developer, any limited partner of an Applicant or Developer, any manager or member of an Applicant or Developer, any officer, director or shareholder of an Applicant or Developer, * * * (c) Any officer, director, shareholder, manager, member, general partner or limited partner of any manager or member of an Applicant or Developer, and . . . . HTG received an “advance review” approval of its designation of principals on October 8, 2013. HTG submitted this stamped and approved list of principals with its application. Applicant HTG is a limited liability company, as is its developer, HTG Miami-Dade 5 Developer, LLC. In its submission of principals, HTG disclosed the names of the manager and member of the applicant and the manager and member of the developer, all of which were also LLCs. HTG also disclosed the names of the managers and members of these component LLCs. HTG did not disclose any officers of the applicant, the developer, or any of the component LLCs. Other documents submitted as part of the application indicate that Mr. Matthew Rieger is a Vice President of the applicant, HTG Miami-Dade 5, LLC, and that the component LLCs also have officers. APC contends that the rule’s definition of principal requires HTG to disclose not only the managers and members of the applicant and developer, and those of their component LLCs, but also the officers of any of these entities, if they also have officers. FHFC asserts that such disclosure is not required, arguing that the term “officer” as found in the rule’s definition of “principal” only applies to corporations. FHFC argues that there is no inconsistency between the rule and the charts of the RFA with respect to disclosure of principals. FHFC contends that the charts in the RFA, read in conjunction with the rule, indicate that officers must be disclosed only when the entity is a corporation, and that members and managers must be disclosed when the entity is a LLC. FHFC interprets rule 67-48.002(89) in a manner consistent with the charts. It does not interpret the rule to require that an LLC disclose its officers, even if it has them, but only that an LLC disclose its managers and members. Both Ms. O’Neill and Ms. Thorp testified to that effect. The examples provided in the RFA are also consistent with this interpretation. The rule certainly might have been drafted with more precision to expressly indicate that a principal is any officer, director, or shareholder if the entity is a corporation; any manager or member if the entity is an LLC; and any general partner or limited partner if the entity is a Limited Partnership. It cannot be said, however, that the Corporation’s interpretation of the RFA and its rule is impermissible. ATA’s Application Mr. Kenneth Reecy, Director of Multifamily Programs, testified that FHFC revised the “Universal Application Cycle” process that had been conducted in the past. Under the old universal cycle, most of the criteria were incorporated into the rule, and then there was a “cure” process that provided an opportunity to correct errors that didn’t necessarily have a bearing on whether a project was good enough to be funded. Under the newer process, several issues were moved out of the eligibility and scoring phase and into the credit underwriting phase.10/ Specifically relevant here, site plan issues and the availability of infrastructure, such as sewer service, were no longer examined as part of the eligibility and scoring phase set forth in the RFA. Mr. Reecy testified that these issues were complex and had been intentionally pushed to the “rigorous review” that takes place during the credit underwriting phase. In signing and submitting Exhibit A of the RFA, each applicant acknowledges and certifies that certain information will be provided to FHFC by various dates in the future. RFA at page 46. Section Four 10.b.(2)(b) provides in part that the following will be provided: Within 21 Calendar Days of the date of the invitation to enter credit underwriting: Certification of the status of site plan approval as of Application Deadline and certification that as of Application Deadline the site is appropriately zoned for the proposed Development, as outlined in Item 13 of Exhibit C of the RFA; Certification confirming the availability of the following for the entire Development site, including confirmation that these items were in place as of the Application Deadline: electricity, water, sewer service, and roads for the proposed Development, as outlined in Item 13 of Exhibit C of the RFA; Item 13 of Exhibit C goes on to provide: 13. Certification of Ability to Proceed: Within 21 Calendar Days of the date of the invitation to enter credit underwriting, the following information must be provided to the Corporation: a. Submission of the completed and executed 2013 Florida Housing Finance Corporation Local Government Verification of Status of Site Plan approval for Multifamily Developments form. * * * c. Evidence from the Local Government or service provider, as applicable, of the availability of infrastructure as of Application Deadline, as follows: * * * Sewer: Submission of the completed and executed 2013 Florida Housing Finance Corporation Verification of Availability of Infrastructure — Sewer Capacity, Package Treatment, or Septic Tank form or a letter from the service provider which is dated within 12 months of the Application Deadline, is Development specific, and specifically states that sewer service is available to the proposed Development as of the Application Deadline. The 2013 Florida Housing Finance Corporation Local Government Verification of Status of Site Plan Approval for Multifamily Developments Form (Site Plan Approval Form) and the 2013 Florida Housing Finance Corporation Verification of Availability of Infrastructure — Sewer Capacity, Package Treatment, or Septic Tank Form (Certification of Sewer Capacity Form) are incorporated by reference in the RFA. The Site Plan Approval Form requires (in the case of Miami-Dade County which does not have a preliminary or conceptual site plan approval process) that the local government confirm that the site plan was reviewed as of the application deadline. Pinnacle and APC assert that the site plan that ATA submitted to the City of Miami for review included a strip of land that is not legally owned by the current owner and will not be conveyed to ATA under the Purchase and Sale Agreement. As a result, they contend, the site plan review which was required on or before the application deadline did not occur. Pinnacle argues that ATA’s certification in its application was incorrect, that this was a mandatory requirement that was not met, and that it will be impossible for ATA to provide the Site Plan Approval Form in credit underwriting. TC similarly maintains that ATA could not “acknowledge and certify” as part of its application that it would later certify that it had “ability to proceed” because the RFA (at Section Four 10.b.(2)(b) quoted above) requires that “sewer service” be “in place” for ATA’s proposed development as of the application deadline. TC also asserts that the Certification of Sewer Capacity Form explicitly states (and that any service provider letter must, too) that no moratorium is applicable to a proposed development. ATA did not submit a Certification of Sewer Capacity Form. Miami-Dade County will not complete such forms. The “letter of availability” option was created to accommodate Miami-Dade County. The November 12, 2013, letter from Miami-Dade Water and Sewer regarding ATA’s development does not state that there is no applicable moratorium in effect. In fact, the letter affirmatively acknowledges that flow to the gravity system already connected to the property cannot be increased because there is a moratorium in effect as to the pumping station serving the abutting gravity sewer basin. The letter from the County states that, if the pumping station is still in Moratorium Status “at the time this project is ready for construction,” that a private pump station is acceptable. It is logical to conclude that this means sewer service would be available at that time and that sewer service was similarly available at the time of application deadline. The letter, therefore, implies, but does not specifically state, that “sewer service is available to the proposed development as of the application deadline.” The moratorium in effect at the application deadline was not a “general” moratorium. It applied only to the pump station serving the abutting gravity sewer basin, but it was applicable to the proposed development and precluded any increase in the flow to the gravity system connected to the property. A moratorium pertaining to sewer service applicable to ATA’s proposed development was in effect at the time that ATA’s application was submitted. Sewer capacity was otherwise available for the proposed development through use of a private pump station. ATA asserts, first, that ATA has not yet filed certification of ability to proceed or the required forms or letter, that it is not to do so until after it is invited to enter credit underwriting, that FHFC has consequently yet to make a determination as to ATA’s ability to proceed, and that therefore any issues as to site plan or sewer service are not yet ripe for consideration. As to the site plan, ATA further maintains that even if it had been required to provide evidence of ability to proceed as part of its application, the site plan submitted to the City of Miami did not represent that the alley was part of the ATA site. ATA, therefore, asserts that the site plan that was reviewed was the correct one, and that its application certification was correct. The plan of the site of ATA’s development project indicates that the site is bifurcated by a private alley, which is not dedicated as a street, avenue, or boulevard. The legal description of the development project, as submitted to the Department of Planning and Zoning of the City of Miami, included lots 2 through 7 and lots 19 and 20. It did not include the strip of land that lies between these lots (lots 2 through 7 lie to the West of the alley and lots 19 and 20 lie to the East of it.) As to sewer availability, ATA asserts that the 2011 Universal Cycle and the RFA are significantly different. ATA maintains that while the former provided that the existence of a moratorium pertaining to sewer service meant that infrastructure was unavailable, this language was removed from the RFA. ATA contends that a letter of availability need not “mimic” the Certification of Sewer Capacity Form and that the RFA allows a development to certify sewer availability by other means when a moratorium is in effect. Mr. Reecy testified that FHFC takes the certified application at face value, regardless of what other information the Corporation might have at hand. As to the site plan, he testified that even had site plan approval been a part of the scoring process, FHFC would not have found ATA’s application ineligible on that ground. He testified that the alley would not be a problem unless it was a “road” or something similar. He testified that it also could have been a problem if the measurement point to measure the distance to nearby amenities was not on the property, but he was not aware that that was the case in ATA’s application. As for sewer service, Mr. Reecy testified that a letter from the service provider does not have to say “exactly” what is on the form, but stated that it does have to give “the relevant information” to let FHFC know if sewer is “possible.” He testified that the only guidance as to what constituted sewer “availability” was contained in the criteria found on the Certification of Sewer Capacity Form. One of the four numbered requirements on the Certification of Sewer Capacity Form is that there are no moratoriums pertaining to sewer service that are applicable to the proposed development. Under the RFA, the Certification of Sewer Capacity Form could not be completed for a proposed development for which a moratorium pertaining to sewer service was in effect at the time the application was submitted. The form could not be certified by the service provider even if it was possible for such a development to obtain sewer service by other means. The text on the 2013 form is substantively identical to that on the form used during the 2011 Universal Cycle, that wording was specifically drafted to require that any moratorium on sewer infrastructure would be a disqualifying criterion, and the 2013 Certification of Sewer Capacity Form still has that effect. No challenge to the use of the form in the RFA was filed. Even though the language of the 2011 Universal Cycle which paralleled the text on the form does not appear in the RFA, that criterion remains as part of the RFA because of the incorporated Certification of Sewer Capacity Form. In any event, the site plan and sewer availability issues must await at least initial resolution by FHFC during the credit underwriting phase. The testimony of Mr. Reecy clearly indicated that FHFC interprets the RFA specifications and its rules to move consideration of site plan issues and infrastructure availability to the credit underwriting phase. It has not been shown that this is an impermissible interpretation. Town Center’s Application Pinnacle alleges that TC’s application fails to demonstrate site control, because the applicant, Town Center Phase Two, LLC, is not the buyer of the site it intends to develop. The RFA requires at Section Four A.7. that an applicant must provide a copy of a contract, deed, or lease to demonstrate site control: 7. Site Control: The Applicant must demonstrate site control by providing, as Attachment 7 to Exhibit A, the documentation required in Items a., b., and/or c., as indicated below. If the proposed Development consists of Scattered Sites, site control must be demonstrated for all of the Scattered Sites. a. Eligible Contract - For purposes of the RFA . . . the buyer MUST be the Applicant unless an assignment of the eligible contract which assigns all of the buyer's rights, title and interests in the eligible contract to the Applicant, is provided. If the owner of the subject property is not a party to the eligible contract, all documents evidencing intermediate contracts, agreements, assignments, options, or conveyances of any kind between or among the owner, the Applicant, or other parties, must be provided . . . . RFA at page 23. The Contract for Purchase and Sale of Real Property submitted as Attachment 7 to TC’s application is signed by Mr. Milo, who is identified as Vice President. The Buyer on the signature page is incorrectly listed as RUDG, LLC. No other assignment, intermediate contract, agreement, option, or conveyance was included with TC’s application to indicate that TC otherwise had site control of the property. The applicant entity, Town Center Phase Two, LLC, is correctly listed in the opening paragraph of the Contract for Purchase and Sale of Real Property as the “Buyer.” RUDG, LLC, is the 99.99 percent Member of Town Center Phase Two, LLC, and is also the sole Member and Manager of Town Center Phase Two Manager, LLC, which is the .01 percent Managing Member of Town Center Phase Two, LLC. Mr. Milo is a Vice President of RUDG, LLC, a Vice President of Town Center Phase Two Manager, LLC, and a Vice President of the applicant, Town Center Phase Two, LLC. Florida Administrative Code Rule 67-60.008, provides that the Corporation may waive minor irregularities in an otherwise valid application. The term “Minor Irregularity” is defined by rule 67- 60.002(6), as follows: (6) “Minor Irregularity” means a variation in a term or condition of an Application pursuant to this rule chapter that does not provide a competitive advantage or benefit not enjoyed by other Applicants, and does not adversely impact the interests of the Corporation or the public. Mr. Reecy testified that FHFC interpreted the rule to mean that if information requested by the RFA is reasonably available within the Application, even if it was not provided exactly in the place where it was requested, the failure to have it in the particular place it was requested is a minor irregularity. Although the information on the signature page of the Contract for Purchase and Sale of Real Property identifying the Buyer as RUDG, LLC, was a discrepancy in the application, the contract elsewhere identified Town Center Phase Two, LLC, as the Buyer, and Mr. Milo was, in fact, authorized to sign for the true Buyer. Ms. Amy Garmon’s deposition testimony indicated that because she was able to determine from other places in the application that the Buyer was the applicant, and that Mr. Milo was authorized to sign for the Buyer, she found this portion of TC’s application to be compliant, and she didn’t see that there was a “minor irregularity” that needed to be waived. However, it is determined that FHFC actually did finally determine that the error in identification constituted a minor irregularity that was waived, in accordance with Mr. Reecy’s testimony. Although it was Ms. Garmon who called attention to the irregularity, Mr. Reecy is in a position of higher authority within the FHFC and is better able to address the Corporation’s actions with respect to TC’s application. Pinnacle also asserts that TC’s finance documents fail, based upon the same signature issue. TC submitted equity proposals detailing its construction funding sources that were addressed to Mr. Milo and endorsed by him as “Vice President.” FHFC similarly concluded that Mr. Milo had authority to endorse the finance letters on behalf of TC. There is evidence to support FHFC’s findings that TC was the actual Buyer, that Mr. Milo had authority to sign the contract and the equity documents, and that the discrepancies in the documents were minor irregularities. Pinnacle’s Application The equity commitment letter from Wells Fargo Bank regarding Pinnacle’s development, as submitted to FHFC, contained only pages numbered one, two, and four of a four-page letter. It is clear that page three is actually missing and the letter was not simply incorrectly numbered, because of discontinuity in the text and in the numbering of portions of the letter. APC contends that Pinnacle’s application should have been deemed ineligible for award because of the missing page. Mr. Reecy testified that even though a page of Pinnacle’s equity commitment letter was missing, all of the RFA requirements were set forth in the remaining pages. He acknowledged that the missing page might have included unacceptable conditions for closing or information that was inconsistent with the other things in the application, but stated that FHFC determined that the missing page from Pinnacle’s equity letter was a minor irregularity. There is evidence to support FHFC’s finding that the missing page was a minor irregularity. APC’s Application The RFA provides at Section Four, A.3.c., at page 5: c. Experienced Developer(s) At least one Principal of the Developer entity, or if more than one Developer entity, at least one Principal of at least one of the Developer entities, must meet the General Developer Experience requirements in (1) and (2) below. (1) General Developer Experience: A Principal of each experienced Developer entity must have, since January 1, 1991, completed at least three (3) affordable rental housing developments, at least one (1) of which was a Housing Credit development completed since January 1, 2001. At least one (1) of the three (3) completed developments must consist of a total number of units no less than 50 percent of the total number of units in the proposed Development. For purposes of this provision, completed for each of the three (3) developments means (i) that the temporary or final certificate of occupancy has been issued for at least one (1) unit in one of the residential apartment buildings within the development, or (ii) that at least one (1) IRS Form 8609 has been issued for one of the residential apartment buildings within the development. As used in this section, an affordable rental housing development, including a Housing Credit development that contains multiple buildings, is a single development regardless of the number of buildings within the development for which an IRS Form 8609 has been issued. If the experience of a Principal for a Developer entity listed in this Application was acquired from a previous affordable housing Developer entity, the Principal must have also been a Principal of that previous Developer entity. (2) Prior General Development Experience Chart: The Applicant must provide, as Attachment 4 to Exhibit A, a prior experience chart for each Principal intending to meet the minimum general development experience reflecting the required information for the three (3) completed affordable rental housing developments, one (1) of which must be a Housing Credit development. Each prior experience chart must include the following information: Prior General Development Experience Chart Name of Principal with the Required Experience Name of Developer Entity (for the proposed Development) for which the above Party is a Principal: ___ ___________ ___ Name of Development Location (City & State) Affordable Housing Program that Provided Financing Total Number Of Units Year Completed RFA at pages 5, 6. Exhibit A to the RFA, at 3.c., further provides: General Developer Experience For each experienced Developer entity, the Applicant must provide, as Attachment 4, a prior experience chart for at least one (1) experienced Principal of that entity. The prior experience chart for the Principal must reflect the required information for the three (3) completed affordable rental housing developments, one (1) of which must be a Housing Credit development. RFA at page 41. Ms. O’Neill, a Senior Policy Analyst at FHFC and member of the Review Committee responsible for scoring the applications’ developer information section, testified at hearing. When FHFC first started scoring applications, Ms. O’Neill was not taking any action to confirm principal developer experience, but rather was taking the information provided by applicants at face value, as it had been submitted on the chart. A colleague of Ms. O’Neill’s, not serving on the Review Committee, called her attention to the fact that a development that was then going through credit underwriting (following an award during the 2011 funding cycle) had recently requested that FHFC approve a change to the developer entity. Ms. O’Neill testified that this request raised a question at FHFC as to whether Ms. Wong, listed by APC as the principal with the required experience, met the requirements. FHFC decided to confirm that Ms. Wong had the required experience for the developments listed in the RFA. Ms. O’Neill stated that she did not make any inquiry to Ms. Wong or to Atlantic Pacific Communities as to whether Ms. Wong was, in fact, a principal of St. Luke’s Development, LLC, developer of St. Luke’s Life Center, because “we’re not really supposed to do that.” Ms. O’Neill instead looked at portions of a credit underwriting report on the St. Luke’s Life Center project that were researched and shown to her by a colleague. Ms. O’Neill did not see Ms. Wong listed in that report as a principal. She did find information in FHFC files that Ms. Wong was a principal on the other two listed developments. Ms. Thorp testified that she researched several documents in FHFC’s possession and found no information indicating that Ms. Wong was a principal for the St. Luke’s development. She testified that Ms. Wong or another representative of APC was not contacted about the issue because that would have given them an unfair advantage over other applicants. Based upon the information in its files, FHFC determined that Ms. Wong did not meet the requirements for principal developer experience. FHFC then similarly reviewed the files of other applicants who had listed in-state developments as their experience, but was unable to review out-of-state experience, so out-of-state experience continued to be accepted at face value. Ms. Wong was not originally a principal in the St. Luke’s development. However, it was demonstrated at hearing through documentary evidence that Ms. Wong was later appointed an officer of St. Luke’s Development, LLC, effective March 2007. That change was submitted to the credit underwriter, and Ms. Wong was a principal for the developer entity before it completed credit underwriting. Both Ms. O’Neill and Ms. Thorp testified that if the documents provided at hearing by APC had been in FHFC’s possession at the time APC’s application was scored, FHFC would have found that Ms. Wong was a principal of the St. Luke’s development and that her experience met principal developer experience requirements. In light of the evidence presented at hearing, it is clear that FHFC’s conclusion was wrong. The prior experience chart submitted by APC as part of its application provided all of the information requested by the RFA, and all of that information was accurate. The information available to FHFC in the application correctly indicated that Ms. Wong was a principle for the developer of the St. Luke’s Life Center development. APC’s application met all requirements of the RFA with respect to prior developer experience. The Corporation’s preliminary determinations that Ms. Wong was not a principal in the St. Luke’s development, and that the APC application did not, therefore, meet principal experience requirements to the contrary, made in good faith based upon incomplete information contained in its files, was clearly erroneous. FHFC’s contention that APC should have submitted explanations or further documentation of Ms. Wong’s developer experience at the time it submitted its application is untenable. APC submitted all of information requested of it. FHFC asked for a chart to be completed, which APC did, completely and accurately. An applicant cannot be found ineligible for failing to do more than was required by the RFA. Credit Underwriting A comparison of the RFA and rules with the 2011 Universal Cycle process shows that the Corporation has moved many requirements formerly required as part of the eligibility and scoring phase into a second review in the credit underwriting phase, as noted earlier. Rule 67-48.0072 provides in part: Credit underwriting is a de novo review of all information supplied, received or discovered during or after any competitive solicitation scoring and funding preference process, prior to the closing on funding, including the issuance of IRS Forms 8609 for Housing Credits. The success of an Applicant in being selected for funding is not an indication that the Applicant will receive a positive recommendation from the Credit Underwriter or that the Development team’s experience, past performance or financial capacity is satisfactory. The rule goes on to provide that this de novo review in the credit underwriting phase includes not only economic feasibility, but other factors statutorily required for allocation of tax credits, such as evidence of need for affordable housing and ability to proceed. These factors might cause an application to fail and never receive funding, even though it was nominally “awarded” the credits earlier. In that event, the RFA provides: Funding that becomes available after the Board takes action on the Committee’s recommendation(s), due to an Applicant declining its invitation to enter credit underwriting or the Applicant’s inability to satisfy a requirement outlined in this RFA, and/or Rule Chapter 67-48, F.A.C., will be distributed to the highest scoring eligible unfunded Application located in the same county as the Development that returned the funding regardless of the Funding Test. If there is not enough funding available to fully fund this Application, it will be entitled to receive a Binding Commitment for the unfunded balance. If an applicant nominally “awarded” funding in the eligibility and scoring phase fails credit underwriting, the next applicant in the queue of eligible applicants may still be granted funding, and so, is substantially affected by FHFC’s decisions in the credit underwriting phase.

Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Florida Housing Finance Corporation enter a final order finding that APC Four Forty Four, Ltd., is eligible for funding, adjusting the Sorting Order accordingly, and otherwise dismissing the formal written protests of all Petitioners. DONE AND ENTERED this 4th day of June, 2014, in Tallahassee, Leon County, Florida. S F. SCOTT BOYD Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 4th day of June, 2014.

Florida Laws (6) 120.569120.57120.68420.504420.507420.5099
# 3
130 NE 40TH STREET, LLC, D/B/A MICHAEL'S GENUINE FOOD AND DRINK vs DEPARTMENT OF REVENUE, 16-006333 (2016)
Division of Administrative Hearings, Florida Filed:Lauderdale Lakes, Florida Oct. 28, 2016 Number: 16-006333 Latest Update: Jun. 16, 2017

The Issue The issues to be determined in this proceeding are 1) whether Respondent, the Department of Revenue (Respondent or the Department), demonstrated that it made an assessment against the taxpayer, as well as the factual and legal basis for the assessment; 2) whether Petitioner, 130 NE 40th Street, LLC, d/b/a Michael’s Genuine Food and Drink (Petitioner or Michael’s), is entitled to enterprise zone job credits (EZ credits) claimed on its sales and use tax returns for the audited period; and whether the penalty and interest assessed in the August 18, 2016, Notice of Decision is justified.

Findings Of Fact Petitioner is a Florida corporation with its home office and principal place of business in Miami, Florida. Respondent is an agency of the State of Florida, charged with administering the state’s sales tax laws under chapter 212, Florida Statutes (2012-2014). Michael’s is a limited liability company located at 130 NE 40th Street, Miami, Florida 33137. It operates a restaurant and bar at that address. Business Structure of Michael’s Michael’s opened in 2007 and is located in an enterprise zone in Miami. Michael’s enterprise zone identification number is 1301. Michael’s is owned by Michael Schwartz. In 2012, Mr. Schwartz opened a second restaurant known as Harry’s Pizzeria, which is also located in Miami. A third restaurant, the Cypress Room, was also opened during the audit period, although the timing of its opening is not clear from the record. Neither Harry’s Pizzeria nor the Cypress Room is the subject of this audit. All of the restaurants are separate legal entities. Mr. Schwartz is also the owner of a shared service company named Genuine Hospitality Group (GHG). The direct employees of GHG are the comptroller for the restaurants, the director of beverage, the director of operations, a marketing person, and the people overseeing the various restaurants. GHG does not have ownership in any of the restaurants, but provides services to each of them, including at different times, payroll, marketing, operations, and menu development. For example, during the years 2012 and 2013, GHG provided payroll functions for the various restaurants. According to Omar Azze, GHG’s comptroller, the idea was to create a “common paymaster” for the restaurants, because it would allow them to have a larger pool of employees for health insurance, in order to get a more favorable rate. When Michael’s decided to use this payroll method, Mr. Azze called the Department and canceled the reemployment tax registration of Michael’s because the taxes would be paid through GHG. Contrary to notations in the Department’s records, Michael’s never closed during the audit period: it still had the same employees and management team. The idea for using a common paymaster approach for the restaurants came from the restaurants’ accounting consultant. Paying employees through GHG was never intended to reduce the tax liability of Michael’s, or to transfer control of the employees to GHG, and taxes related to payroll were all paid through GHG for 2012 and 2013. Each restaurant maintained control over its own employees (general manager, two or three assistant managers, the head chef, bussers, waiters, cooks, support staff, and bartenders) and employee records, and employees did not “float” from restaurant to restaurant. GHG would pay the employees for Michael’s and the other restaurants, and all of the restaurants would reimburse GHG for the payroll payments for their respective employees. Mr. Azze’s testimony regarding this arrangement is consistent with the deductions on the restaurants’ respective federal tax returns for the payrolls in 2012 and 2013, and is credited. It is found that, during the calendar years 2012 and 2013, the employees remained under the direction and control of Michael’s and that payroll services alone were handled by GHG. In 2014, the third year of the audit period, the Petitioner decided to stop having GHG performing payroll functions, and to handle payroll in-house using a QuickBooks program, in order to reduce costs. In terms of the audit, this change in payroll method meant that for the first two years of the audit, all of the employees for Michael’s were paid through GHG, as were all of Michael’s’ reemployment taxes. The third year of the audit, employees and reemployment taxes were paid through Michael’s directly. Applications for EZ Credits for Michael’s Section 212.096 allows certain eligible businesses within identified “enterprise zones” to take a credit against sales and use taxes when there are employees hired who live within the identified enterprise zones and when there has been an increase in jobs over the 12 months prior to the date of the application. Section 212.096(1)(a) defines an “eligible business” as “any sole proprietorship, firm, partnership, corporation, bank, savings association, estate, trust, business trust, receiver, syndicate, or other group or combination, or successor business, located in an enterprise zone.” In order to obtain the credit, an eligible business must file an application, including a statement made under oath that includes, for each new employee, the employee’s name and place of residence; the enterprise zone number for the zone in which the new employee lives; the name and address of the eligible business; the starting salary or hourly wages paid to the new employee; and a demonstration to the Department that, on the date of the application, the total number of full-time jobs is greater than it was 12 months prior to the application. The application is initially filed with the governing body or enterprise zone development agency, which reviews the application and determines whether it contains all of the required information and meets the requirements of section 212.096. If it does, then the enterprise zone coordinator certifies the application and transmits it to the Department. In addition, the business also forwards a certified application to the Department. Once the Department receives a certified application for enterprise zone credits, it has ten days to notify the business that the credit has been approved. If the application is incomplete or insufficient to support the credit, the Department is required to deny the credit and notify the business, which is free to reapply. Section 212.096(2)(a) provides that “[u]pon an affirmative showing . . . that the requirements of this section have been met, the business shall be allowed a credit against the tax remitted under this chapter.” The credit “shall be allowed for up to 24 consecutive months, beginning with the first tax return due pursuant to s. 212.11 after approval by the department.” § 212.096(2)(b), Fla. Stat. Petitioner regularly submitted applications for EZ credits, and during the audit period, submitted applications on the following dates: February 1, 2012; August 1, 2012; February 4, 2013; April 2, 2013; July 19, 2013; August 15, 2013; August 30, 2013; January 6, 2014; January 30, 2014; March 3, 2014; March 27, 2014; and June 17, 2014. Each of these applications was made listing Michael’s as the taxpayer. Petitioner used a company named Economic Development Consultants (EDC) to help it calculate the credits Michael’s would be entitled to claim. Each month, Petitioner provided to EDC the names of employees terminated or resigned and those newly hired, along with the new hires’ addresses. Petitioner would also provide to EDC the number of full-time employees for each month. In determining residency for its employees, Petitioner relied on the addresses received from employees when they were hired. EDC would then provide a report saying which employees qualified for a credit, and do the necessary paperwork in order to obtain approvals for the credits. Each of Petitioner’s applications for EZ credits submitted during the audit period was approved, and Petitioner took the EZ credits associated with those applications with the understanding that they were properly approved. At the time the Department approved each of the applications for EZ credits, it had access to the information in and attached to the applications, including the identities of employees eligible for the credits. What the Department did not have when it reviewed the applications would be the actual wages paid to the eligible employees, because most of those wages would not have been paid at that point. Actions Taken By the Auditor On February 27, 2015, the Department issued a Notice of Intent to Audit Books and Records to Michael’s, indicating that it would be subject to audit for the period February 1, 2012, through January 31, 2015. Robert Ward was the auditor assigned to conduct the audit. Mr. Ward was relatively new to the Department, and had not previously conducted an audit that involved EZ credits. As part of his audit preparation, Mr. Ward pulled a copy of the Department’s standard audit plan, as well as the Department’s audit plan specifications for the industry in question (here, the restaurant industry). He noted that Michael’s had been audited previously and that the current audit resulted from a “lead,” but could not recall the basis or substance of the lead. He also noted that EZ credits had been an issue in the previous audit, which spanned the period from March 1, 2007, through June 30, 2009. Mr. Ward conducted a pre-audit interview with Omar Azze, Petitioner’s comptroller, on May 1, 2015.1/ While there was an agenda prepared for this pre-audit meeting, it does not appear to be in the record. At this pre-audit meeting, Mr. Ward was focused on the routine aspects of the audit as opposed to EZ credits. The issue of EZ credits was first raised in a meeting with Mr. Azze and Mr. Schwartz on May 27, 2015. At that time, Mr. Ward advised that EZ credits would be disallowed because the employees for whom credits were taken were on the payroll of GHG as opposed to Michael’s. Mr. Ward stated at hearing that this decision was made not based upon additional information, but based upon the sharing of employees by different entities. Mr. Ward acknowledged that Michael’s had received approval to take EZ credits, and that Michael’s provided all of the documentation requested of it. He had sought guidance from his trainer, Michelle Samuels, and a senior revenue consultant, Miguel Suarez. Mr. Ward was advised to verify the validity of the EZ credits claimed, with the focus on the growth of full-time employment. If a company subject to an audit had not received an approval letter for the credits, then the credits would be disallowed automatically. If there was an approval letter (as there was here), Mr. Ward understood that he was to look at the application itself and review the information provided with the application, including the schedules filed with the application, in order to validate the use of the EZ credits. Mr. Ward acknowledged that the person who reviewed the application for the Department when it was approved had all of this information. He was advised that the turn-around period for the initial applications was short, and that the initial reviewer is not required to validate the information, because the reviewer would trust the accuracy of the affirmation required of the taxpayer. The initial approval did not mean that the Department would not later go back and reexamine the information originally submitted. In addition to the documents submitted with the applications, Mr. Ward considered other Department records, such as reemployment tax records. He also verified addresses for named employees in the applications using the DAVID database of the Department of Highway Safety and Motor Vehicles. The DAVID database maintains information related to drivers’ licenses and car registrations. The information in the DAVID database is not available to the general public, and was not available to Petitioner. Mr. Ward also acknowledged that people can have a different mailing address from their residential address for a variety of reasons, and they were not always consistent, even in the DAVID database.2/ For example, one of the employees listed by Petitioner on an application dated August 1, 2012, was Aleksandar Gjurovski. The DAVID records indicate that on July 20, 2013, Mr. Gjurovski changed his mailing address. However, his residential address was not changed in the DAVID system until a date after the filing of the enterprise zone application. Mr. Ward relied on the change in the mailing address alone to determine that Mr. Gjurovski did not live within the enterprise zone at the time of the application. It is found that, at the time of the application, Mr. Gjurovski lived in the enterprise zone. After consultation with his supervisors, Mr. Ward disallowed all of the EZ credits for 2012 and 2013, as well as some of the credits for 2014. Respondent issued Michael’s a Notice of Intent to Make Audit Changes dated November 10, 2015, for audit number 200180508. The reasons given in the Explanation of Items included in the Work Papers are initially listed by employee, as opposed to by date. For all of the employees for which credits were claimed for 2012 and 2013, the primary reason stated by Mr. Ward is that the employees for which EZ credits were claimed were not employees of Michael’s, but instead were employees of another company. If the application for EZ credits was filed during 2012 or 2013, but the credits were claimed past December 2013, all of the credits related to that employee were disallowed. Other reasons listed for disallowing the tax credits were that there was no demonstrated job growth (for employees Kates, Gibson, Lopez, Jackson-Thompson, Daniels, Bradbury, Allante, Alicea, Wallace, and Herget); that the employee for which the credit was claimed did not live in the enterprise zone (for employees Coleman, Albert, Gjurovski, and Lopez); and discrepancies in terms of when employment ended compared to dates credits were claimed, or whether appropriate amount of credit was claimed for wages paid (for employees Kates, Poinsetti, Gomez, Daniels, Bradbury, Williams, Allante, and Herget). The first two of these reasons were based upon Mr. Ward’s verification of the information provided in the EZ credit applications. With respect to those employees for whom credits were disallowed because they had left the employ of Michael’s, Petitioner introduced a letter from the Department’s tax specialist, Suzanne Paul. The letter stated that a company could claim credits up to three months after employment ended in order to recapture the three months of employment required prior to submitting an application for that employee. Mr. Ward was not aware of this letter at the time he performed the audit, and had he known, it would have changed his note, at least as to Mr. Gjurovski, concerning that basis for disallowing the credit. Respondent assessed Michael’s sales and use tax for disallowed EZ credits, for untaxed purchases of fixed assets, and for untaxed consumable purchases. Only the assessment related to disallowed EZ credits is challenged in this proceeding. The Notice of Intent to Make Audit changes included a penalty of $62,609.01. In the letter accompanying the notice, Mr. Ward informed Petitioner that the penalty for items assessed in Exhibit B01 had been adjusted based on the reasonable cause guidelines outlined in Florida Administrative Code Rule 12- 13.007. It appears that there was no adjustment or compromise of penalties associated with the disallowance of EZ credits. Mr. Ward testified that penalties were assessed in this case because EZ credits were also an issue in the prior audit for Michael’s. The payroll arrangement at issue in this case was not at issue in the prior audit, however, as it did not begin until 2012. The financial dealings of Michael’s, including the payment of taxes to the Department, were also under a new comptroller, who was not involved in the first audit. Lastly, while the Department found fault with EZ credits in the first audit, it compromised the taxes assessed for the same amount as those associated with the EZ credits. Mr. Ward acknowledged that, under the circumstances related to this audit, the penalty seemed harsh. The Department issued a Notice of Proposed Assessment (NOPA) on December 15, 2015, in which it assessed taxes in the amount of $127,243.77, penalties of $62,609.01, and interest as of December 15, 2015, of $19,605.03. Michael’s filed an informal protest of the proposed assessment with the Department by means of a letter dated February 5, 2016. On August 18, 2016, the Department issued a Notice of Decision that sustained the proposed assessment against Michael’s in full. The Notice of Decision, which is, by its terms, the Department’s final position in this matter, only addresses the issue of whether Michael’s is an eligible employer for the purpose of receiving EZ credits.

Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Department of Revenue enter a final order assessing additional taxes based upon discrepancies in wages paid for eligible employees, and rejecting those parts of the assessment attributable to disallowance of enterprise zone credits based on information related to Petitioner’s initial applications. It is further recommended that no penalties be imposed on the reduced assessment. DONE AND ENTERED this 16th day of June, 2017, in Tallahassee, Leon County, Florida. S LISA SHEARER NELSON Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 16th day of June, 2017.

Florida Laws (18) 120.569120.57120.68120.80212.08212.096212.11212.17213.34215.26220.181243.77288.703290.004290.0065609.0172.01195.091
# 4
RST FRUITLAND HOUSING, L.P. vs FLORIDA HOUSING FINANCE CORPORATION, 10-000896 (2010)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Feb. 18, 2010 Number: 10-000896 Latest Update: Jun. 07, 2016

The Issue The issue is whether the Florida Housing Finance Corporation ("Florida Housing") properly rescinded the preliminary funding awarded to RST Fruitland Housing, L.P. ("RST"), pursuant to applicable rules, prior agency practice, and the existing case law.

Findings Of Fact RST is a limited partnership authorized to do business in Florida and is controlled by Roundstone Development, LLC ("Roundstone"). Roundstone is in the business of providing affordable rental housing. In addition to Florida, Roundstone operates in Texas, Arkansas, Mississippi, and South Carolina. Michael Hartman, the consultant for Roundstone, has been involved in the development of over 70 affordable housing developments, including many in Florida. Florida Housing is a public corporation created by Section 420.504, Florida Statutes, to administer the governmental function of financing or refinancing of affordable housing and related facilities in Florida. Florida Housing's statutory authority and mandates appear in Part V of Chapter 420, Florida Statutes. Florida Housing is governed by a Board of Directors consisting of nine individuals appointed by the Governor and confirmed by the Senate. On July 31, 2009, Florida Housing issued RFP 2009-04 (the "RFP") setting forth criteria and qualifications for developers to seek funding for affordable housing projects from funds that Florida received through the American Recovery and Reinvestment Act of 2009, PL 111-5 ("ARRA"). ARRA was enacted in 2009 by Congress as part of federal economic stimulus efforts. RST received notice of the RFP through e-mail notification on July 31, 2009. The RFP required applicants to submit proposals to Florida Housing no later than 2:00 p.m. on August 14, 2009. RST submitted an application and intended to seek financing for its affordable housing project by applying for funding from the sources that are proposed to be allocated through the RFP. Florida Housing's Programs Florida Housing administers numerous programs aimed at assisting developers to build affordable housing. These programs include: the Multi-Family Mortgage Revenue Bond Program ("MMRB") established under Section 420.509, Florida Statutes; the State Apartment Incentive Loan Program ("SAIL") created pursuant to Section 420.5087, Florida Statutes; and the Low Income Housing Tax Credit Program (the "Tax Credit program") established under the authority of Section 420.5093, Florida Statutes. These funding sources are allocated by Florida Housing to finance the construction or substantial rehabilitation of affordable housing. A portion of the units constructed based upon funding from these programs must be set aside for residents earning a certain percentage of area median income ("AMI"). For purposes of these proceedings, the primary program of interest is the Tax Credit program. Tax Credits The Tax Credit program was created in 1986 by the federal government. Tax Credits come in two varieties: competitively awarded nine percent tax credits, and non- competitively awarded four percent tax credits. For the nine percent credits, the federal government annually allocates to each state a specific amount of tax credits using a population- based formula. Tax Credits are a dollar for dollar offset to federal income tax liability over a 10-year period. A developer awarded Tax Credits will often sell the future stream of Tax Credits to a syndicator who in turn sells them to investors seeking to shelter income from federal income taxes. The developer receives cash equity with no debt associated with it. Thus, Tax Credits provide an attractive subsidy and, consequently, are a highly sought after funding source. Florida Housing is the designated agency in Florida to allocate Tax Credits to developers of affordable housing. Every year since 1986, Florida Housing has received an allocation of Tax Credits to be used to fund the construction of affordable housing. Universal Application Florida Housing has historically allocated funds from the MMRB, SAIL, and Tax Credit programs through a single annual application process. Since 2002, Florida Housing has administered the three programs through a combined competitive process known as the "Universal Cycle." The Universal Cycle operates much the same as an annual competitive bidding process in which applicants compete against other applicants to be selected for limited funding. Florida Housing has adopted rules which incorporate by reference the application forms and instructions for the Universal Cycle as well as general policies governing the allocation of funds from the various programs it administers. Typically, Florida Housing amends its Universal Cycle rules, forms, and instructions every year. The typical process used by Florida Housing to review and approve the Universal Cycle applications operates as set forth in Florida Administrative Code Rule 67-48.004, and is summarized as follows: Interested developers submit applications by a specified date. Florida Housing reviews all applications to determine if certain threshold requirements are met. A score is assigned to each application. Applications receive points towards a numerical score, based upon such features as programs for tenants, amenities of the development as a whole and of tenants' units, local government contributions to the specific development, and local government ordinances and planning efforts that support affordable housing in general. Florida Housing has built into its scoring and ranking process a series of "tiebreakers" to bring certainty to the selection process. The tiebreakers are written into the application instructions which, as indicated above, are incorporated by reference into Florida Housing's rules. After the initial review and scoring, a list of all applications, along with their scores, is published by Florida Housing on its website. The applicants are then given a specific period of time to alert Florida Housing of any errors they believe Florida Housing made in its initial review of the applications. An appeal procedure for challenging the scores assigned by Florida Housing is set forth in Florida Administrative Code Rule 67-48.005. Following the completion of the appeal proceedings, Florida Housing publishes final rankings which delineate the applications that are within the "funding range" for the various programs. In other words, the final rankings determine which applications are preliminarily selected for funding. The applicants ranked in the funding range are then invited into a "credit underwriting" process. Credit underwriting review of a development selected for funding is governed by Florida Administrative Code Rule 67-48.0072. In the credit underwriting process, third party financial consultants (selected by Respondent, but paid for by the individual applicants) determine whether the project proposed in the application is financially sound. The independent third party examines every aspect of the proposed development, including the financing sources, plans and specifications, cost analysis, zoning verification, site control, environmental reports, construction contracts, and engineering and architectural contracts. Subsection (10) of Florida Administrative Code Rule 67- 48.0072 expressly requires that an appraisal (as defined by the Uniform Standards of Professional Appraisal Practice), and a market study be ordered by the Credit Underwriter, at the applicant's expense. The Credit Underwriter is required to consider the market study, as well as the development's financial impact on other developments in the area previously funded by Florida Housing, and make a recommendation to approve or disapprove a funding allocation. RST's Application in the 2008 Universal Cycle RST timely submitted an application in the 2008 Universal Cycle seeking an award of Tax Credits and a supplemental loan to construct a 100-unit garden style apartment complex ("Plata Lago") in Fruitland Park, Lake County, Florida. RST complied with all of the requirements of the 2008 Universal Cycle Application and Instructions, and achieved a perfect score for its application. RST also achieved maximum tie-breaker points. As a result, RST was allocated by Florida Housing $1,334,333 in Tax Credits from the Universal Cycle allocation. Based on the final ranking of its application, RST was invited into the credit underwriting process on October 6, 2008. RST timely accepted the invitation and paid the necessary underwriting fees. Credit Underwriting Under the credit underwriting process, a professional credit underwriter is appointed by Florida Housing to review the proposed project that qualified for funding as a result of the Universal Cycle. The credit underwriter reviews and assesses numerous financial, demographic, and market factors concerning the proposed project. The credit underwriter selected by Florida Housing to review the RST application was Seltzer Management Group, Inc. ("Seltzer"). As required by the applicable 2008 Universal Cycle Application requirements and rule, the credit underwriting process required the preparation of a Market Study by an independent appraiser. Seltzer engaged Meridian Appraisal Group ("Meridian") to perform an independent appraisal and market study as required by the RFP. This initial Market Study was issued with the identified purpose defined as follows: Provide a site analysis for the subject property. Provide regional and neighborhood analyses for the subject property. Provide an Apartment Market Overview for the subject market area. Provide an evaluation of market demand within the competitive area for affordable rental apartment products. Identify and evaluate the relevant competitive supply of affordable apartments. Perform an income band analysis for the subject property based on achievable restricted rents. Perform a Capture Rate analysis for the subject property as a restricted property, and estimate an absorption rate. Establish rental estimates for the subject, both as a market rate project and as restricted by the Housing Credit program. Illustrate the difference between our estimate of the market rental rates and restricted rental rates. Estimate the impact of the subject project on the existing rental inventory. Economic Downturn By the fall of 2008, significant changes were taking place in the economic environment and the affordable housing market in particular. Many of the projects that had been awarded funding through Florida Housing allocation process were encountering difficulties and in many instances were unable to close. By the latter part of 2008, it became evident that the market for Tax Credits had precipitously dropped as a result of the changed economic environment. Shortly before RST was to complete the credit underwriting process, the syndicator who had originally expressed its intent to purchase the Tax Credits awarded to RST announced that it would not go forward with the syndication. This withdrawal was a direct result of the nationwide downturn in economic conditions. Many other projects that were awarded Tax Credits during the 2007 and 2008 (and later the 2009) Universal Cycles similarly experienced difficulty in finding syndicators to purchase the awarded Tax Credits and were also unable to proceed to closing. In early 2009, in recognition of the collapse of the housing market and the difficulty in marketing Tax Credits, the federal government, as part of its economic stimulus efforts, established mechanisms to assist in the development of affordable housing and offset some of the economic devastation to developers. ARRA The ARRA enacted by Congress and signed by the President on February 17, 2009, included specific provisions intended to address the collapse of the Tax Credit market. ARRA gives states the ability to return to the federal government previously awarded Tax Credits that had not been utilized. These Tax Credits are exchanged for a cash distribution of 85 cents for each tax credit dollar returned. The money that is awarded to the states for the return Tax Credits (the "Exchange Funds") is to be used by Florida Housing to fund developers who were unable to syndicate their Tax Credits due to the economic downturn. In other words, the Tax Credits that had not been utilized as a result of the declining economic conditions were allowed to be converted into cash from the federal government to be allocated to developers who were ready to proceed with their affordable housing projects but for the inability to syndicate their Tax Credits. ARRA also included a direct allocation of funds to state housing finance agencies under the Tax Credit Assistance Program ("TCAP"). These funds were allocated to the states to "resume funding of affordable rental housing projects across the nation while stimulating job creation in the hard-hat construction industry." TCAP is a separate program included as part of ARRA to provide gap financing for affordable housing projects that have been affected by the economic downturn. The RFP In response to ARRA, on July 31, 2009, Florida Housing issued RFP 2009-04 (the "RFP"), setting forth criteria and qualifications for developers to seek funding for affordable housing projects from money that had been allotted by the federal government as part of economic stimulus efforts. RST received notice of the RFP through e-mail notification on July 31, 2009. The RFP required applicants to submit proposals to Florida Housing by no later than 2:00 p.m. on August 14, 2009. The RFP solicits proposals from applicants with an "Active Award" of Tax Credits who were unable to close and are seeking alternate funding to construct affordable housing utilizing Exchange Funds from the Tax Credit Exchange Program authorized under Section 1602 of ARRA. The RFP provides a general description of the type of projects that will be considered eligible for this alternate funding. The RFP also sets forth eligibility criteria that are a precondition to award of an allocation of Exchange Funds, and also specifies that projects allocated Exchange Funds and also specifies that projects allocated Exchange Funds will be required to meet new credit underwriting standards. Occupancy Standards Section 5B.1b. of the RFP states that a tentative funding award under the RFP will be rescinded "if the submarket of the Proposed Development does not have an average occupancy rate of 92% or greater for the same Demographic population, as determined by a market study ordered by the Credit Underwriter, and analyzed by the Credit Underwriter and Florida Housing staff, as well as approved by the Board." The RFP does not define "submarket." Likewise, there was no definition of "submarket" in the rules which governed the 2008 or 2009 Universal Cycle. The word "submarket" is included in the 2009 Universal Cycle Rule, but it is not defined. RST timely submitted a response to the RFP on August 14, 2009, which sought additional funding for the Plata Lago project. On August 20, 2009, Florida Housing issued a Notice of Awards for RFP #2009-04. Based on the Notice, RST was one of the responders awarded funds subject to successfully completing the underwriting criteria listed in the RFP. Accordingly, RST was once again invited into credit underwriting. By accepting the invitation, RST was required by the credit underwriter to update its Market Study ("2009 Study"). This Second Market Study, which was completed approximately eight months after the 2008 study, was also prepared by Meridian on July 14, 2009. Likewise, Seltzer was the assigned underwriter. On September 9, 2009, Seltzer issued a letter to Florida Housing concerning the Plata Lago project. In essence, Seltzer in the letter considered the 2009 Market Study and concluded that "the submarket average occupancy rate for the subject does not meet the minimum requirement of 92%." On October 23, 2009, Florida Housing's Board of Directors considered Seltzer's letter and a staff recommendation and voted to rescind funding to RST because of the alleged failure to satisfy the 92 percent occupancy requirement. This action effectively stopped the underwriting process. While RST timely filed its petition with the Division, it also intervened in a challenge to the provisions of the RFP. The challenge specifically involved a review of the 92 percent occupancy standard. In that matter, Elmwood Terrace Ltd. P'ship v. Fla. Hous. Fin. Corp., Case No. 09-4682BID, 2009 Fla. Div. Adm. Hear. Lexis 816 (Final Order entered December 7, 2009), the administrative law judge entered a Recommended Order on November 12, 2009, holding that the provision of the RFP which required a 92 percent occupancy rate is contrary to Florida Housing's governing statutes and rules. The administrative law judge concluded that Florida Housing is limited to using the 90 percent occupancy test established at Florida Administrative Code Rule 67-48.0072(10). Florida Housing issued its Final Order in the Elmwood case on December 7, 2009, adopting the administrative law judge's Recommended Order. Based upon the Final Order in Elmwood, Florida Housing has reevaluated the RST Market Study under the provisions of the 2009 Universal Cycle Rule which established a 90 percent occupancy test. Florida Housing has now concluded that RST's Market Study indicates an 87 percent occupancy rate. Accordingly, Florida Housing has not changed its previous position and refuses to allow Petitioner to move forward in the underwriting process. Unstipulated Findings of Fact Two market studies were commissioned by Florida Housing and Seltzer regarding the proposed Plata Lago development, the first in November 2008 and the second in July 2009. Both the First and Second Market Studies were performed by Meridian Appraisal Group and Robert Von, a state- certified general appraiser. While purported to be a new stand-alone study, the Second Market Study is identical in many respects to the First Market Study. However, the First Market Study predated the requirement of the occupancy test in Florida Administrative Code Rule 67-48.0072(10), while the Second Market Study included the 90 percent occupancy test analysis. In each of the two studies, a circle is drawn extending out 10 miles from the proposed location of the Plata Lago development. That circle represents the primary market area ("PMA") which includes Fruitland Park, Lady Lake, and Leesburg. The PMA is where generally two-thirds to three-quarters of the demand for a facility originates. In the Second Market Study, when the occupancy rate of the three existing senior apartment developments within the PMA is considered, the threshold requirement of 90 percent is met. If the PMA alone were considered, Florida Housing would not have rescinded the Tax Credits, and Petitioner would be entitled to move forward with its project. The Second Market Study, performed in 2009, added an additional factor to the analysis. The concept of a Competitive Market Area ("CMA") was introduced. A CMA was not designated in the 2008 Market Study. CMA is neither defined in the 2009 Universal Cycle Rule or RFP 2009-04. The delineation of a CMA was not a requirement of the RFP, nor was it otherwise requested by Florida Housing. CMA is not a term defined in either the development or market analysis industries. The term appears to have been created or borrowed by Florida Housing's designated market analyst based upon his experience as a certified appraiser. Unlike the PMA, the CMA was not mapped or otherwise designated in the Second Market Study. However, both the First and Second Market Studies included information regarding a development known as Lake Point Senior Village ("Lake Point"). Both Plata Lago and Lake Point are affordable housing developments targeted at the elderly demographic category. Lake Point is not in the PMA of the proposed Plata Lago development as PMA is defined in the Second Market Study. The PMA as defined in the Second Market Study is a predetermined geographic area used for purposes of demographic analysis, but not for competitive analysis. A set unmovable circle on a map could lead to skewed or absurd results if the nature and character of the developments within and without the circle are not considered by the appraiser. Lake Point is an elderly affordable housing development located 13 miles from the proposed location of Plata Lago. It is located in Tavares which is outside the 10-mile radius from the proposed development and is past two lakes that separate Tavares from those developments contained within the PMA. The analysis by Florida Housing's expert was that an individual moving into the Lake County area would look for elderly housing developments in close proximity to his or her work, shopping, health care, and other amenities they deemed important. The tenant does not necessarily look to see if other elderly housing developments are nearby. This is especially true when only four elderly developments are located in the county. Plata Lago and Lake Point are similar to each other, both serve the elderly demographic category, and each would compete with the other for residents if the Plata Lago development were built. It was appropriate for the Second Market Study to include Lake Point in its analysis of occupancy data for the purpose of determining whether Plata Lago passed the test set forth in the rule requiring a 90 percent occupancy rate in its applicable submarket. To address the requirement of the rule regarding occupancy rates for the submarket of the Plata Lago development, it was necessary for Florida Housing's consultant to determine what developments would compete with the proposed project. To do a competitive analysis, it is necessary for the consultant to move beyond the fixed PMA to a study of the market as real people in the real world look at it. In the Second Market Study, the term CMA is used to describe the "submarket" as it applies to the occupancy test of the rule, as well as to distinguish this area from the PMA and from other incidental uses of the term "submarket." Florida Housing's consultant investigated all the comparable properties and interviewed the manager of Lake Point about where the competition lay. The manager mentioned a property around the corner from the proposed Plata Lago (Silver Pointe) as a competitor which led the consultant to expand the CMA to include Lake Point. The manager at Silver Pointe named Lake Point as part of its competition. Florida Housing's appraiser considers the submarket to be where a project's competitive property is located. In this case, the submarket or competitive market is larger than the PMA. Lake Point suffered a drop in its occupancy between the First and Second Market Studies. This was most likely attributable to the nature of elderly developments. Elderly residents tend to expire or suffer health issues that cause them to move to facilities providing health care or assisted living services. On October 23, 2009, Florida Housing's Board of Directors met and considered the market study letter prepared by Seltzer along with its finding that the Plata Lago development did not pass the required occupancy test of 90 percent set forth in the rule. Based upon the occupancy rate being only 87 percent, as well as the results of the market study and credit underwriter recommendations, the Board voted to rescind Florida Housing's commitment to fund the Plata Lago development.

Recommendation it is Based upon the Findings of Fact and Conclusions of Law, RECOMMENDED that the Florida Housing Finance Corporation enter a final order rescinding funding to the Plata Lago development for failing to pass the occupancy standard set forth in Florida Administrative Code Chapter 67-48. DONE AND ENTERED this 9th day of June, 2010, in Tallahassee, Leon County, Florida. S ROBERT S. COHEN Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 9th day of June, 2010. COPIES FURNISHED: Wellington H. Meffert, II, General Counsel Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1329 Michael P. Donaldson, Esquire Carlton Fields, P.A. 215 South Monroe Street, Suite 500 Post Office Drawer 190 Tallahassee, Florida 32302-0190 Hugh R. Brown, Esquire Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1329 Della Harrell, Corporation Clerk Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1329

Florida Laws (8) 120.52120.569120.57120.68420.504420.5087420.509420.5093 Florida Administrative Code (3) 67-48.00467-48.00567-48.0072
# 5
PINNACLE RIO, LLC vs FLORIDA HOUSING FINANCE CORPORATION, 14-001398BID (2014)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Mar. 25, 2014 Number: 14-001398BID Latest Update: Jun. 13, 2014

The Issue The issue for determination is whether Respondent's intended decision to award low-income housing tax credits in Miami-Dade County through Request for Applications 2013-003 to HTG Miami-Dade 5, LLC, and Allapattah Trace Apartments, Ltd., is contrary to governing statutes, the corporation’s rules or policies, or the solicitation specifications.

Findings Of Fact Overview FHFC is a public corporation created pursuant to section 420.504, Florida Statutes (2013).1/ Its purpose is to promote the public welfare by administering the governmental function of financing affordable housing in Florida. Pursuant to section 420.5099, FHFC is designated as the housing credit agency for Florida within the meaning of section 42(h)(7)(A) of the Internal Revenue Code and has the responsibility and authority to establish procedures for allocating and distributing low-income housing tax credits. The low-income housing tax credit program was enacted by Congress in 1986 to incentivize the private market to invest in affordable rental housing. Tax credits are competitively awarded to housing developers in Florida for qualified rental housing projects. Developers then sell these credits to investors to raise capital (or equity) for their projects, which reduces the debt that the developer would otherwise have to borrow. Because the debt is lower, a tax credit property can offer lower, more affordable rents. Provided the property maintains compliance with the program requirements, investors receive a dollar-for-dollar credit against their federal tax liability each year over a period of 10 years. The amount of the annual credit is based on the amount invested in the affordable housing. These are tax credits and not tax deductions. For example, a $1,000 deduction in a 15 percent tax bracket reduces taxable income by $1,000 and reduces tax liability by $150. However, a $1,000 tax credit reduces tax liability by $1,000. Developers that are awarded tax credits can use them directly. However, most sell them to raise equity capital for their projects.2/ Developers sell these credits for up-front cash. A developer typically sets up a limited partnership or limited liability company to own the apartment complex. The developer maintains a small interest but is responsible for building the project and managing (or arranging for the management) of the project. The investors have the largest ownership interest but are typically passive investors with regard to development and management.3/ Because the tax credits can be used by the investors that provide the equity for 10 years, they are very valuable. When sold to the investors, they provide equity which reduces the debt associated with the project. With lower debt, the affordable housing tax credit property can (and must) offer lower, more affordable rent. The demand for tax credits provided by the federal government far exceeds the supply. FHFC has adopted Florida Administrative Code Rule chapter 67-60, to govern the competitive solicitation process for several different programs, including the one for tax credits. Chapter 67-60 was newly enacted on August 20, 2013. It replaced prior procedures used by FHFC for the competitive process for allocating tax credits. FHFC has now adopted the bid protest provisions of section 120.57(3), Florida Statutes, as its process for allocating tax credits.4/ The Competitive Application Process Tax credits are made available annually. FHFC begins the competitive application process through the issuance of a Request for Applications.5/ In this case, that document is Request for Applications 2013-003. A copy of the RFA, including its Questions & Answers, is Joint Exhibit 1. The RFA was issued September 19, 2013 and responses were due November 12, 2013. According to the RFA, FHFC expected to award up to approximately $10,052,825 in tax credits for qualified affordable housing projects in Miami-Dade, Broward, and Palm Beach Counties. Knowing that there would be far more applications than available credits, FHFC established an order for funding in the three counties: The Applications will be considered for funding in the following funding order: first the highest scoring eligible Application located in Miami-Dade County that can meet the Funding Test, then the highest scoring eligible Application located in Broward County that can meet the Funding Test, then the highest scoring eligible Application located in Palm Beach County that can meet the Funding Test, then the highest scoring eligible unfunded Application located in Miami-Dade County that can meet the Funding Test and then the highest scoring eligible unfunded Application located in Broward County regardless of the Funding Test. If there is not enough funding available to fully fund this last Broward County Application, the Application will be entitled to receive a Binding Commitment for the unfunded balance. No further Applications will be considered for funding and any remaining funding will be distributed as approved by the Board. RFA at page 36. Applications were scored using a 27-point scale based on criteria in the RFA. RFA at page 37. This process was described in the RFA as follows: The highest scoring Applications will be determined by first sorting all eligible Applications from highest score to lowest score, with any scores that are tied separated first by the Application’s eligibility for the Development Category Funding Preference which is outlined in Section Four A.4.c.(1)(a) of the RFA (with Applications that qualify for the preference listed above Applications that do not qualify for the preference), then by the Application’s eligibility for the Per Unit Construction Funding Preference which is outlined in Section Four A.9.e. of the RFA, (with Applications that qualify for the preference listed above Applications to [sic] do not qualify for the preference), then by the Application’s Leveraging Classification (applying the multipliers outlined in Exhibit C below and having the Classification of A be the top priority), then by the Application’s eligibility for the Florida Job Creation Preference which is outlined in Exhibit C below (with Applications that qualify for the preference listed above Applications that do not qualify for the preference), and then by lottery number, resulting in the lowest lottery number receiving preference. RFA at page 36 (emphasis added). The way this process works in reality is that the developers know that they must first submit a project that meets all the eligibility criteria and does not have any significant omissions or errors.6/ Developers also strive to submit projects structured to receive all 27 points. The tiebreaker is then the luck-of-the-draw. At the time each application is filed, it is randomly assigned a lottery number7/ used to break the ties. The role of the lottery numbers is demonstrated by the following facts. One hundred and nineteen applications were filed in response to the RFA. All but six received the maximum score of 27 points. Seventy of the 119 were deemed eligible. Of those 70, 69 received the maximum score of 27 points. A copy of the RFA Sorting Order is Joint Exhibit 2.8/ As such, the lottery numbers are a big factor in deciding the winners and, concomitantly, the challengers are (1) the projects with high lottery numbers that were deemed ineligible; and (2) those with lottery numbers outside the funding range that are trying to displace those with lower lottery numbers. A copy of the final Review Committee Recommendations is Joint Exhibit 3. This document shows the developers selected, the county and the lottery number. The two Miami-Dade projects selected for funding are: HTG Miami-Dade 5, LLC d/b/a Wagner Creek - lottery number 3 Allapattah Trace Apartments, Ltd. - lottery number 6 The Petitioners/Intervenors in these consolidated proceedings are: Town Center Phase Two, LLC - lottery number 7 Pinnacle Rio, LLC - lottery number 9 APC Four Forty Four, Ltd. - deemed ineligible and with a lottery number of 10 The protests here center upon whether various applicants were correctly deemed eligible or ineligible. Applications are competitively reviewed, and so determinations as to one applicant affect other applicants’ positions. Each application, and the allegations against it, will be considered in turn. HTG’s Application APC argues that HTG should be found ineligible for allocation of tax credits because HTG failed to disclose its principals and those of its developer, as required by the RFA. The RFA at Section Four A.2.d. provides, in part, that each applicant will submit an application that identifies: d. Principals for the Applicant and for each Developer. All Applicants must provide a list, as Attachment 3 to Exhibit A, identifying the Principals for the Applicant and for each Developer, as follows: * * * (2) For a Limited Liability Company, provide a list identifying the following: (i) the Principals of the Applicant as of the Application Deadline and (ii) the Principals for each Developer as of the Application Deadline. This list must include warrant holders and/or option holders of the proposed Development. * * * This eligibility requirement may be met by providing a copy of the list of Principals that was reviewed and approved by the Corporation during the advance-review process. To assist the Applicant in compiling the listing, the Corporation has included additional information at Item 3 of Exhibit C. RFA at page 5. The RFA goes on to provide in Exhibit C 3.: 3. Principal Disclosures for Applicants and Each Developer The Corporation is providing the following charts and examples to assist the Applicant in providing the required list identifying the Principals for the Applicant and for each Developer. The term Principals is defined in Section 67-48.002, F.A.C. a. Charts: (1) For the Applicant: * * * (b) If the Applicant is a Limited Liability Company: Identify All Managers and Identify All Members and For each Manager that is a Limited Partnership: For each Manager that is a Limited Liability Company: For each Manager that is a Corporation: Identify each General Partner Identify each Manager Identify each Officer and and and Identify each Limited Partner Identify each Member Identify each Director and Identify each Shareholder and For each Member that is a Limited Partnership: For each Member that is a Limited Liability Company: For each Member that is a Corporation: Identify each General Partner Identify each Manager Identify each Officer and and and Identify each Limited Partner Identify each Member Identify each Director and Identify each Shareholder For any Manager and/or Member that is a natural person (i.e., Samuel S. Smith), no further disclosure is required. RFA at page 61. The RFA at Section Three F.3. Provides: 3. Requirements. Proposed Developments funded with Housing Credits will be subject to the requirements of the RFA, the Application requirements outlined in Rule Chapter 67-60, F.A.C., the credit underwriting and HC Program requirements outlined in Rule Chapter 67-48, F.A.C., and the Compliance requirements of Rule Chapter 67-53, F.A.C. RFA at page 3. The term “principal” is defined by rule 67-48.002(89)9/, as follows: (89) “Principal” means: (a) Any general partner of an Applicant or Developer, any limited partner of an Applicant or Developer, any manager or member of an Applicant or Developer, any officer, director or shareholder of an Applicant or Developer, * * * (c) Any officer, director, shareholder, manager, member, general partner or limited partner of any manager or member of an Applicant or Developer, and . . . . HTG received an “advance review” approval of its designation of principals on October 8, 2013. HTG submitted this stamped and approved list of principals with its application. Applicant HTG is a limited liability company, as is its developer, HTG Miami-Dade 5 Developer, LLC. In its submission of principals, HTG disclosed the names of the manager and member of the applicant and the manager and member of the developer, all of which were also LLCs. HTG also disclosed the names of the managers and members of these component LLCs. HTG did not disclose any officers of the applicant, the developer, or any of the component LLCs. Other documents submitted as part of the application indicate that Mr. Matthew Rieger is a Vice President of the applicant, HTG Miami-Dade 5, LLC, and that the component LLCs also have officers. APC contends that the rule’s definition of principal requires HTG to disclose not only the managers and members of the applicant and developer, and those of their component LLCs, but also the officers of any of these entities, if they also have officers. FHFC asserts that such disclosure is not required, arguing that the term “officer” as found in the rule’s definition of “principal” only applies to corporations. FHFC argues that there is no inconsistency between the rule and the charts of the RFA with respect to disclosure of principals. FHFC contends that the charts in the RFA, read in conjunction with the rule, indicate that officers must be disclosed only when the entity is a corporation, and that members and managers must be disclosed when the entity is a LLC. FHFC interprets rule 67-48.002(89) in a manner consistent with the charts. It does not interpret the rule to require that an LLC disclose its officers, even if it has them, but only that an LLC disclose its managers and members. Both Ms. O’Neill and Ms. Thorp testified to that effect. The examples provided in the RFA are also consistent with this interpretation. The rule certainly might have been drafted with more precision to expressly indicate that a principal is any officer, director, or shareholder if the entity is a corporation; any manager or member if the entity is an LLC; and any general partner or limited partner if the entity is a Limited Partnership. It cannot be said, however, that the Corporation’s interpretation of the RFA and its rule is impermissible. ATA’s Application Mr. Kenneth Reecy, Director of Multifamily Programs, testified that FHFC revised the “Universal Application Cycle” process that had been conducted in the past. Under the old universal cycle, most of the criteria were incorporated into the rule, and then there was a “cure” process that provided an opportunity to correct errors that didn’t necessarily have a bearing on whether a project was good enough to be funded. Under the newer process, several issues were moved out of the eligibility and scoring phase and into the credit underwriting phase.10/ Specifically relevant here, site plan issues and the availability of infrastructure, such as sewer service, were no longer examined as part of the eligibility and scoring phase set forth in the RFA. Mr. Reecy testified that these issues were complex and had been intentionally pushed to the “rigorous review” that takes place during the credit underwriting phase. In signing and submitting Exhibit A of the RFA, each applicant acknowledges and certifies that certain information will be provided to FHFC by various dates in the future. RFA at page 46. Section Four 10.b.(2)(b) provides in part that the following will be provided: Within 21 Calendar Days of the date of the invitation to enter credit underwriting: Certification of the status of site plan approval as of Application Deadline and certification that as of Application Deadline the site is appropriately zoned for the proposed Development, as outlined in Item 13 of Exhibit C of the RFA; Certification confirming the availability of the following for the entire Development site, including confirmation that these items were in place as of the Application Deadline: electricity, water, sewer service, and roads for the proposed Development, as outlined in Item 13 of Exhibit C of the RFA; Item 13 of Exhibit C goes on to provide: 13. Certification of Ability to Proceed: Within 21 Calendar Days of the date of the invitation to enter credit underwriting, the following information must be provided to the Corporation: a. Submission of the completed and executed 2013 Florida Housing Finance Corporation Local Government Verification of Status of Site Plan approval for Multifamily Developments form. * * * c. Evidence from the Local Government or service provider, as applicable, of the availability of infrastructure as of Application Deadline, as follows: * * * Sewer: Submission of the completed and executed 2013 Florida Housing Finance Corporation Verification of Availability of Infrastructure — Sewer Capacity, Package Treatment, or Septic Tank form or a letter from the service provider which is dated within 12 months of the Application Deadline, is Development specific, and specifically states that sewer service is available to the proposed Development as of the Application Deadline. The 2013 Florida Housing Finance Corporation Local Government Verification of Status of Site Plan Approval for Multifamily Developments Form (Site Plan Approval Form) and the 2013 Florida Housing Finance Corporation Verification of Availability of Infrastructure — Sewer Capacity, Package Treatment, or Septic Tank Form (Certification of Sewer Capacity Form) are incorporated by reference in the RFA. The Site Plan Approval Form requires (in the case of Miami-Dade County which does not have a preliminary or conceptual site plan approval process) that the local government confirm that the site plan was reviewed as of the application deadline. Pinnacle and APC assert that the site plan that ATA submitted to the City of Miami for review included a strip of land that is not legally owned by the current owner and will not be conveyed to ATA under the Purchase and Sale Agreement. As a result, they contend, the site plan review which was required on or before the application deadline did not occur. Pinnacle argues that ATA’s certification in its application was incorrect, that this was a mandatory requirement that was not met, and that it will be impossible for ATA to provide the Site Plan Approval Form in credit underwriting. TC similarly maintains that ATA could not “acknowledge and certify” as part of its application that it would later certify that it had “ability to proceed” because the RFA (at Section Four 10.b.(2)(b) quoted above) requires that “sewer service” be “in place” for ATA’s proposed development as of the application deadline. TC also asserts that the Certification of Sewer Capacity Form explicitly states (and that any service provider letter must, too) that no moratorium is applicable to a proposed development. ATA did not submit a Certification of Sewer Capacity Form. Miami-Dade County will not complete such forms. The “letter of availability” option was created to accommodate Miami-Dade County. The November 12, 2013, letter from Miami-Dade Water and Sewer regarding ATA’s development does not state that there is no applicable moratorium in effect. In fact, the letter affirmatively acknowledges that flow to the gravity system already connected to the property cannot be increased because there is a moratorium in effect as to the pumping station serving the abutting gravity sewer basin. The letter from the County states that, if the pumping station is still in Moratorium Status “at the time this project is ready for construction,” that a private pump station is acceptable. It is logical to conclude that this means sewer service would be available at that time and that sewer service was similarly available at the time of application deadline. The letter, therefore, implies, but does not specifically state, that “sewer service is available to the proposed development as of the application deadline.” The moratorium in effect at the application deadline was not a “general” moratorium. It applied only to the pump station serving the abutting gravity sewer basin, but it was applicable to the proposed development and precluded any increase in the flow to the gravity system connected to the property. A moratorium pertaining to sewer service applicable to ATA’s proposed development was in effect at the time that ATA’s application was submitted. Sewer capacity was otherwise available for the proposed development through use of a private pump station. ATA asserts, first, that ATA has not yet filed certification of ability to proceed or the required forms or letter, that it is not to do so until after it is invited to enter credit underwriting, that FHFC has consequently yet to make a determination as to ATA’s ability to proceed, and that therefore any issues as to site plan or sewer service are not yet ripe for consideration. As to the site plan, ATA further maintains that even if it had been required to provide evidence of ability to proceed as part of its application, the site plan submitted to the City of Miami did not represent that the alley was part of the ATA site. ATA, therefore, asserts that the site plan that was reviewed was the correct one, and that its application certification was correct. The plan of the site of ATA’s development project indicates that the site is bifurcated by a private alley, which is not dedicated as a street, avenue, or boulevard. The legal description of the development project, as submitted to the Department of Planning and Zoning of the City of Miami, included lots 2 through 7 and lots 19 and 20. It did not include the strip of land that lies between these lots (lots 2 through 7 lie to the West of the alley and lots 19 and 20 lie to the East of it.) As to sewer availability, ATA asserts that the 2011 Universal Cycle and the RFA are significantly different. ATA maintains that while the former provided that the existence of a moratorium pertaining to sewer service meant that infrastructure was unavailable, this language was removed from the RFA. ATA contends that a letter of availability need not “mimic” the Certification of Sewer Capacity Form and that the RFA allows a development to certify sewer availability by other means when a moratorium is in effect. Mr. Reecy testified that FHFC takes the certified application at face value, regardless of what other information the Corporation might have at hand. As to the site plan, he testified that even had site plan approval been a part of the scoring process, FHFC would not have found ATA’s application ineligible on that ground. He testified that the alley would not be a problem unless it was a “road” or something similar. He testified that it also could have been a problem if the measurement point to measure the distance to nearby amenities was not on the property, but he was not aware that that was the case in ATA’s application. As for sewer service, Mr. Reecy testified that a letter from the service provider does not have to say “exactly” what is on the form, but stated that it does have to give “the relevant information” to let FHFC know if sewer is “possible.” He testified that the only guidance as to what constituted sewer “availability” was contained in the criteria found on the Certification of Sewer Capacity Form. One of the four numbered requirements on the Certification of Sewer Capacity Form is that there are no moratoriums pertaining to sewer service that are applicable to the proposed development. Under the RFA, the Certification of Sewer Capacity Form could not be completed for a proposed development for which a moratorium pertaining to sewer service was in effect at the time the application was submitted. The form could not be certified by the service provider even if it was possible for such a development to obtain sewer service by other means. The text on the 2013 form is substantively identical to that on the form used during the 2011 Universal Cycle, that wording was specifically drafted to require that any moratorium on sewer infrastructure would be a disqualifying criterion, and the 2013 Certification of Sewer Capacity Form still has that effect. No challenge to the use of the form in the RFA was filed. Even though the language of the 2011 Universal Cycle which paralleled the text on the form does not appear in the RFA, that criterion remains as part of the RFA because of the incorporated Certification of Sewer Capacity Form. In any event, the site plan and sewer availability issues must await at least initial resolution by FHFC during the credit underwriting phase. The testimony of Mr. Reecy clearly indicated that FHFC interprets the RFA specifications and its rules to move consideration of site plan issues and infrastructure availability to the credit underwriting phase. It has not been shown that this is an impermissible interpretation. Town Center’s Application Pinnacle alleges that TC’s application fails to demonstrate site control, because the applicant, Town Center Phase Two, LLC, is not the buyer of the site it intends to develop. The RFA requires at Section Four A.7. that an applicant must provide a copy of a contract, deed, or lease to demonstrate site control: 7. Site Control: The Applicant must demonstrate site control by providing, as Attachment 7 to Exhibit A, the documentation required in Items a., b., and/or c., as indicated below. If the proposed Development consists of Scattered Sites, site control must be demonstrated for all of the Scattered Sites. a. Eligible Contract - For purposes of the RFA . . . the buyer MUST be the Applicant unless an assignment of the eligible contract which assigns all of the buyer's rights, title and interests in the eligible contract to the Applicant, is provided. If the owner of the subject property is not a party to the eligible contract, all documents evidencing intermediate contracts, agreements, assignments, options, or conveyances of any kind between or among the owner, the Applicant, or other parties, must be provided . . . . RFA at page 23. The Contract for Purchase and Sale of Real Property submitted as Attachment 7 to TC’s application is signed by Mr. Milo, who is identified as Vice President. The Buyer on the signature page is incorrectly listed as RUDG, LLC. No other assignment, intermediate contract, agreement, option, or conveyance was included with TC’s application to indicate that TC otherwise had site control of the property. The applicant entity, Town Center Phase Two, LLC, is correctly listed in the opening paragraph of the Contract for Purchase and Sale of Real Property as the “Buyer.” RUDG, LLC, is the 99.99 percent Member of Town Center Phase Two, LLC, and is also the sole Member and Manager of Town Center Phase Two Manager, LLC, which is the .01 percent Managing Member of Town Center Phase Two, LLC. Mr. Milo is a Vice President of RUDG, LLC, a Vice President of Town Center Phase Two Manager, LLC, and a Vice President of the applicant, Town Center Phase Two, LLC. Florida Administrative Code Rule 67-60.008, provides that the Corporation may waive minor irregularities in an otherwise valid application. The term “Minor Irregularity” is defined by rule 67- 60.002(6), as follows: (6) “Minor Irregularity” means a variation in a term or condition of an Application pursuant to this rule chapter that does not provide a competitive advantage or benefit not enjoyed by other Applicants, and does not adversely impact the interests of the Corporation or the public. Mr. Reecy testified that FHFC interpreted the rule to mean that if information requested by the RFA is reasonably available within the Application, even if it was not provided exactly in the place where it was requested, the failure to have it in the particular place it was requested is a minor irregularity. Although the information on the signature page of the Contract for Purchase and Sale of Real Property identifying the Buyer as RUDG, LLC, was a discrepancy in the application, the contract elsewhere identified Town Center Phase Two, LLC, as the Buyer, and Mr. Milo was, in fact, authorized to sign for the true Buyer. Ms. Amy Garmon’s deposition testimony indicated that because she was able to determine from other places in the application that the Buyer was the applicant, and that Mr. Milo was authorized to sign for the Buyer, she found this portion of TC’s application to be compliant, and she didn’t see that there was a “minor irregularity” that needed to be waived. However, it is determined that FHFC actually did finally determine that the error in identification constituted a minor irregularity that was waived, in accordance with Mr. Reecy’s testimony. Although it was Ms. Garmon who called attention to the irregularity, Mr. Reecy is in a position of higher authority within the FHFC and is better able to address the Corporation’s actions with respect to TC’s application. Pinnacle also asserts that TC’s finance documents fail, based upon the same signature issue. TC submitted equity proposals detailing its construction funding sources that were addressed to Mr. Milo and endorsed by him as “Vice President.” FHFC similarly concluded that Mr. Milo had authority to endorse the finance letters on behalf of TC. There is evidence to support FHFC’s findings that TC was the actual Buyer, that Mr. Milo had authority to sign the contract and the equity documents, and that the discrepancies in the documents were minor irregularities. Pinnacle’s Application The equity commitment letter from Wells Fargo Bank regarding Pinnacle’s development, as submitted to FHFC, contained only pages numbered one, two, and four of a four-page letter. It is clear that page three is actually missing and the letter was not simply incorrectly numbered, because of discontinuity in the text and in the numbering of portions of the letter. APC contends that Pinnacle’s application should have been deemed ineligible for award because of the missing page. Mr. Reecy testified that even though a page of Pinnacle’s equity commitment letter was missing, all of the RFA requirements were set forth in the remaining pages. He acknowledged that the missing page might have included unacceptable conditions for closing or information that was inconsistent with the other things in the application, but stated that FHFC determined that the missing page from Pinnacle’s equity letter was a minor irregularity. There is evidence to support FHFC’s finding that the missing page was a minor irregularity. APC’s Application The RFA provides at Section Four, A.3.c., at page 5: c. Experienced Developer(s) At least one Principal of the Developer entity, or if more than one Developer entity, at least one Principal of at least one of the Developer entities, must meet the General Developer Experience requirements in (1) and (2) below. (1) General Developer Experience: A Principal of each experienced Developer entity must have, since January 1, 1991, completed at least three (3) affordable rental housing developments, at least one (1) of which was a Housing Credit development completed since January 1, 2001. At least one (1) of the three (3) completed developments must consist of a total number of units no less than 50 percent of the total number of units in the proposed Development. For purposes of this provision, completed for each of the three (3) developments means (i) that the temporary or final certificate of occupancy has been issued for at least one (1) unit in one of the residential apartment buildings within the development, or (ii) that at least one (1) IRS Form 8609 has been issued for one of the residential apartment buildings within the development. As used in this section, an affordable rental housing development, including a Housing Credit development that contains multiple buildings, is a single development regardless of the number of buildings within the development for which an IRS Form 8609 has been issued. If the experience of a Principal for a Developer entity listed in this Application was acquired from a previous affordable housing Developer entity, the Principal must have also been a Principal of that previous Developer entity. (2) Prior General Development Experience Chart: The Applicant must provide, as Attachment 4 to Exhibit A, a prior experience chart for each Principal intending to meet the minimum general development experience reflecting the required information for the three (3) completed affordable rental housing developments, one (1) of which must be a Housing Credit development. Each prior experience chart must include the following information: Prior General Development Experience Chart Name of Principal with the Required Experience Name of Developer Entity (for the proposed Development) for which the above Party is a Principal: ___ ___________ ___ Name of Development Location (City & State) Affordable Housing Program that Provided Financing Total Number Of Units Year Completed RFA at pages 5, 6. Exhibit A to the RFA, at 3.c., further provides: General Developer Experience For each experienced Developer entity, the Applicant must provide, as Attachment 4, a prior experience chart for at least one (1) experienced Principal of that entity. The prior experience chart for the Principal must reflect the required information for the three (3) completed affordable rental housing developments, one (1) of which must be a Housing Credit development. RFA at page 41. Ms. O’Neill, a Senior Policy Analyst at FHFC and member of the Review Committee responsible for scoring the applications’ developer information section, testified at hearing. When FHFC first started scoring applications, Ms. O’Neill was not taking any action to confirm principal developer experience, but rather was taking the information provided by applicants at face value, as it had been submitted on the chart. A colleague of Ms. O’Neill’s, not serving on the Review Committee, called her attention to the fact that a development that was then going through credit underwriting (following an award during the 2011 funding cycle) had recently requested that FHFC approve a change to the developer entity. Ms. O’Neill testified that this request raised a question at FHFC as to whether Ms. Wong, listed by APC as the principal with the required experience, met the requirements. FHFC decided to confirm that Ms. Wong had the required experience for the developments listed in the RFA. Ms. O’Neill stated that she did not make any inquiry to Ms. Wong or to Atlantic Pacific Communities as to whether Ms. Wong was, in fact, a principal of St. Luke’s Development, LLC, developer of St. Luke’s Life Center, because “we’re not really supposed to do that.” Ms. O’Neill instead looked at portions of a credit underwriting report on the St. Luke’s Life Center project that were researched and shown to her by a colleague. Ms. O’Neill did not see Ms. Wong listed in that report as a principal. She did find information in FHFC files that Ms. Wong was a principal on the other two listed developments. Ms. Thorp testified that she researched several documents in FHFC’s possession and found no information indicating that Ms. Wong was a principal for the St. Luke’s development. She testified that Ms. Wong or another representative of APC was not contacted about the issue because that would have given them an unfair advantage over other applicants. Based upon the information in its files, FHFC determined that Ms. Wong did not meet the requirements for principal developer experience. FHFC then similarly reviewed the files of other applicants who had listed in-state developments as their experience, but was unable to review out-of-state experience, so out-of-state experience continued to be accepted at face value. Ms. Wong was not originally a principal in the St. Luke’s development. However, it was demonstrated at hearing through documentary evidence that Ms. Wong was later appointed an officer of St. Luke’s Development, LLC, effective March 2007. That change was submitted to the credit underwriter, and Ms. Wong was a principal for the developer entity before it completed credit underwriting. Both Ms. O’Neill and Ms. Thorp testified that if the documents provided at hearing by APC had been in FHFC’s possession at the time APC’s application was scored, FHFC would have found that Ms. Wong was a principal of the St. Luke’s development and that her experience met principal developer experience requirements. In light of the evidence presented at hearing, it is clear that FHFC’s conclusion was wrong. The prior experience chart submitted by APC as part of its application provided all of the information requested by the RFA, and all of that information was accurate. The information available to FHFC in the application correctly indicated that Ms. Wong was a principle for the developer of the St. Luke’s Life Center development. APC’s application met all requirements of the RFA with respect to prior developer experience. The Corporation’s preliminary determinations that Ms. Wong was not a principal in the St. Luke’s development, and that the APC application did not, therefore, meet principal experience requirements to the contrary, made in good faith based upon incomplete information contained in its files, was clearly erroneous. FHFC’s contention that APC should have submitted explanations or further documentation of Ms. Wong’s developer experience at the time it submitted its application is untenable. APC submitted all of information requested of it. FHFC asked for a chart to be completed, which APC did, completely and accurately. An applicant cannot be found ineligible for failing to do more than was required by the RFA. Credit Underwriting A comparison of the RFA and rules with the 2011 Universal Cycle process shows that the Corporation has moved many requirements formerly required as part of the eligibility and scoring phase into a second review in the credit underwriting phase, as noted earlier. Rule 67-48.0072 provides in part: Credit underwriting is a de novo review of all information supplied, received or discovered during or after any competitive solicitation scoring and funding preference process, prior to the closing on funding, including the issuance of IRS Forms 8609 for Housing Credits. The success of an Applicant in being selected for funding is not an indication that the Applicant will receive a positive recommendation from the Credit Underwriter or that the Development team’s experience, past performance or financial capacity is satisfactory. The rule goes on to provide that this de novo review in the credit underwriting phase includes not only economic feasibility, but other factors statutorily required for allocation of tax credits, such as evidence of need for affordable housing and ability to proceed. These factors might cause an application to fail and never receive funding, even though it was nominally “awarded” the credits earlier. In that event, the RFA provides: Funding that becomes available after the Board takes action on the Committee’s recommendation(s), due to an Applicant declining its invitation to enter credit underwriting or the Applicant’s inability to satisfy a requirement outlined in this RFA, and/or Rule Chapter 67-48, F.A.C., will be distributed to the highest scoring eligible unfunded Application located in the same county as the Development that returned the funding regardless of the Funding Test. If there is not enough funding available to fully fund this Application, it will be entitled to receive a Binding Commitment for the unfunded balance. If an applicant nominally “awarded” funding in the eligibility and scoring phase fails credit underwriting, the next applicant in the queue of eligible applicants may still be granted funding, and so, is substantially affected by FHFC’s decisions in the credit underwriting phase.

Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Florida Housing Finance Corporation enter a final order finding that APC Four Forty Four, Ltd., is eligible for funding, adjusting the Sorting Order accordingly, and otherwise dismissing the formal written protests of all Petitioners. DONE AND ENTERED this 4th day of June, 2014, in Tallahassee, Leon County, Florida. S F. SCOTT BOYD Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 4th day of June, 2014.

Florida Laws (6) 120.569120.57120.68420.504420.507420.5099
# 6
PINNACLE HEIGHTS, LLC vs FLORIDA HOUSING FINANCE CORPORATION, 15-003304BID (2015)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Jun. 09, 2015 Number: 15-003304BID Latest Update: Sep. 21, 2015

The Issue The issue is whether Florida Housing and Finance Corporation's intended decision to award low income housing tax credits for an affordable housing development in Miami-Dade County to Rio at Flagler, LP (Rio), was contrary to solicitation specifications, and if so, whether that determination was clearly erroneous or contrary to competition.

Findings Of Fact Florida Housing is a public corporation created pursuant to section 420.504. One of its responsibilities is to award low-income housing tax credits, which developers use to finance the construction of affordable housing. Tax credits are made available to states annually by the United States Treasury Department and are then awarded pursuant to a competitive cycle that starts with Florida Housing's issuance of a RFA. In this case, the RFA was issued on November 21, 2014, modified slightly on January 30, 2015, and required the filing of applications by February 10, 2015. According to the RFA, Florida Housing is expected to award up to an estimated $4,367,107 of housing credits for the following demographic set- aside: housing projects targeted for either the family or elderly population in Miami-Dade County. The credits will be awarded to the applicants with the highest total scores. Pinnacle submitted Application No. 2015-211C seeking $2,560,000.00 in annual allocation of housing credits to finance the construction of a 104-unit residential rental development to be known as Pinnacle Heights. Rio submitted Application No. 2015-217C seeking $1,940,000.00 in annual allocation of housing credits to finance the construction of a 76-unit residential development to be known as Rio at Flagler. The agency's Executive Director appointed a review committee comprised of Florida Housing staff to evaluate the applications for eligibility and scoring. Fifty-three applications were received, processed, deemed eligible or ineligible, scored, and ranked pursuant to the terms of the RFA, administrative rules, and applicable federal regulations. Applications are considered for funding only if they are deemed "eligible," based on whether the application complies with various content requirements. Of the 53 applications filed in response to the RFA, 43 were found to be eligible, and ten were found ineligible. Both Pinnacle and Rio were found eligible for the family/elderly demographic. The RFA specifies a sorting order for funding eligible applicants. All eligible applicants in the family/elderly demographic, including Pinnacle and Rio, achieved the maximum score of 23 based on criteria in the RFA. Recognizing that there would be more applications than available credits, Florida Housing established an order for funding for applicants with tied scores using a sequence of six tiebreakers, with the last being a lottery number assigned by the luck of the draw. Applications with lower lottery numbers (closer to zero) are selected before those with higher lottery numbers. Both Pinnacle and Rio received the maximum 23 points and met all tiebreaker criteria. In other words, both had so- called "perfect" applications. The ultimate deciding factor for perfect applications is a randomly generated lottery number that is assigned at the time each application is filed. Rio's number is four, while Pinnacle's number is six. Because Rio had a lower lottery number than Pinnacle, Florida Housing issued its notice of intent to award tax credits to Rio and another applicant (with a lower lottery number) not relevant here. Pinnacle timely filed a formal written protest. As amended, Pinnacle's protest is narrowed to a single issue -- whether the bus stop identified in Rio's application is a Public Bus Transfer Stop, as defined in the RFA. A failure to comply with this provision would lower Rio's total proximity score and make it ineligible to receive tax credit funding. The RFA specifies two Point Items in the family/elderly demographic category. The first Point Item is "Local Government Contributions," for which a maximum of five points could be awarded. The second is "Proximity to Transit and Community Services," for which points are awarded based on the distance between the proposed development and the selected transit and community service. A maximum of six proximity points are allowed for Transit Services, while a maximum of 12 proximity points are allowed for Community Services for a total maximum of 18 proximity points. Under the terms of the RFA, if an applicant achieves a minimum of 12.25 proximity points for Community Services and Transit Services, a "point boost" up to the maximum total score of 18 proximity points is added to the applicant's score. Rio's transit score of six points is the focus of this dispute. The RFA lists five types of Transit Services that an applicant can self-select to obtain proximity points, including Public Bus Stop (maximum two points) and Public Bus Transfer Stop (maximum six points). Applicants may select only one type of transit services on which to base their transit score. Depending on the type of transit service selected, an applicant may receive up to a maximum of six points for Transit Services. To verify the information in the application, an applicant must submit a Surveyor Certification Form, which is completed and signed by a licensed surveyor. In making its preliminary decision to award tax credits, Florida Housing relies on the information provided in the form and does not second-guess the surveyor. Issues regarding the accuracy of the information in the form are presented through challenges by other applicants. Because Rio had only ten points for proximity to Community Services, it needed at least 2.25 transit points in order to obtain the minimum 12.25 proximity points necessary to achieve a point boost up to 18 points and be in the running for funding. Accordingly, Rio's application sought six points for the project site's proximity to a Public Bus Transfer Stop. A Public Bus Transfer Stop is defined on page 19 of the RFA as follows: This service may be selected by Family and Elderly Demographic Applicants. For purposes of proximity points, a Public Bus Transfer Stop means a fixed location at which passengers may access at least three routes of public transportation via buses. Each qualifying route must have a scheduled stop at the Public Bus Transfer Stop at least hourly during the times of 7 a.m. to 9 a.m. and also during the times of 4 p.m. to 6 p.m. Monday through Friday, excluding holidays, on a year-round basis. This would include both bus stations (i.e. hubs) and bus stops with multiple routes. Bus routes must be established or approved by a Local Government department that manages public transportation. Buses that travel between states will not be considered. In sum, a Public Bus Transfer Stop is a fixed location at which passengers may access "at least three routes of public transportation via buses," with each route having a scheduled stop at that location at least hourly during morning and afternoon rush hours, Monday through Friday, on a year-round basis. To comply with this requirement, and based upon oral information provided by customer service at Miami-Dade Transit Authority (Authority), Rio selected a bus stop located at West Flagler Street and Northwest 8th Avenue. Rio represented that this location was served by three qualifying routes: Route 6 (Coconut Grove), Route 11 (Florida International University- University Park Campus), and Route 208 (Little Havana Circulator). The RFA requires that a bus route be established or approved by the "local government department" that manages public transportation, in this case the Authority. Florida Housing defers to the local government in determining whether a selected bus route is a qualifying bus route within the meaning of the RFA. The head of the local government department that manages public transportation is Gerald Bryan, the chief of service planning and scheduling. By deposition, Mr. Bryan testified that the location selected by Rio has only two qualifying routes: 11 and 208. Route 6, the third route relied upon by Rio, does not run hourly during the requisite rush hour times as required by the RFA and therefore is not a qualifying route. With only two qualifying routes, the transit service selected by Rio is a Public Bus Stop for which only two points, rather than six, can be awarded. Had this information been available to Florida Housing when it reviewed Rio's application, Rio's proximity score would have been less than 12.25, making it ineligible to receive a point boost and achieve the maximum total score of 18 proximity points. Because Rio is ineligible for funding, the next applicant in line is Pinnacle, as it has the next lowest lottery number among the eligible applications that received 23 points. Rio does not dispute that Route 6 fails to make the requisite stops during rush hours to be considered a qualifying route. However, it contends that Route 11 functionally serves as two distinct routes because it has two separate destinations: the Mall of the Americas and Florida International University Park Campus. But whether Route 11 is a single route or two routes is a determination that must be made by the local government, and not the applicant. Mr. Bryan testified that the Authority established Route 11 as a single route with two separate termination points. He further explained that it is a standard practice for a single route, such as Route 11, to have more than one terminus in order to provide a higher level of customer service. Because Florida Housing does not second guess the determination of the local government, the undersigned has rejected Rio's assertion that the bus stop is a Public Bus Transfer Stop. Without the inclusion of the six proximity points for this type of transit service, Rio's application is not eligible for funding in this cycle.

Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Florida Housing Finance Corporation enter a final order finding that Rio's application is ineligible for funding and that Pinnacle's application should be selected for funding under RFA 2014-116. DONE AND ENTERED this 31st day of August, 2015, in Tallahassee, Leon County, Florida. S D. R. ALEXANDER Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 31st day of August, 2015. COPIES FURNISHED: Kate Fleming, Corporation Clerk Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1367 (eServed) Michael P. Donaldson, Esquire Carlton Fields Jorden Burt, P.A. Post Office Box 190 Tallahassee, Florida 32302-0190 (eServed) Hugh R. Brown, General Counsel Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1367 (eServed) Betty C. Zachem, Esquire Florida Housing Finance Corporation 227 North Bronough Street, Suite 5000 Tallahassee, Florida 32301-1367 (eServed) J. Stephen Menton, Esquire Rutledge Ecenia, P.A. 119 South Monroe Street, Suite 202 Tallahassee, Florida 32301-1591 (eServed) Gary J. Cohen, Esquire Shutts and Bowen, LLP 1500 Miami Center 201 South Biscayne Boulevard Miami, Florida 33131-4329 (eServed)

Florida Laws (4) 120.569120.57120.68420.504
# 8
BELLA GRANDE, LTD. vs FLORIDA HOUSING FINANCE AGENCY AND KYLE'S RUN, 96-000326RU (1996)
Division of Administrative Hearings, Florida Filed:Tallahassee, Florida Jan. 17, 1996 Number: 96-000326RU Latest Update: Dec. 13, 1996

Findings Of Fact Section 420.5099, Florida Statutes, designates Respondent as the "housing credit agency" responsible for allocating Florida's share of federal income tax credits for low- income housing. Section 42 of the Internal Revenue Code provides federal income tax credits for qualifying low-income housing expenditures. The amount of the tax credit is nine percent of the qualifying basis, and this nine percent credit is available annually for ten years. Calculation of the qualifying basis starts with the project cost, less the cost of land acquisition. The difference is then multiplied by a ratio of affordable units (or floor space, if a smaller ratio results) over total units (or floor space) in the proposed project. The amount of federal income tax credit is based on the population of each state. In Florida, the demand exceeds the supply of these credits, so Florida's allocation plan includes procedures for the allocation of these limited credits. Section 42(m)(2)(A), Internal Revenue Code, limits the credit allocation for any project to the amount Respondent "determines is necessary for the financial feasibility of the project and its viability as a qualified low- income housing project throughout the credit period." Section 42(m)(2)(B)(iv), Internal Revenue Code, requires Respondent, in determining the feasibility and viability of the project, to consider "the reasonableness of the developmental and operational costs of the project." Certain guidelines have evolved in the low-income housing tax credit (LIHTC) program to limit the fees payable to developers and contractors, on which credits may be calculated. The portion of an allocation based on developer's fees is limited to fees constituting no more than 20 percent of a project's hard costs plus land acquisition. The 20 percent developer's limitation, which is not a promulgated rule, is not directly involved in any of the four cases. Another guideline, which is contingently involved in these cases, is that the portion of an allocation based on contractor's fees is limited to fees constituting no more than 14 percent of a project's hard costs. The so-called "626 rule" breaks the contractor's maximum fees into 6 percent general requirements, 2 percent overhead, and 6 percent profit. Each Petitioner is a limited partnership that constructed, owns, and leases low-income houses. Each Petitioner has applied for and received an allocation of LIHTCs for the construction and leasing of these low-income houses. In the related cases, Respondent tried to reduce Petitioners' LIHTCs for the two projects. Respondent claimed that the apparent general contractor, Heritage Construction Co. Inc. (Heritage), was not the real general contractor because Heritage had entered into prime subcontracts on both projects with Picerne Construction Corp. (Picerne) assuming nearly all of the work described in the contracts for lower costs. Respondent proposed instead to allocate LIHTCs based on the lower costs of the prime subcontracts. If Respondent failed to prevail in disregarding the contract costs in the contract between each Petitioner and Heritage, the 14 percent limitation would not limit the allocations of LIHTCs to Petitioners. These transactions were structured so that the total contractor's fees payable to Heritage did not exceed the 14 percent limitation or the individual components of the 14 percent limitation. However, if Respondent prevailed in disregarding the contract costs in the contract between each Petitioner and Heritage, and instead succeeded in using the lower contract amounts in the two Picerne prime subcontracts, then the 14 percent limitation would limit the allocation of LIHTCs. In this event, Petitioners challenge the 14 percent limitation in order to try to recover some of the lost tax credits. The 14 percent limitation, which is not promulgated as a rule, is recorded in two documents: the Best Practices Manual for the LIHTC program and the Underwriting Guidebook. It is undisclosed when the Best Practices Manual first included the 14 percent limitation, but this limitation has been in effect for about three years. The reference to the 14 percent limitation was included in the Underwriting Guidebook after March 1995, or else the Underwriting Guidebook itself was not in existence until after March 1995. The Underwriting Guidebook, which was prepared jointly by Respondent and underwriters, prohibits the allowance of general contracting fees in excess of 14 percent of hard costs. Respondent is not engaged in rulemaking as to the 14 percent limitation. Respondent presented no evidence that rulemaking as to this limitation was not feasible. To the contrary, rulemaking as to the 14 percent limitation is both feasible and practicable.

Florida Laws (3) 120.57120.68420.5099
# 10

Can't find what you're looking for?

Post a free question on our public forum.
Ask a Question
Search for lawyers by practice areas.
Find a Lawyer