Remoteness of Damage in Financial Claims
Assess remoteness of damage before calculating financial loss. Compare contract and negligence rules using evidence of knowledge and consequences.
- Published
- Updated
Remoteness of damage limits which consequences of a wrong can be recovered, even where the wrong factually caused a financial loss. In contract, examine the parties’ knowledge when they contracted. In negligence, assess the relevant duty and legal scope of responsibility before treating foreseeable financial loss as recoverable.
For a commercial litigator, that means separating each alleged loss before briefing an accountant. A supported payment trail can establish what happened without establishing that the defendant must compensate every consequence.
Remoteness and Causation Are Different
Factual causation asks whether the alleged wrong caused the loss. Remoteness addresses the legal limits on recovery for consequences that have a factual connection to it.
Start with the cause of action. A contract claim, negligence claim and statutory claim can arise from the same conduct but require different legal analysis. Identify the governing law and any applicable statutory provisions before choosing the test. A contractual formulation drawn from Hadley v Baxendale is not a universal rule for Australian financial claims.
Keep four inquiries separate in the brief:
- Identify the obligation the defendant owed this claimant.
- Describe the conduct that breached that obligation.
- Explain how the breach caused the particular loss.
- Give the legal basis for extending responsibility to that consequence.
Only then settle the assumptions for quantification. The accountant can calculate separate scenarios where legal responsibility remains disputed. A larger spreadsheet does not resolve the legal boundary.
Contractual Contemplation and Known Circumstances
Contractual remoteness examines the consequences reasonably contemplated when the contract was made, using the knowledge available at that point. Ordinary circumstances and communicated special circumstances inform that inquiry.
In European Bank v Evans, paragraphs 11 to 13, the High Court explains the contractual rule as a limit on recoverable heads of damage. Its discussion distinguishes loss arising naturally from breach and loss contemplated because of the relevant circumstances. The case itself concerned an undertaking as to damages, so its outcome must be read in that context.
The majority in Elisha v Vision Australia, paragraphs 61 to 63, confirms the forward-looking assessment from contract formation. The precise damage and its exact manner of occurrence need not have been contemplated. The general type of damage and how it occurred require attention.
Consider a hypothetical supplier who knows that a machine supports ordinary trading. A delay causes lost trading income and the buyer also alleges losing an unusually profitable downstream deal. Separate the two heads. For the unusual deal, locate evidence of what the supplier knew about its dependency on timely delivery when contracting.
An email sent after the breach can describe the eventual consequence. It does not, by itself, establish knowledge at formation. Preserve negotiations and any communicated delivery dependencies beside the executed agreement.
Read exclusions and liability caps separately. A conclusion that loss falls within contractual contemplation does not answer whether an operative clause limits recovery. Avoid treating the label “consequential loss” as a substitute for interpreting the actual clause.
After identifying the recoverable heads, use expectation damages to frame the performance-position calculation. Keep that calculation distinct from deciding which consequences belong in it.
Foreseeability in Financial Negligence
Remoteness of damage in negligence requires attention to the kind of foreseeable harm and the legally relevant scope of responsibility. Foreseeability alone does not establish a duty to protect the claimant against every financial consequence.
Badenach v Calvert illustrates why the professional undertaking must be identified first. The High Court rejected a beneficiary’s negligence claim arising from will-making advice. The reasons examine the solicitor’s instructions, the duty alleged and the separate question of what would have happened with different advice.
In a hypothetical commercial matter, an accountant advises on a proposed acquisition’s tax treatment. The buyer later claims both an unexpected tax payment and losses from falling customer demand. Analyse the engagement and advice to identify the risks the accountant undertook to address. The fact that both losses followed the acquisition does not put both within that responsibility.
Then examine factual causation. Would correct advice have changed the buyer’s decision, price or transaction structure? Use contemporaneous instructions and decision records to test the answer. A claim that the buyer would have abandoned the deal needs evidence beyond the later existence of a loss.
Keep quantification separate again. A bank debit supports the payment amount. It does not establish that negligent advice caused that payment or that the adviser bears legal responsibility for it. Record the conclusion for each head under the governing jurisdiction’s negligence law.
Build the Knowledge and Loss Evidence
Build a source-linked matrix that connects each alleged consequence to the relevant knowledge and the documents supporting it. Give counsel the competing explanation beside the claimant’s account.
The following hypothetical matrix shows the distinction without calculating the full claim.
| Alleged consequence | Knowledge or responsibility evidence | Payment or loss evidence | Competing explanation |
|---|---|---|---|
| Lost ordinary trading income after machine delay | Contract and pre-contract production discussions, each with document and page reference | Sales records and statement receipts, identified by file and page | Demand fell independently of the delay |
| Lost unusual downstream deal | Email disclosing the deal before formation, with recipient and delivery dependency | Customer cancellation and any refunded deposit, with source references | Customer lacked funding regardless of delivery |
| Unexpected acquisition tax payment | Accountant’s retainer, tax advice and buyer instructions | Assessment and bank debit, with account and source page | Tax would have been payable under the alternative structure |
| Acquisition trading losses | Engagement terms and any advice on commercial performance | Trading records reconciled to receipts | Customer demand explains the decline |
Replace those document descriptions with actual bundle references. Record who received each communication and whether it preceded formation or the relevant advice. Distinguish a forecast prepared for internal use from one communicated to the defendant. Keep the forecast’s assumptions beside actual receipts so a prediction is not mistaken for a realised loss.
For large statement bundles, FinTrace saves lawyers and forensic accountants hours of manual statement review. Its searchable ledger and findings report give direct access to the source PDF filename and page behind each finding. That makes the payment evidence easier to place beside the communications in your matrix.
Brief the accountant with the heads counsel considers recoverable, disputed alternatives and the source references for each assumption. Ask for separate totals where the scope decision remains open, so a later ruling changes the relevant schedule without rebuilding the entire claim.
FinTrace
Statements in. Evidence out.
FinTrace turns your bank statements into one searchable Excel ledger and a written findings report, with every finding cited to its source page.
FinTrace
See how FinTrace works