In an effort to summarize the highlights of the U.S. Department of Housing and Urban Development (HUD) LEAN E-mail Blasts that we receive, and rarely have time to review in a timely fashion, we at Pepper are providing this quick synopsis of the latest LEAN update. Our aim is to provide pertinent information succinctly as a roadmap to the LEAN E-mail Blasts, not to replace the LEAN E-mail Blasts. We hope you find these summaries helpful. Here is a link to the complete July 23, 2014 LEAN Blast.

In response to HUD’s February request for comments on the new loan documents, HUD has posted revised Section 232 documents. The changes to the documents include a few substantive revisions, as well as edits resolving scrivener’s errors and updated OMB form information. The new documents are posted on HUDClips for immediate use and redlines are provided on the ORCF Web site – note that the quick links on the Lean 232 documents Web page, where the redlines are located, have not been updated with clean versions of the new loan documents. The documents must be used for any legal packages submitted after August 31, 2014.

We have found that the vast majority of the edits are designed to make the 232 program more palatable for third-party operators. This is a welcomed approached as an increasing number of third-party operators were having difficulty getting comfortable with HUD’s requirements. The longer the LEAN programs excellent track record continues and the faster the processing times shrink, more and more interested owners and operators will become interested. We believe the LEAN program will continue evolve and become more friendly to owners and third-party operators as the 232(a)(7) queue runs its course and the lending industry brings new, strong borrowers and operators into the FHA-insured realm.

In Section 3, “Project Operating Deficiencies,” ORCF revised the definition of a “Project Operating Deficiency,” which gives rise to the need to retain a consultant, by substituting debt service coverage ratio for several other financial indicators. ORCF also added language explicitly limiting the circumstances in which a denial of payments or a proposed termination of Permits and Approvals would constitute a Project Operating Deficiency. ORCF’s intention was to clarify that an operator diligently and adequately addressing such matters would have some reasonable time to resolve them. In addition, ORCF clarified that a Project Operating Deficiency will not be considered an Event of Default unless such circumstance meets the requirements for an Event of Default pursuant to the relevant Loan Document.

In Section 4, “Master Tenant and/or Operator Rights to Cure,” ORCF clarified that the defaults being referenced are those of the borrower. ORCF also revised the section to allow an operator or master tenant to cure a borrower default even if a Project Operating Deficiency exists.

In Section 10, “Miscellaneous,” ORCF revised the definition of “Material Risk of Termination” to make it consistent with the definition used in the Regulatory Agreements.

2. Operator Security Agreement and Rider (HUD-92323-ORCF)

In Section 2, “Representations; General Covenants,” ORCF revised subsection (c) to recognize that Books and Records might be located off-site.

In Section 8, ORCF revised subsection (g) to clarify that “Permitted Liens” would not be a circumstance constituting an Event of Default.

In Section 23, “Miscellaneous,” ORCF revised subsection (b) to recognize that certain sections of the document impose a reasonableness standard on the decisions of a Lender.

ORCF added Section 25, which will be used to indicate whether the Security Agreement includes a Third Party Rider.

Finally, ORCF added a final paragraph to the Third Party Rider, so as to include a definition of Material Risk of Termination consistent with the definition used in the other Section 232 documents.

3. Master Tenant Security Agreement (HUD-92340-ORCF)

ORCF revised the Master Tenant Security Agreement to include the same changes set forth in the Operator Security Agreement and also added a Third Party Rider to the Master Tenant Security Agreement for use when the Master Tenant is not related to the Borrower.

In Section 3, “Representations; General Covenants,” ORCF edited subsection (j) explaining how a Master Tenant might receive Government Payments due the Operator.

In Section 6, “Consultants,” ORCF edited the definition of “Project Operating Deficiency” consistent with the edits discussed above with respect to the Master Lease SNDA.

In Section 8, “Notice of Violation and Event of Default,” ORCF revised subsection (a) clarifying that in the case of a non-Identity-of-Interest Operator, the payment obligations being referenced therein are those of the Operator.

In Section 20, “Books, Accounts, Financial Reports, Financial Covenants,” ORCF edited subsection (h) elaborating that if ORCF directs that a report be sent to the Lender and/or another third party, it is so that the party can review such reports at ORCF’s direction.

5. Healthcare Regulatory Agreement – Master Tenant (HUD-92337-ORCF)

Made conforming changes that were discussed above with respect to the Master Lease SNDA and the Operator Regulatory Agreement.

In Section 2, “Approved Use; Permits and Approvals,” ORCF edited subsection (c) to clarify that the civil money penalties referenced are those of the Healthcare Facility.

6. Healthcare Regulatory Agreement – Borrower (HUD-92466-ORCF)

In Section 13, “Reserve for Replacement,” ORCF revised subsection (e) so that upon Borrower’s satisfaction of all of its obligations under the Loan Documents, the account balance may be distributed either to the Borrower or the Borrower’s designee.

ORCF edited Section 23 to clarify that goods and services referenced therein are those, if any, that the borrower purchase or acquires in connection with the Project.

In Section 26, “Operator; Cooperation in Change of Operator,” ORCF amended subsection (e) permitting that arms-length negotiated purchase options in a lease are not categorically impermissible.

7. Security Instrument/Mortgage/Deed of Trust (HUD-94000-ORCF)

In Section 1, “Definitions,” ORCF clarified the definitions of “Event of Default,” and “Mortgaged Property” as it applies to security deposits.

In Section 4, “Assignment of Leases; Leases Affecting Mortgaged Property,” ORCF modified subsection (b) to clarify that a Borrower’s right to collect rent, which ceases upon an Event of Default, will be reinstated should the Event of Default be subsequently cured.

Various sections were edited (e.g., Section 7(a)) so that instead of directing the Borrower itself to take action, the document directs the Borrower to take “or cause the Operator to take” the action.

In Section 19, “Property and Liability Insurance,” ORCF modified subsection (c) to explicitly set forth a “reasonableness” standard in the language allowing a lender to impose various requirements for the maintenance of insurance.

Based on further collaboration with the industry, ORCF has further edited Section 2.3(a) (the “standstill provision”). ORCF, at the industry’s behest, added language to make it clear that the FHA Lender could not contact account debtors or seek to change the remittance instructions as to where proceeds of accounts receivable should be paid prior to the AR Lender’s loan being paid in full. ORCF also added language to provide comfort to the FHA Lender and ORCF that the standstill provision would not in any way hamper the FHA Lender’s abilities to exercise remedies to which it may be entitled or to transition the operation of the facility to a new operator or to seek all related licenses, permits and provider agreements.

ORCF is also now requiring that an Intercreditor Agreement be executed for each facility in an account receivable portfolio rather than permitting multiple facilities to be referenced in one Intercreditor Agreement.

9. Guide for Opinion of Operator’s Counsel, and Certification (HUD-92325-ORCF)

After considering comments to the Operator Opinion, ORCF revised three sections that were problematic for opining attorneys:

First, the Opinion permits the opining attorney to limit the opinion to the corporate/partnership/limited liability company law of the Operator’s organizational jurisdiction. Previously, the operator’s attorney was not permitted to limit the scope of the organizational jurisdiction opinion.

Second, the revised Operator opinion allows the opining attorney to limit the opinion to the laws of (i) the property jurisdiction; (ii) the organizational jurisdiction (if different than the property jurisdiction); (iii) the UCC of the state where the operator is located; and, the new addition, (iv) sections 9-314 and 9-304 of the UCC in the state law which controls the terms of the DACA and DAISA. ORCF and OGC hope that the addition of limitation (iv) will give more comfort to the opining attorney that they are not forced to comply with the entire UCC of the state law for the controlling collateral state.

Third, the definition of “Transaction Documents” inappropriately included the accounts receivable documents, and that reference to the accounts receivable documents has now been removed.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

"My best business intelligence, in one easy email…"

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.

Privacy Policy (Updated: October 8, 2015):

hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide

*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.