Posts

Injunctions and bank guarantees: When can a contractor prevent a developer having recourse to bank guarantees or performance bonds?

Case: Uber Builders and Developers Pty Ltd v MIFA Pty Ltd [2020] VSC 596

One feature of construction contracts which is distinctive and unique from other types of contracts is the provision of security from the contractor to the principal. Commonly, security takes the form of retention monies or bank guarantees. The consequences of having recourse to bank guarantees can be serious for the party providing the security (the security provider). In September 2020, the Supreme Court of Victoria handed down a decision in relation to bank guarantees. The decision Uber Builders and Developers Pty Ltd v MIFA Pty Ltd [2020] VSC 596 (Uber), sets out a helpful summary of the principles in respect of bank guarantees, interlocutory hearings and recourse to bank guarantees.

The Facts

Uber Builders and Developers (Uber) sought an injunction preventing MIFA from calling on its bank guarantees. MIFA asserted that it was entitled to have recourse to the bank guarantee as the Superintendent had certified amounts as payable by Uber in respect of rectification costs for defective and incomplete work, liquidated damages, credit allowances and purported variations. As a result of non-payment by Uber of these amounts, MIFA sought to have recourse to the bank guarantees to recover the amounts certified against Uber. To prevent MIFA from having recourse to the bank guarantee, Uber sought interlocutory relief (lawyer jargon for an interim/immediate court order) that MIFA was not allowed to have recourse to the bank guarantee.

The Principles

Nichols J summarised the governing principles in respect of where interlocutory relief is sought to restrain the calling of a performance bond/bank guarantee that has been given under a contract. There principles are:

  1. The applicant for interlocutory relief must show there is a serious question to be tried. The applicant, in this case Uber, must show that there is sufficient reason to think that the applicant would be successful if the matter were to progress to a final hearing;

 

  1. The applicant must show that the ‘balance of convenience’ favours the granting of the injunction. This means that the court should take whichever course appears to carry the lowest risk of injustice should it be wrong in either granting pr not granting the injunction;

 

  1. The court must consider whether damages would be an inadequate remedy. This means that the court has to consider whether the applicant would suffer irreparable injury for which monetary compensation would not be an adequate option; and

 

  1. These questions and factors to consider must be considered together and not as isolated issues.

 

In the context of setting out these guiding principles, Nichols J set out some drafting considerations for security clauses in construction contracts. These are summarised below:

  • Purpose: Bank guarantee or performance bonds may be stipulated for two reasons.
    • The first is to provide security against the risk that the security holder will not recover a sum owing by the defaulting party. In this way, the security acts as a means of ensuring the principal or security holder can recover some money if an amount is payable to the principal/security holder.

 

  • The second is to allocate risk as to who will be out of pocket while a resolution of a dispute is pending. If the security is to allocate risk, then the party holding the security may have recourse, even if it turns out that the other party was not actually in default.

 

  • Conditions of Recourse: If the purpose of the security is to act as an interim allocation of risk, then it is important to consider in what circumstances the principal/security holder will be entitled to have recourse to the security. The parties may agree to allow the security holder to have recourse to the security pending a final determination, but this right should be limited to certain circumstances. For instance, the parties may agree that recourse to the security can only occur if notice is given and/or where the dispute relates to damage caused by the security provider to the works/the project and/or adjoining properties.

 

  • Conditions imposed by the Courts: Where there are no contractual conditions under the contract, the Courts will prevent a party from calling on security where the security holder acts fraudulently or unconscionably in calling on the security.

 

  • Interim Risk Allocation: If the security is intended to be an interim risk allocation tool, the security holder will be entitled to have recourse to the security even if it turns out that the other party was not in default, notwithstanding the existence of a genuine dispute and a serious issue to be tried as to underlying entitlements.

 

Interim Risks

So far, this article has discussed a lot about ‘interim risk allocation’ but what does this actually mean and when is it relevant? Throughout the projects, various issues (such as the valuation of variations and defective work) may arise and payments are generally made on account only. At the end of the contract, the Superintendent will generally issue the final certificate. The final certificate will determine if there has been any over or underpayment by the principal to the contractor, whether there are any liquidated damages, and any other interim issue (such as the valuation of defective work and variations). If a party does not agree with payments to be made under the final certificate, they are generally able to issue a notice of dispute under the contractual provisions or can commence proceedings in relation to the contract. In these circumstances, the interim risk is the amount certified under the final certificate and a final determination of the issue made pursuant to a Court or the dispute resolution process set out in the contract. As the dispute resolution process (whether it be Court, expert determination, arbitration, or another dispute resolution forum under the contract) can take substantial time to finally determine the issues, if the security is an interim risk allocation tool, the principal will be able to have recourse to the security until the matter is finally determined. If it turns out the final certificate was incorrect, this will not prevent the principal from having recourse to security. It will mean that the decision maker will generally order for the principal to make payment of however much they have been overpaid so that the parties’ entitlements are finalised and concluded.

Bringing it back to the case study, Uber, the Superintendent certified that an amount was payable by the contractor to the principal. The contractor disputed the amount that was payable and did not make payment as and when required by the final certificate. As a result, the principal was entitled to have recourse to the security once it had complied with the conditions of recourse under the contract. As these conditions were predominantly notice requirements, the principal was not prevented from having recourse to the security. If Uber had made payment of the final certificate amount and issued the notice of demand, it is arguable that MIFA would not have been able to have recourse to the security. This is because MIFA would not be able to claim that the amount in the final certificate remained unpaid. As a result, contractors are put in the difficult position of paying a disputed amount or the principal may have recourse to the security.

The Takeaways

Intention of the Security

Parties need to be clear about the intentions behind providing security. This can be achieved by drafting the purpose of the security into the security clause of the contract. If there is an intention for the security to be an interim risk allocation tool, it will be much easier for the security holder/principal to have recourse to the security. If the security is only to protect against the failure to pay a sum owing by a party, then the security holder will be able to have recourse to the security if the amount is not paid as and when required under the contract.

Conditions of Recourse

Conditions of recourse essentially mean the security holder promises that they will not have recourse to the security unless those conditions are met. If the parties agree on the circumstances where the security holder can or cannot have recourse to the security, this will bind the security holder irrespective of the terms of the bank guarantee. Typical conditions include where the principal is entitled to payment under the contract.

If the security provider seeks to prevent the security holder from having recourse to the security, the security holder (generally the principal) will be required to show that it has met and/or followed the contractual process.

It is important to note that some jurisdictions, such as Queensland, may impose restrictions on when a party can have recourse to security. For example, under the Queensland Building and Construction Commission Act 1991 (QLD) section 67J(1)-(2), a principal may use a security or retention amount only if they have given 28 days’ notice in writing to the contractor advising of the proposed use and the amount owed. In these jurisdictions, the additional conditions will be imposed in addition to with the conditions of recourse under the contract.

Interim amounts owed

The crux of the purpose of security comes to a head in circumstances where a party disputes the amount owed. For instance, when the Superintended issues that final certificate (as was the case in Uber). If the security clause is drafted to allow for the security to be an interim risk allocation tool, the principal will be entitled to have recourse to the security. This will mean that contractor holds the risk of being out of pocket until the matter is finally determined.

If you are a developer, a contractor or a subcontractor and you or someone you know needs advice in respect of whether it is possible to have recourse to security, please get in touch with the staff at Bradbury Legal. Alternatively, if you are in the process of drafting and negotiating a contract, including the clauses relating to security, Bradbury Legal is able to assist and help you know exactly what you are signing up to.

Spring is here and so is the Building and Construction Industry Security of Payment Regulation 2020

On 1 September 2020, the Building and Construction Industry Security of Payment Regulation 2020 commenced (2020 Regulation) repealing the 2008 Regulation.

The 2020 Regulation will provide the legislative support and administrative detail for the operation of the Building and Construction Industry Security of Payment Act 1999 (NSW) (Act) as provided by the amendments which commenced on 21 October 2019. These amendments came about to address poor payment practices and the high incidence of insolvencies in the building and construction industry and also, to facilitate prompt payment, preserve cash flow and resolve disputes quickly and efficiently.

The 2020 Regulation is not retrospective and will not apply to contracts entered into prior to its commencement date.

Key reforms of the 2020 Regulation include:

  • removing the annual reporting requirements for trust accounts to NSW Fair Trading,
  • introducing a requirement for head contractors to keep a ledger for retention money held in relation to each subcontractor and provide the subcontractor with a copy of a ledger at least once every 3 months or longer period of 6 months if agreed in writing, and also to provide trust account records to subcontractors if their money is held in trust,
  • supporting statements are only required for subcontractors or suppliers directly engaged by the head contractor,
  • removing owner occupier construction contracts as a prescribed class of construction contract to which the Act does not apply, and
  • introducing qualifications and eligibility requirements for adjudicators to improve the quality of adjudication determinations under the Act.  The eligibility requirements include either a degree or diploma in a relevant specified field with at least 5 years’ experience, or at least 10 years’ experience in a relevant specified field.  The continuing professional development requirements for adjudicators will commence on 1 September 2021.

Of particular note, the project value threshold (value of the head contractor’s contract with the principal) for retention money trust account requirements will not be reduced from $20 million to $10 million as previously foreshadowed. The existing threshold will remain. Perhaps, given the current climate, it was considered too much of an administrative burden on head contractors who are already dealing with the pressures of delivering projects during Covid. A copy of the 2020 Regulation is  here.

If you would like to discuss or would like any more information, please contact us at info@bradburylegal.com.au or (02) 9248 3450.

If you would like to receive our regular newsletters, please click  here.

Suspension of relief: take out notices, jurisdictional error and Security of Payment Act

In Parrwood Pty Ltd v Trinity Constructions (Aust) Pty Ltd, the Court confirmed that, for the purposes of the Building and Construction Industry Security of Payment Act 1999 (NSW) (SOPA), taking the work out of the hands of a contractor will not remove reference dates accrued before the take out notice is served, even if they are not actually used until after the take out notice is issued.

Although the facts were unusual and complicated, in the unique world of the SOPA they are not unheard of. This note is useful for parties considering whether:

  1. to issue a take out notice instead of a termination notice (particularly for NSW construction contracts entered into before 21 October 2019); or
  2. to withdraw an adjudication application in the event of jurisdictional error by an adjudicator on the first determination, to re-lodge before a new adjudicator.

The facts

The contractor was working under the principal in a residential building project. The contractor accrued reference dates on the 25th day of each month. The contract contained an AS standard clause where the contractor fails to show reasonable cause for its default:

“the Principal may by written notice to the Contractor:

(a) take out of the Contractor’s hands the whole or part of the work remaining to be completed and suspend payment until it becomes due and payable pursuant to subclause 39.6; or

(b) terminate the Contract.”

The parties fell into dispute and the principal asked the contractor to show cause.

Then:

  • on 25 August 2019, the monthly reference date for a SOPA claim came about;
  • on 3 September 2019, the principal issued a notice that took out of the contractor’s hands all of the work remaining to be completed, instead of terminating the contract; and
  • on 6 September 2019, the contractor issued a payment claim in the amount of $2,023,645.76. This payment claim was said to use the 25 August 2019 reference date.

In response, the principal scheduled “$Nil”.

The contractor applied for adjudication under the SOPA. The adjudicator declined to determine an amount that the contractor was owed (if any), finding the payment claim was invalid.

After it received the first adjudicator’s decision, the contractor “withdrew” its application, and made a second adjudication application. The contractor argued that the first adjudicator had failed to exercise his statutory function in declining to determine the amount owing. The second adjudicator considered the application and awarded over $400,000 to the contractor. The principal applied to the Supreme Court to set aside the second adjudication determination.

There were two broad issues that the Court was required to consider.

Suspension and payment claims

The first issue was what effect the take out notice had on the ability to issue payment claims.

The Court found that even though the payment claim was served after a take out notice, it was saved by the fact that it was served for a reference date occurring before the take out notice was made.

The outcome would have been different if the take out notice was served before the reference date. In this case, the contractor’s rights are suspended by the take out notice, and it cannot make a payment claim under the fast-track SOPA. It can, however, still make a claim under general law.

A take out notice cannot extinguish a right to make a payment claim that already exists.

Second Adjudication

Jurisdictional error

The second issue concerned the unusual circumstances in which a claimant may effectively redo its application.

The Court found that the first adjudicator had not made a ruling that, for example, the contractor was entitled to “$Nil”. Rather, the adjudicator had decided that, no matter what he thought about the facts, he could not determine any adjudicated amount (“I must decline therefore from determining …”).

The first adjudicator had failed to determine the amount of the progress payment (if any) to be paid, as required under section 22(1) of the SOPA. Therefore, the first purported determination was void.

Making a second application

Section 26(3) of the SOPA allows for a claimant to withdraw an application and make a new adjudication application, if the adjudicator accepts the application but then “fails to determine the application within the time allowed”. The claimant must withdraw and make the new application within five business days after it is entitled to withdraw the previous adjudication application.

This may occur where the adjudicator has made a jurisdictional error in failing to determine the application.

If the original decision is decided by a court to be valid (because there was no jurisdictional error), then the second application is wasted. However, if the original decision is declared void, then the second application may still be valid.

Conclusion

It pays to be aware of when reference dates arise, and when take out notices can and should be served. Principals concerned to issue effective take out notices should be mindful of existing reference dates which have or may accrue before that notice.

Claimants should be keenly aware of the existence of any jurisdictional error on the part of adjudicators. Such error may allow them to re-lodge an adjudication application.

 

 

NCC 2019 Amendment 1: Changes starting on 1 July 2020

In response to the recommendations of the Shergold Wier Building Confidence Report, the Australian Building Codes Board (ABCB) and the Building Ministers’ Forum have undertaken an out of cycle amendment to the National Construction Code (NCC). While the NCC was not due for review until 2022, the amendment known as “NCC 2019 Amendment 1” will be adopted by all Australian jurisdictions on 1 July 2020.

The NCC is a performance-based code containing technical standards for the design, construction and performance of buildings as well as for plumbing work and drainage systems. It is published and maintained by the ABCB and adopted by each Australian jurisdiction through its own legislation. For example, in NSW the NCC is given effect by the Environmental Planning and Assessment Act 1979 (NSW), the Plumbing and Drainage Act 2011 (NSW) and subordinate legislation.

The aim of the NCC is to create a uniform set of technical standards that apply to all Australian jurisdictions. However, as identified in the Shergold Wier Building Confidence Report, there have been a number of systematic issues with the implementation and enforcement of the NCC which has prompted NCC 2019 Amendment 1.

What will change?

Following a period of key stakeholder consultation last year, NCC 2019 Amendment 1 will introduce the following changes:

  • a new provision regarding egress from early childhood centres (NCC Volume One);
  • clarification of the concession that permits the use of timber framing for low-rise Class 2 and 3 buildings (NCC Volume One);
  • clarification that anti-ponding board requirements only apply to roofs where sarking is installed (NCC Volume Two);
  • an update to the Governing Requirements for all Volumes to require labelling of aluminium composite panels in accordance with SA Technical Specification 5344; and
  • correction of minor errors, including the correction of typographical errors and errors in diagrams.

In addition to the above, the ABCB announced last month that NCC 2019 Amendment 1 will also include a provision mandating the process for developing Performance Solutions. This process is based on the ABCB’s existing Development of Performance Solution Guideline and requires that the process for documenting Performance Solutions be commensurate with the complexity and risk of the design.

Unlike the other amendments, this amendment will not commence until 1 July 2021. However, as the process is included in NCC 2019 Amendment 1 there is plenty of time for industry participants to prepare necessary documentation to encompass the process for Performance Solutions prior to the amendment taking effect next year.

Other changes expected

It was also proposed that NCC 2019 Amendment 1 would include the new defined term of “building complexity”. The draft definition proposes a risk-based system from levels 0 to 5 for classifying complex buildings, which assists to identify buildings where additional regulatory oversight is needed during the design, construction and certification processes.

 

The ABCB announced last month that this new definition would not be included in NCC 2019 Amendment 1, however it has been published on their website with a six month consultation period for comments and feedback.

A copy of the preview of NCC 2019 Amendment 1 is available on the ABCB website via the NCC Suite.

If you or someone you may know is in need of advice regarding NCC 2019 Amendment 1 or the NCC generally, please contact our office by phoning (02) 9248 3450 or by email at info@bradburylegal.com.au.