Lumina BPO Pty Ltd v Cocoon Data Technologies Pty Ltd [2026] FCA 116

This was a debt recovery dispute arising out of a common modern business structure. Lumina supplied outsourced accounting and taxation services to a technology business that operated through several related companies. One company, Cocoon Data Australia, handled payroll, expenses and administration for the Australian group. Other companies in the structure carried on the operating business or sat above it in the ownership chain.

That setup worked while invoices were being paid. The problem emerged when the Australian group fell into arrears, Cocoon Data Australia entered voluntary administration, and Lumina received only a partial return under a deed of company arrangement. Lumina then looked beyond the administration entity and sued the other Australian group companies, saying they were also parties to the services contract and therefore also liable for the unpaid fees.

The dispute was not about whether Lumina had done the work. The judgment says the existence of a contract was not in issue. The real fight was over party identity. Had Lumina contracted only with Cocoon Data Australia, the treasury and administration vehicle? Or had it contracted with all of the companies included in the defined Australian client group under the engagement letter?

The judgment gives a clear picture of the group structure. Cocoon Data Technologies was the ultimate holding company. Cocoon Data Holdings was its wholly owned subsidiary and the main Australian operating entity. Cocoon Data was another wholly owned subsidiary. Cocoon Data Australia was also a wholly owned subsidiary of Cocoon Data Holdings and acted as the employment, treasury and administration entity. It channelled payments for various services but did not itself engage in income-generating activities.

Lumina had started working with the Cocoon companies in about August 2019 under an earlier proposal. In August 2020, Lumina sent three new engagement letters to govern future work. One was for the Australian companies, one for the UK company and one for the US company. The Australian engagement letter was the key document in the case.

That letter was directed to the provision of services to the “Cocoon Data Group”. The Court said that term was defined in the contract to include Cocoon Data Australia and the three corporate respondents. The Court also made an important clarification: the phrase “Cocoon Data Group” was not used consistently in the evidence, so for the purposes of the reasons the Court used the contractual definition. That distinction matters for business readers. A label used loosely in emails or affidavits is not necessarily the same as a defined term in the contract. When a dispute arises, the contractual definition can carry far more weight.

The Australian engagement letter also incorporated Lumina’s terms of trade. One express term, which the parties accepted, was that where there was more than one client, each client was jointly and severally liable for Lumina’s professional fees and expenses, whether or not each client equally benefited from the services. That clause became central once Lumina argued that multiple companies were clients under the contract.

The letter could be accepted in more than one way, including by giving instructions or by signing and returning it. Mr Telford electronically signed the engagement letters on 26 October 2021, although Lumina had already been providing services during the 14 months after the letters were sent. The judgment notes that the written offer could be accepted by instructions, but the instructions themselves were not in evidence. That is one reason the Court had to focus carefully on the written terms and the objective surrounding circumstances.

The legal issue was narrow but commercially significant. The Court had to identify the parties to the contract formed by acceptance of the Australian engagement letter. The doctrine of privity meant that only a party to the contract could generally sue or be sued on it. So Lumina had to prove that the respondents were parties, not merely companies that benefited from services arranged through another group entity.

The judgment explains that this was an objective construction exercise. The Court asked what a reasonable business person would understand from the contractual text, read in light of the surrounding circumstances known to the parties and the commercial purpose of the arrangement. The Court also emphasised the primacy of the text in a written contract. Surrounding circumstances can assist interpretation, but they cannot be used to contradict clear contractual language.

The respondents argued that Cocoon Data Australia was the sole counterparty. Their position was that Lumina may have been obliged to provide services that benefited the wider group, but the payment obligation sat only with Cocoon Data Australia. They also argued that Cocoon Data Australia had no continuing liability after the DOCA was fully effectuated.

Lumina argued that the contract was with each company in the defined Cocoon Data Group. On that view, the administration company was one client among several, and the joint and several liability clause meant each of the corporate respondents could be pursued for the unpaid debt after crediting the dividend received under the DOCA.

The judgment also notes a point that often matters in practice. Questions about party identity can sit at the intersection of contract formation and contract construction. Here, because the contract was embodied in the written engagement letter and its incorporated terms, the Court treated the issue through the lens of objective construction of the written contract, informed by the factual matrix.

Cheeseman J held that each of the corporate respondents, together with Cocoon Data Australia, were counterparties to the contract. The Court therefore rejected the respondents’ argument that Cocoon Data Australia alone had contracted with Lumina.

Because it was common ground that the contract expressly provided that where there was more than one client, each client was jointly and severally liable for Lumina’s professional fees and expenses, the finding on party identity had a direct financial consequence. Each of the corporate respondents was liable for the debt due under the contract.

The Court ordered judgment against the corporate respondents in the amount of $269,865.56 plus pre-judgment interest. The reasons explain that Lumina’s original claim was for $307,738.63, less the dividend of $37,873.07 received in the DOCA of Cocoon Data Australia, with interest added. The orders also required the parties to confer and provide proposed short minutes on costs, including in relation to Mr Telford’s costs, and provided a timetable for short written submissions if costs were not agreed.

The judgment also makes clear that the claim against Mr Telford personally was not part of the contract claim pressed at hearing. When the matter came on for hearing, the Court dismissed the claim against him and reserved the question of his costs. The alternative claims based on promissory estoppel and misleading or deceptive conduct were not ultimately pressed. So the decision stands as a contract case about identifying the parties to a written engagement letter in a corporate group setting.

For suppliers, the case is a reminder that recovery rights often turn on drafting discipline. If you intend to contract with several entities in a group, say so clearly. Define the client group precisely. State whether liability is joint and several. Make sure the signatory has authority for each entity. Keep records showing how the offer was accepted, especially if your terms allow acceptance by conduct or instructions rather than signature alone.

For customers, the case is a warning against treating group engagement letters as harmless administration. If a document defines the client as a group of companies and includes joint and several liability wording, signing it may expose multiple entities to the supplier’s claim. That can cut across internal assumptions that one treasury or payroll company will be the only payer.

The case also shows that invoicing practice is not everything. Here, invoices were issued to Cocoon Data Australia, and that company was the payroll, treasury and administration vehicle. Even so, the Court held that the wider Australian group entities were also counterparties. In other words, the invoice addressee did not control the legal analysis where the contract pointed the other way.

Another practical point is the effect of insolvency arrangements. Participating in an administration or DOCA for one group entity does not necessarily end a supplier’s rights against other entities if they are also parties to the contract. The dividend received under the DOCA reduced the debt, but it did not prevent Lumina from pursuing the remaining balance against the other contracting parties.

Finally, this case highlights the danger of inconsistent terminology. The Court expressly noted that the phrase “Cocoon Data Group” was used inconsistently in the evidence, but the contract itself contained a defined meaning. Businesses should avoid relying on loose shorthand such as “the group”, “associated entities” or “our Australian business” unless the contract spells out exactly which legal entities those words cover.

A frequent question is whether a supplier should contract with the operating entity, the treasury entity, or all relevant entities. There is no single answer for every business, but this case shows the importance of making a deliberate choice. If you want broader recourse, the contract needs to say so clearly. If you want liability limited to one entity, that also needs to be stated clearly and reflected in the rest of the paperwork.

Another common question is whether later conduct can change the identity of the parties. The judgment records that post-contractual matters may have limited relevance, especially where the written offer could be accepted by giving instructions and those instructions are not in evidence. But the Court's reasoning, as far as the published reasons show, remained anchored in the written engagement letter and objective context rather than subjective assumptions.

Businesses also often ask whether a director or CEO signing a document personally becomes liable. This case does not support that proposition on the facts stated. The contract claim pressed at hearing was against the corporate respondents, not Mr Telford personally, and the claim against him was dismissed when the matter came on for hearing.

The broader message is simple. Group structures can be commercially efficient, but they create legal complexity if contracts are drafted casually. The more entities involved, the more important it is to identify exactly who is receiving services, who is promising to pay, and whether those obligations are shared.

The judgment was delivered on 18 February 2026 in the Federal Court of Australia. The hearing took place on 6 May 2025. The published orders entered judgment against the corporate respondents and set a process for dealing with costs on the papers if not agreed. The reasons also record the earlier administration and DOCA of Cocoon Data Australia, which formed part of the commercial background to the claim.

This page explains the decision as a practical contract case. It should not be read as a complete statement of all issues that can arise in insolvency, group company liability or authority to contract.