EOFY Sale · Save up to $750 off your legals · Ends 30 June

Claim offer
Selected cases

Federal Court of Australia · [2026] FCA 116

Lumina BPO v Cocoon Data

A Federal Court supplier-payment case about outsourced finance services, group-company liability and unpaid invoices after an administration.

Federal Court of Australia18 Feb 2026

Plain-English explainers, not legal advice. Check the linked official source before you rely on a specific section, and get advice for your situation.

Get legal help

Start here

Quick read

  • Group service contracts should identify every company that is actually on the hook for fees.
  • A Federal Court supplier-payment case about outsourced finance services, group-company liability and unpaid invoices after an administration.

Use this to check

  • Group-company engagements should name every liable entity.
  • A joint and several liability clause can matter when one group company enters administration.
  • Suppliers should not rely only on trading names or informal group language.

Decision snapshot

  1. 1

    What happened

    • Lumina BPO provided outsourced accounting, tax, payroll, treasury, corporate governance and CFO-style services to the Cocoon Data group.
    • Cocoon Data Australia was the payroll, expense and administration entity, but the broader group included Cocoon Data Technologies, Cocoon Data Holdings and Cocoon Data.
    • When Cocoon Data Australia went into voluntary administration in October 2023, Lumina lodged a proof of debt for unpaid invoices.
    • It received a DOCA dividend of $37,873.07, but a large balance remained unpaid.
  2. 2

    What the court had to decide

    • The Federal Court had to decide whether the services contract was only between Lumina and Cocoon Data Australia, or whether the other Cocoon Data corporate respondents were also counterparties and therefore jointly and severally liable for unpaid professional fees after Cocoon Data Australia entered voluntary administration.
  3. 3

    What the court decided

    • The Court found that Cocoon Data Australia and the corporate respondents were parties to the contract.
    • It entered judgment against the corporate respondents for $269,865.56 plus pre-judgment interest, with costs to be dealt with separately.
    • Lumina's claim against Mr Telford personally was dismissed.

Practical impact

Practical read

  • Group service contracts should identify every company that is actually on the hook for fees.
  • If one company is only the payroll or administration vehicle, suppliers should not assume the wider group will be liable unless the engagement wording, authority and conduct make that clear.

Useful next steps

  • Group-company engagements should name every liable entity.
  • A joint and several liability clause can matter when one group company enters administration.
  • Suppliers should not rely only on trading names or informal group language.
  • Customer groups should decide whether the admin entity or the wider group is the contracting party.
  • Proofs of debt and DOCA dividends may not end the dispute if other entities are also liable.

Practical read

This is a supplier-payment story with a very common group-company problem. Lumina had been doing finance and accounting work across the Cocoon Data business for years. The group had several Australian companies, and one of them handled payroll, expenses and administration. When that admin company entered voluntary administration, the practical question became simple: was Lumina stuck with a dividend from that one company, or could it recover from the other group entities as well?

The Court looked closely at the engagement letter, how the group was described, who gave instructions and how the services were used. The contract included a joint and several liability term where there was more than one client. On that evidence, the Court found that Cocoon Data Australia and the corporate respondents were counterparties to the contract. That meant the other group companies could not avoid the unpaid fees by pointing to the administration of the payroll entity.

For small businesses, the lesson is to make the contracting party obvious before invoices start building up. If you are a supplier, write the engagement so it says exactly which entities are clients and who pays. If you are a group, avoid loose trading names and vague group references unless you really intend every entity to be liable.

Checks to run

Key points

  • Name each contracting entity in the engagement letter.
  • Say whether group companies are jointly and severally liable.
  • Match invoice descriptions to the entity or entities receiving the services.
  • Keep board or director authority for group-wide service engagements.
  • Get legal help before assuming a DOCA dividend is the only recovery pathway.

Key takeaways

  • Group-company engagements should name every liable entity.
  • A joint and several liability clause can matter when one group company enters administration.
  • Suppliers should not rely only on trading names or informal group language.
  • Customer groups should decide whether the admin entity or the wider group is the contracting party.
  • Proofs of debt and DOCA dividends may not end the dispute if other entities are also liable.

Related topics

How Sprintlaw can help

Update history

Case8 June 2026

Current Federal Court contract and records cases added

Six current Federal Court explainers were added for group contracts, company records, related-party money flows, restraints, creative credits and enforcement deadlines.