Can You Use Held Retentions to Defeat a QLD Security for Costs Application?

John Merlo
8 hours ago
12 min read

Key Takeaways

Under rule 670 of the Uniform Civil Procedure Rules 1999 (Qld) ("UCPR"), a court may order a civil contracting company to provide security for a developer's legal costs if there is reason to believe the contractor cannot pay them.
If the principal is still holding your unconditional bank guarantees or project retentions, they may already be secured — which lets you ask the court why they need cash on top of security they can already reach.
A court is likely to consider whether your financial distress was directly caused by the developer's failure to pay the disputed progress claims, leveraging rule 672 of the UCPR.
Failing to provide ordered security typically results in an automatic stay of your proceeding under rule 674 of the UCPR and may ultimately lead to dismissal.

You have just filed a claim in the Supreme Court to recover a major progress claim from a special purpose vehicle (SPV) developer, but instead of a defence, you are served with an interlocutory application demanding a massive sum be paid into court before you can take another step. The developer is attempting to use the very financial distress they caused your business as a tactical weapon to price you out of the litigation. This guide explains how Queensland civil contractors can counter this aggressive procedural move using existing project assets—like held retentions and unconditional bank guarantees—to satisfy security requirements and keep their claim alive. As you will see, if the principal is still sitting on security under your contract, that fact alone can put them on the back foot.

The Tactical Threat: How Developers Use UCPR Rule 670 to Stifle Contractor Claims

You are now looking at a formal application seeking to halt your lawsuit until you deposit hundreds of thousands of dollars into the court's trust account. This section breaks down the specific legal mechanisms the developer is using to stall your claim, distinguishing the financial prerequisites they must prove from the court's actual discretionary power to refuse their demand.

Distinguishing the Statutory Threshold from the Court's Broad Discretion

When defending these applications, keep two questions apart: first, can the developer show your company probably cannot pay their costs; and second, even if they can, should the court exercise its discretion to order security at all. A defendant in Queensland can apply for a court order requiring the plaintiff to provide security for the defendant's legal costs, as governed by r 670 of the UCPR. However, simply proving there is reason to believe your contracting company could not pay a costs order does not trigger a mandatory order.

Under Queensland law, a defendant establishing that there is reason to believe a civil contractor will be unable to pay the defendant's costs if ordered to do so only crosses a procedural threshold; it does not eliminate the court's discretion to refuse a security for costs order.

The court retains a broad discretion to refuse the developer's application based on fairness and conduct. Experienced Queensland building and construction lawyers often focus on leveraging this discretion to defeat the application. This works differently in tribunals like the Queensland Civil and Administrative Tribunal, where the formal security for costs rules do not apply in the same way.

Activating the Prerequisite Against a Corporate Plaintiff

To pass the initial procedural hurdle, the developer is likely to use your financial statements or records of delayed payments to argue that there is reason to believe your contracting company cannot pay their costs if you lose. A prerequisite for ordering a corporate plaintiff to provide security for costs is that there is reason to believe it cannot pay the defendant's costs if unsuccessful, which is the test applied under Uniform Civil Procedure Rules 1999 (Qld), rule 671.

Furthermore, under federal corporate law, a court may require a corporate plaintiff to provide sufficient security for costs if credible evidence shows they will likely be unable to pay a successful defendant's costs, pursuant to the Corporations Act 2001 (Cth), section 1335. Courts can closely scrutinise this financial evidence, and whether the developer clears this threshold usually turns on what your financial disclosures actually show at the interlocutory hearing.

Immediate Proceeding Stays and Dismissal Risks Under UCPR Rule 674

Miss an order for security, and the consequences are strict. If a plaintiff fails to provide the ordered security for costs, their proceeding is automatically stayed and may ultimately be dismissed under Uniform Civil Procedure Rules 1999 (Qld), r 674.

An order does not strike out the claim on day one. Instead, it formally stays the proceeding, preventing you from taking any further steps to advance the litigation until the required security is deposited into court. The matter is only dismissed if the plaintiff fails to comply within the allowed timeframe, requiring a subsequent procedural application by the defendant to terminate the lawsuit. The better strategy, of course, is to avoid an unmet order in the first place — which starts with taking stock of the security you can already put on the table.

What Security for Costs Can You Offer Before Paying Cash Into Court?

Before you consider liquidating physical assets or abandoning a perfectly valid claim, you need to inventory the project-specific assets you already hold. This section outlines how your Contracts Administrator can strategically propose existing bank guarantees, held retentions, or related claims to satisfy the court's security requirements without draining your operating capital.

Repurposing Unconditional Bank Guarantees as Evidence of Security

When a developer demands liquid cash paid into court, civil contractors often overlook the substantial funds the developer already holds under the construction contract. You can point to existing cash retentions or unconditional bank guarantees as evidence that the developer is already secured against potential costs orders. Courts may view these held funds as sufficient alternative security, negating the need for an additional cash payment.

In Queensland construction litigation, an existing unconditional bank guarantee held by the principal can often be leveraged as evidence of sufficient security for costs.

The tactical point most contractors miss is the double dip. Under a standard form like AS 4000, the principal typically holds two undertakings totalling five per cent of the contract sum, often released in halves — the first at practical completion and the balance following the issue of the final certificate, which ordinarily occurs after the defects liability period has expired. If the principal is still sitting on those undertakings while asking the court for cash security, you should put that squarely in front of the judge.

The undertakings are payable on demand and are not tied up in the merits of your progress claim dispute. That makes them a genuine, liquid source the principal can already reach. A court weighing discretion is entitled to ask why a defendant holding on-demand security worth six figures needs a further cash payment into court to feel protected.

Frame it as arithmetic, not rhetoric. Tender the contract, identify the clause governing the security, confirm the guarantees have not been called or released, and quantify what the principal holds against the costs sum they are claiming. Where the held security comfortably exceeds a realistic costs estimate, the "double protection" argument becomes hard for the principal to answer.

Two practical cautions. First, the guarantees secure the principal's contractual entitlements, not costs, so expect the principal to argue they cannot be appropriated to a costs order — your answer is that they are evidence of the principal's existing protected position, not a substitute payment. Second, if the principal has already made a bona fide call on the security, or the defects liability period has closed and the undertakings have been returned, this argument weakens considerably, so confirm the current status before you run it.

A developer who ignores security they already hold and presses for cash regardless can expect a sceptical reception from the bench.

Valuing Disputed Progress Claims and BIF Act Determinations as Defensive Assets

Beyond held cash and guarantees, your pending contractual entitlements can be framed as active defensive assets. Unadjudicated payment claims or favourable determinations under the Building Industry Fairness (Security of Payment) Act 2017 (Qld) can serve as evidence to prove your company's net financial position, thereby weakening the developer's argument that you are impecunious. Courts may consider these active payment rights when evaluating the overall financial strength of your business.

Securing guidance from a Queensland litigation lawyer can help you map out how these pending recoveries offset the developer’s claims. Asserting your Queensland security of payment rights effectively may provide strong evidence that your commercial position is significantly stronger than the developer alleges.

Overcoming the Stifling Argument Against Undercapitalised SPV Developers

Many civil contractors find themselves suing special purpose vehicle (SPV) developers who are highly leveraged, raising the argument that an oppressive security order would "stifle" the contractor's genuine claim — a factor the court is expressly permitted to weigh under Uniform Civil Procedure Rules 1999 (Qld), r 672(h). However, successfully arguing that an application will stifle the litigation is likely to require invasive financial disclosure. Courts typically expect that to successfully raise the stifling defence, the directors or shareholders behind the civil contracting firm must prove that they too lack the personal means to fund the security.

In practice, courts treat the stifling argument with a degree of scepticism, because it is so easily asserted and so rarely evidenced. Expect the developer's counsel to demand that every director and substantial shareholder swear affidavits disclosing personal assets, borrowing capacity, and access to related-entity funds — and to press the point in cross-examination if the disclosure looks thin.

The burden is on those standing behind the company to show they cannot fund security, not merely that they would prefer not to. A director who owns a house with equity, or who has drawn dividends in recent years, will struggle to run this argument credibly without addressing why those resources cannot be tapped. Half-hearted disclosure that leaves obvious questions open tends to sink the stifling defence faster than no disclosure at all, so if you raise it, commit to it fully.

You cannot simply claim the corporate entity is broke; you may be required to open your personal financial records to show that you cannot inject the necessary funds to keep the claim alive. Advice from a Queensland commercial lawyer can help you navigate this complex disclosure process, particularly where the party on the other side is a broke SPV pressing you for security.

Turning It Around: The "Defendant Caused Our Impecuniosity" Defence

It is deeply frustrating when the very developer withholding your $1.2 million progress claim argues that you are too broke to sue them. This section explores how you can use the developer's own breaches against them by proving their failure to pay directly caused your financial distress, leveraging the discretionary defences available under the rules.

Raising the "Defendant Caused the Financial Distress" Defence Under UCPR Rule 672

When defending these applications, you can argue that the developer should not benefit from the financial damage caused by their own breach of contract. The court has discretion to consider factors such as the financial means of those backing the lawsuit and the merits of the case when deciding on a security for costs order, as outlined in the Uniform Civil Procedure Rules 1999 (Qld), r 672.

This discretionary defence turns the developer's primary argument on its head, using their non-payment as the evidentiary basis to refuse the security order altogether.

Evidentiary Requirements to Link Unpaid Civil Works to Company Impecuniosity

It is not enough to simply claim the developer owes you money; you must trace the precise cash flow impact of the withheld variations or progress claims directly to your current inability to fund the litigation. Your Contracts Administrator and external accountants must assemble financial records that clearly isolate the developer's non-payment as the trigger for your liquidity constraints.

The defence lives or dies on the timeline. Courts are persuaded by evidence that shows the business trading normally before the non-payment, then falling into distress in step with the withheld sums — not by a general assertion that money is tight.

Build the chronology from the primary documents. Line up the payment claim and payment schedule against dated bank statements and management accounts from the same period, so the drop in the cash position can be read against the exact date the money should have landed. A month-by-month cash flow comparison spanning the twelve months either side of the non-payment usually tells the story more clearly than any narrative affidavit.

Then close off the alternative explanations. The developer will argue your distress came from over-trading, a bad contract elsewhere, tax debt, or poor management, so put the aged creditors ledger, ATO position, and any other significant disputes in front of the court and address them directly. Isolating the disputed sum as the material trigger — rather than one of several problems — is what separates a defence that holds from one that gets waved away.

An accountant's report that traces the funds and expresses a view on causation carries real weight here, provided it is grounded in the source documents rather than instructions. Where the withheld amount is large relative to your turnover, the causal link tends to speak for itself; where it is modest, expect to work much harder to prove it was the difference between solvency and distress.

Defeating Delayed Security Applications That Prejudice the Contractor

When a developer holds off on their Uniform Civil Procedure Rules 1999 (Qld), r 670 application until right before trial, their tactical delay can become your strongest procedural advantage. In exercising its discretion, the court may expressly consider whether such an order would be oppressive under Uniform Civil Procedure Rules 1999 (Qld), r 672(g), and may also weigh the prejudice caused by delay as part of its general discretion. Queensland Courts may view extreme delay as inherently prejudicial to the contractor who has already invested heavily in the proceeding, which can be fatal to the developer's application. To leverage this delay, civil contractors should typically document the following factors:

Calculate the exact legal costs your company has already sunk into the litigation prior to the developer filing their security application.
Identify any strategic milestones the developer allowed to pass (such as disclosure or mediation) without formally raising the issue of security.
Formulate an argument that granting the order now may unfairly ambush your trial preparation and is likely to operate as a tactical weapon rather than a genuine protective measure.
Assess whether the developer had early access to your financial records that could have prompted a much earlier application.

Conclusion

You commenced proceedings against the developer to recover a $1.2 million progress claim, and they responded with a tactical demand for hundreds of thousands of dollars in upfront security. While the prospect of paying liquid cash into the court's trust account initially seemed like an insurmountable barrier, you now understand that the developer’s application is merely a procedural hurdle, not an unchallengeable death sentence for your lawsuit. By distinguishing the mandatory financial prerequisites from the court's broad discretionary power, you can begin to build a robust defence against their attempt to stifle your claim.

Instead of scrambling to liquidate physical assets, your Contracts Administrator can start with the project-specific assets already in play on the job. By repurposing existing unconditional bank guarantees or held retentions, you may provide the court with sufficient evidence of alternative security, negating the need for a cash deposit. More importantly, you can weaponise the developer’s own breaches against them. By forensic tracing, you can argue that your financial distress was caused by their failure to pay the disputed contract sums, directly invoking the discretionary protections under the Uniform Civil Procedure Rules.

Your immediate next step is to inventory all unconditional bank guarantees and project retentions currently held by the principal across your civil works portfolio. Assemble your historical cash flow statements alongside the relevant unpaid payment schedules, and prepare the specific evidentiary timeline required to prove the developer caused your liquidity constraints. Then seek independent legal advice to review your contract's security clause and map your causation timeline before the application is heard — the two moves most likely to shift the outcome in your favour.

FAQs

What is a security for costs application in Queensland litigation?

A security for costs application is a procedural request by a defendant for a court order requiring the plaintiff to provide financial security for the defendant's legal costs. Under UCPR rule 670, a court may order this security if it considers it appropriate. If the order is granted and not met, the proceeding is stayed.

Can a developer force my civil contracting company to pay cash into court if we are struggling financially?

A developer can apply for an order, but establishing that there is reason to believe your company could not pay a costs order only crosses a procedural threshold; it does not eliminate the court's discretion to refuse the order. Under federal corporate law and UCPR rule 671, the court may require security if there is reason to believe the corporation cannot pay the costs. However, courts may consider discretionary factors under UCPR rule 672 before mandating any payment

What happens if my company cannot pay the court-ordered security for costs?

If a plaintiff fails to provide the ordered security for costs, their proceeding is automatically stayed under UCPR rule 674. This stay halts your ability to take further steps in the litigation. If the security remains unpaid for an extended period, the court may ultimately dismiss your claim entirely.

Can we use our existing bank guarantees to satisfy a security for costs order?

Yes, an existing unconditional bank guarantee held by the principal can often be leveraged as evidence of sufficient security for costs. Courts may view these held funds as adequate alternative security. This strategy can often negate the need for an additional cash payment into the court's trust account.

How do we defend against a security for costs order if the developer's non-payment caused our financial distress?

Under UCPR rule 672, a Queensland court may refuse a security for costs order if the civil contractor can demonstrate their financial distress was caused by the developer’s failure to pay the disputed contract sums. You must provide clear financial evidence linking their specific non-payment to your current lack of liquidity. This discretionary defence often relies on historical cash flow statements and unpaid progress claims.

What if the developer waits until just before trial to file their security for costs application?

Courts may view extreme delay in filing an application as inherently prejudicial to the contractor who has already invested heavily in the proceeding. Such tactical delays can be fatal to the developer's application. You should document the legal costs already sunk into the litigation to argue that the delayed application is oppressive and designed to ambush your trial preparation.

This guide is for informational purposes only and does not constitute legal advice. For advice tailored to your specific circumstances, please contact Merlo Law