Normally a SMSF is restricted from borrowing money to purchase assets to be held by the fund (S67 of the SIS Act). However there is one exception to this ruling, which is a Limited Recourse Borrowing Arrangement (LRBA).
Under a LRBA a SMSF can borrow money as long as the lender uses only the asset being purchased as security, that is, the lender's recourse is limited only to the purchased asset. However, Trustees should always consider the quality of the investments and whether the fund can meet all of the future obligations under the arrangement.
A Trustee can only enter into such an arrangement where the purchase of the asset is consistent with the investment strategy of the fund and the governing rules of the fund allow the trustee to enter into any borrowing arrangement.
ATO legislation states, if your SMSF chooses to use a LRBA, then the arrangement must satisfy the following conditions:
If the fund chooses to purchase a property, then significantly, the fund cannot borrow to make improvements to the property (see article on Repair v improvement in a SMSF property asset). However, the fund may use its own cash reserves to undertake improvements to the property. Alternatively, a fund may have tenant pay for the improvements. While this is a valid strategy, the Trustee must be aware of:
Before, you enter into any LRBA in a SMSF, ensure that you seek advice regarding the dos and don'ts and ensure your fund remains complaint at all times, otherwise any capital growth on the asset may go straight to the ATO's piggy bank.
For more information on SMSF compliance and regulations, please contact our wealth team.
- See more at: http://www.azuregroup.com.au/resources/blog/smsf/limited-recourse-borrowing-arrangements-for-smsfs#sthash.cdINC5Wb.dpufThis article is intended to provide general information only, and is not to be regarded as legal or financial advice. The content is based on current facts, circumstances, and assumptions, and its accuracy may be affected by changes in laws, regulations, or market conditions. Accordingly, neither Azure Group Pty Ltd nor any member or employee of Azure Group or associated entities, undertakes responsibility arising in any way whatsoever to any persons in respect of this alert or any error or omissions herein, arising through negligence or otherwise howsoever caused. Readers are advised to consult with qualified professionals for advice specific to their situation before taking any action.