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

Claim offer
Selected cases

Federal Court of Australia · [2025] FCA 1212

Norden Holdings Pty Ltd (Trustee) v Martens Investments Pty Ltd (Trustee), in the matter of Amazonia IP Holdings Pty Ltd (No 6)

The court found missing documents, incomplete production, unauthorised redactions and failure to provide general ledgers.

Federal Court of Australia

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

  • Read this case as a warning about court process, not as a general statement that privacy lets businesses withhold records.
  • In Norden Holdings Pty Ltd (Trustee) v Martens Investments Pty Ltd (Trustee), in the matter of Amazonia IP Holdings Pty Ltd (No 6) [2025] FCA 1212, the Federal Court...

Use this to check

  • Missing documents in categories already covered by earlier court orders
  • Late production during the hearing process
  • Redactions made without court approval

Decision snapshot

  1. 1

    What happened

    • The case arose within ongoing Federal Court proceedings involving Amazonia-related companies.
    • The broader dispute was not a standalone privacy claim.
    • Earlier decisions in the matter, referred to in these reasons, show the proceeding involved claims of oppressive conduct concerning an alleged transfer of the applicant’s stake in the fourth and fifth respondents to the first respondent.
    • Because the case required valuation evidence for final determination, a joint expert valuer had been appointed and needed financial material from the relevant companies.
  2. 2

    What the court had to decide

    • The court had to decide whether, after admitted and established non-compliance with earlier production orders, it should exercise its broad procedural powers to grant direct access to the relevant financial management systems and make further orders for specific financial documents.
    • The issue was not whether the applicant was generally entitled to the records, because earlier orders had already required production.
  3. 3

    What the court decided

    • The application was allowed in part.
    • Wheatley J held that most of the specific document types sought under the May orders and the expert requests had not been provided, and that the June 2024 orders had not been complied with because the required general ledgers were not produced.
    • The court decided that direct access to the relevant systems should be granted so the applicant could satisfy itself about documents that should already have been produced.

Practical impact

Practical read

  • Read this case as a warning about court process, not as a general statement that privacy lets businesses withhold records.
  • The court treated the real problem as non-compliance with existing orders.
  • Redacted documents were non-compliant because there was no order permitting redactions.
  • Incomplete emails without attachments were non-compliant.

Useful next steps

  • Missing documents in categories already covered by earlier court orders
  • Late production during the hearing process
  • Redactions made without court approval
  • Incomplete production, including emails without attachments
  • Substitute accounting material, including a trial balance where general ledgers were required

The story

This decision sits inside a larger corporations dispute involving Amazonia-related entities. The broader proceeding concerned claims of oppressive conduct linked to an alleged transfer of the applicant's stake in certain respondent companies. The court had already made earlier orders requiring financial documents to be produced, and a joint expert valuer had been appointed for the final determination of the case.

By the time this application came before Wheatley J, the immediate issue was no longer whether the applicant was entitled to those records in principle. Earlier orders had already answered that. The real issue was whether the respondents had actually complied. The applicant said they had not, and asked for stronger procedural relief: direct access to the companies' financial management systems and further orders requiring specific missing documents to be produced.

What was actually in dispute

The applicant grouped the disputed material into three categories. First were documents required by orders made on 7 May 2025. Second were documents requested by the joint expert and also required by those May orders. Third were documents required by orders made on 28 June 2024, including general ledgers.

The respondents had denied non-compliance in written submissions, but at the hearing they accepted there had been some non-compliance with the May orders and the expert requests. They argued they had substantially complied and said direct access to their systems would be disproportionate. They also relied on a further tranche of documents said to have been provided shortly before the resumed hearing.

The extract shows several recurring problems. Some documents were produced late. Some were incomplete. Some emails were produced without attachments. Some documents were redacted even though there was no court order allowing redactions. In relation to the June 2024 orders, the respondents accepted there was no document before the court that purported to be a general ledger.

Practical sense check

  • Missing documents in categories already covered by earlier court orders
  • Late production during the hearing process
  • Redactions made without court approval
  • Incomplete production, including emails without attachments
  • Substitute accounting material, including a trial balance where general ledgers were required
  • No workable plan explaining how the remaining non-compliance would be fixed

Documents and conduct the court focused on

The reasons are useful because they show the court looking closely at practical document categories rather than speaking only in generalities. The extract records findings of non-compliance across multiple items in Annexure A to the May orders.

For balance sheets, the court was not satisfied the required years had been properly covered and noted the respondents could not assure the court of compliance. For fixed asset registers or depreciation schedules, the respondents accepted the material had not been provided in accordance with the orders and that some required periods were still missing. For aged debtors and aged creditors, the respondents accepted the documents remained redacted and incomplete.

The same pattern appeared for stock listings and inventory reports, where redactions remained and required periods had not all been produced.

The court also dealt with sales or income reports by customer and by product. In one category, the respondents accepted the documents provided were redacted and that some years were missing. In another, they accepted some required years had not been provided at all. For owner and associate remuneration material, only employment contracts had been produced, not the broader payment and benefits information required by the order.

For bank reporting documents, the court accepted that emails without attachments were incomplete and therefore non-compliant.

One category was treated differently. For sales or income reports by region or country, the respondents submitted, without clear supporting evidence, that reports of that kind were not produced. The court did not make a further order on that item at that time, but noted that direct access to the systems could allow the applicant to inspect whether documents answering that description existed.

What the court had to decide

The legal issue was procedural. The court had to decide whether, given the admitted and established non-compliance with earlier orders, it should use its broad powers to grant direct access to the relevant financial systems and make further production orders. The reasons refer to the Federal Court of Australia Act 1976 (Cth), including sections 23, 37P, 37M and 37N, and to the court's obligation to manage proceedings in a way that promotes the just, quick, inexpensive and efficient resolution of disputes.

The respondents argued that direct access should be treated as subject to a very high threshold. The court rejected that characterisation. The question was not whether the court had power. It did. The real question was whether the discretion should be exercised in the circumstances of this case, where there had been default under previous orders, delay, and no acceptable proposal for future compliance.

What the court decided

Wheatley J held that most of the specific document types sought by the applicant under the May orders and the expert requests had not been provided. The court also held that the June 2024 orders had not been complied with because the required general ledgers had not been produced. The only document before the court in purported compliance was, in substance, a trial balance, which was not enough.

The court decided that direct access should be granted because it would allow the applicant to satisfy itself in relation to documents that should already have been produced under earlier orders. The reasons given included non-compliance with previous court orders, the oppression context of the proceeding, delay, the need to avoid further possible delay and increased costs, and the respondents' failure to offer any reasonable or acceptable proposal or plan to comply.

The application was allowed in part. The court said it would hear further from the parties on the appropriate form of orders and separately on costs. That means the reasons establish the court's conclusions and intended relief, but the final entered wording of the orders is not set out here.

Redactions, privacy and confidentiality

The privacy angle in this case is narrower than the topic label might suggest. The respondents relied on privacy concerns and possible disclosure to competitors to explain why some documents had been redacted. The court did not treat that as a free-standing right to alter production. Instead, it treated the issue as one of compliance with court orders.

The reasons are clear on the procedural point. There was no order permitting redactions. There was no application seeking permission to provide documents in redacted form. There was also no application to vary or amend the earlier orders to allow redactions. Because of that, the respondents accepted that redacted production was not compliant.

That is the practical lesson for businesses. If records are sensitive, commercially confidential or contain private information, the answer is not self-help redaction after the order is made. The answer is to seek the court's approval for redactions, confidentiality protections or a variation to the production regime before producing altered documents.

How businesses should read it

For business owners, this case is really about systems, people and process. Courts expect ordered records to be produced in the form required. If your accounting platform can generate reports, the court may expect those reports to be generated even if they were not previously run. The reasons expressly reject the idea that a party can avoid compliance simply by saying it is not required to create records, where the order required documents to be produced, generated or created and produced.

The case also shows the risk of vague internal responsibility. There was argument about whether the sixth respondent, said to be a contractor CFO, was the proper person against whom direct access orders should be made. For a business, that is a warning to know in advance who controls system access, who can export ledgers and reports, and who can gather attachments and supporting records quickly if litigation escalates.

Another practical point is that substantial compliance may not be enough if the missing pieces matter. Here, the respondents argued they had substantially complied, but the court still found non-compliance serious enough to justify direct access in part because the missing records were needed for expert valuation and the final hearing, and because there was no acceptable plan to remedy the defaults.

Practical steps to avoid the same problem

Businesses can reduce the risk of this kind of procedural escalation by treating document production as an operational project, not just a legal task. The court's criticism in this case centred on missing records, substitute records, redactions without approval, incomplete emails, delay and the absence of a credible remediation plan. Those are all issues that can often be improved with better internal preparation.

If your business is in litigation, identify one responsible person to coordinate production across accounting systems, email, cloud storage and banking records. Make sure that person understands the difference between a general ledger, a trial balance, a stock report, a debtor schedule and a customer sales report. If a report can be generated from software, test that early. If attachments are stored separately from emails, map that process early too.

And if there is a genuine confidentiality concern, raise it with lawyers before production occurs so the court can be asked for appropriate protections.

Practical sense check

  • Map every system that holds relevant financial records, including accounting, inventory, banking and email systems
  • Identify who has administrator or export rights for each system
  • Check early whether required reports can be generated for each ordered period
  • Keep general ledgers and trial balances distinct and do not assume one substitutes for the other
  • Produce complete emails with attachments where the order requires the full document
  • Do not redact ordered documents unless the court has permitted it
  • If compliance will be delayed or difficult, prepare a concrete plan and seek directions promptly
  • Track expert requests separately and make sure they are matched against the court orders

Dates and status

The judgment was delivered on 17 September 2025 and the reasons were published on 2 October 2025. The hearing dates noted in the reasons were 5 and 15 September 2025. The court ordered the parties to submit short minutes of orders by 4 pm on 18 September 2025 in accordance with the reasons.

The decision records that the application was allowed in part and that the court would hear further from the parties on the precise form of orders and separately on costs. This page therefore explains the court's reasoning and intended procedural outcome, but does not state any final costs order or final entered wording beyond what is set out in the published reasons.

Source notes

This page is based on the Federal Court of Australia decision in Norden Holdings Pty Ltd (Trustee) v Martens Investments Pty Ltd (Trustee), in the matter of Amazonia IP Holdings Pty Ltd (No 6) [2025] FCA 1212. It is a practice and procedure decision about direct access to systems and compliance with earlier production orders in ongoing corporations litigation.

It should be read as a procedural case note for business readers. It does not attempt to restate the full underlying oppression dispute or any final orders that may have been settled after short minutes were submitted.

Related topics

How Sprintlaw can help