Dispute Resolution and FOS Defence 27 October 2026 · 11 min

Strategic FOS Defence, Dispute Resolution and Forensic Redress Modelling

Strategic FOS Defence

High-stakes complaints under the DISP framework

Complaints in wealth management, pensions and private banking are rarely a service grumble. They turn on suitability under COBS, dealing lag, a tax trigger, or a defined benefit transfer. The work is to isolate the allegation, answer it on the rules in force at the time, and, where money is due, calculate it to the FCA benchmark rather than a round number.

The notes linked below are the detailed tests. This page is how they fit a dispute, from the first letter to the redress figure.

Three streams of a dispute

DISP defence Ombudsman rebuttal Redress
The eight-week final response Jurisdiction and precedent Forensic loss modelling
Allegations ring-fenced DISP 2.8 time-bar objections FCA benchmark calculations
A letter that is also the brief Challenging a preliminary view Settlement-lag redress
Plain English under PRIN 2A.5 Stopping retrospectivity Tax drag reconstructed

Who the work is written for

Advisory practices and wealth managers

Retirement planning, defined benefit transfers, decumulation and investment volatility produce the complaints that a standard letter cannot carry.

SIPP operators and custodians

The dispute is often the asset, the dealing lag, the settlement delay, or a tax charge nobody told the member to expect.

An SMF16 holder needs a final response that will stand up, a reply to an adverse preliminary view, or capacity when the cases arrive together.

Firms facing claims-management campaigns

Templated complaints are written to be answered on the merits. The useful first answer is often jurisdictional: time, knowledge, and the rules that actually applied.

Stream 1: DISP defence and adjudication

The case is taken before or after it reaches the Ombudsman. The allegation is isolated. The determination is written to DISP.

The jurisdictional shield

Claims about transactions from eight or ten years ago often arrive in the hope the firm will argue the advice. DISP 2.8.2R is the prior question: six years from the event, or three years from when the complainant knew, or ought reasonably to have known, that they had cause to complain. Valuations, tax statements and the contact log are how that date is proved. The objection asks for the complaint to be dismissed before anyone opens the suitability file.

The full note is The Jurisdictional Shield: Enforcing DISP 2.8 Time Limits Against Stale Claims.

The preliminary view

An investigator’s first assessment can treat a market fall as an advice failure, or apply a standard that did not exist on the advice date. DISP 3.6 and DISP 3.6.4R judge the firm by the rules and good practice at the relevant time. The reply takes the view apart, line by line, before the case reaches a final Ombudsman decision.

The full note is Rebutting the Ombudsman Investigator’s Preliminary View: The Mechanics of an Effective Escalation.

The eight-week letter

DISP 1.6 sets the clock. An apologetic letter written only for the client can concede a breach the file does not support. A final response has to satisfy DISP 1.4 and DISP 1.6, and be plain enough for PRIN 2A.5, while remaining the brief an adjudicator will actually use.

The full note is The 8-Week Final Response Letter: Drafting for the Ombudsman, Not Just the Client.

Attitude to risk and capacity for loss

After a fall, the complaint is often that the portfolio was “too high risk”, against a signed questionnaire that said otherwise. COBS 9.2 asks a prior question: could the client’s finances absorb the loss. The defence is the fact-find: cash buffers, essential spending, and the reserve that was there at the time.

The full note is Attitude to Risk vs Capacity for Loss: Winning the Battle of Contemporaneous Evidence.

The adviser and the platform

Clients sue the adviser for a loss that started in a dealing backlog or a custody delay. COBS 2.1.1R, SYSC and PRIN 2A.2 do not make every firm in the chain liable for every other firm’s delay. The timeline shows when the instruction left the adviser and when the platform failed to act.

The full note is When Advisers and Platforms Collide: Defending the Boundaries of Intermediary Responsibility.

Stream 2: Decisions, precedent and root cause

Published determinations and the rules on retrospectivity are how a speculative campaign is answered, and how a board sees the pattern rather than the count.

Legacy advice and the Consumer Duty

Boilerplate complaints now describe pre-2023 advice in the language of sludge, price and value. PS22/9 did not apply PRIN 2A backwards. DISP 3.6.4R looks at the standards in force on the transaction date. The reply puts the case back on the COBS rules that governed it.

The full note is Halting Regulatory Retrospectivity: Defending Legacy Advice Against Post-Consumer Duty Claims.

SIPP custody and advisory due diligence

When an unregulated asset inside a SIPP fails, the complaint often names the adviser and the operator together. Section 27 of FSMA, COBS 9A and Principle 2 draw different duties. Adams v Options UK is about the operator. It is not a reason to treat the adviser’s file and the trustee’s file as the same document.

The full note is SIPP Custody vs Advisory Due Diligence: Applying Adams v Options UK to Intermediary Disputes.

Complaints as board information

A count of closed complaints is not DISP 1.3. It is also not the monitoring PRIN 2A.9 requires, or the annual governing-body report under PRIN 2A.8. Root cause has to name the operational failure: sludge, a fee that was not explained, a vulnerable customer who was missed.

The full note is Turning FOS Casework into Consumer Duty Root-Cause MI: Complaints as Governance Telemetry.

Stream 3: Loss and redress

Where there was a fault, the figure has to be the loss, not a gesture. Overpayment is its own problem. Underpayment comes back as a second complaint.

Cash in, cash out is not a redress calculation

A simple comparison of money in and money out fails the pension transfer method in FG17/9 and DISP App 1. The calculation reconstructs the position the client would have been in: the benchmark, the fees, and the tax.

The full note is Beyond Simple Cash Differences: Why Generalist Accounting Fails FCA Redress Benchmarks (FG17/9).

Emergency tax is not always a loss

A first flexi-access or UFPLS payment is often taxed on the Month 1 code 1257L M1. The deduction can be £5,000 to £20,000. Most of it is temporary. PRIN 2A.2 and PRIN 2A.5 ask whether the client was warned, and whether the money can be reclaimed. HMRC forms P55 and P53Z are the reclaim route. A settlement that refunds the whole deduction, as if it were gone, overpays.

The full note is The Month 1 Emergency Tax Trap: Assessing True Detriment vs Temporary Cashflow Drag Under Code 1257L M1.

Distress and inconvenience

Claims for £5,000 to £10,000 of upset, attached to an ordinary delay, sit outside the Ombudsman’s published bands. Those bands run from nominal awards around £100 to severe awards above £5,000. The log of what actually happened is what places the case on that scale.

The full note is Benchmarking Distress and Inconvenience: Defending Against Exaggerated Non-Financial Detriment Claims.

When the work starts

  • On day one. A high-value complaint, a contentious one, or a claims-management letter. The scope is ring-fenced and the time-bar is checked before anyone drafts on the merits.
  • As the eight weeks run out. The final response still has to go, and it has to be the brief.
  • When the preliminary view arrives. An unfavourable assessment built on hindsight or a misunderstood product.
  • When fault is accepted. The compensation is modelled so the firm neither overpays nor invites a second dispute about the sum.

Why the letter is a balance-sheet document

  • Defensible advice, conceded in a weak letter, marks the claims record and the professional indemnity renewal.
  • An apology that admits a COBS breach hands the adjudicator a finding the file may not support.
  • Speculative campaigns depend on the firm missing DISP 2.8, or treating the Consumer Duty as if it rewrote the past.
  • The FCA reads complaint handling as governance. A pattern that is not reported is an SMF16 problem under the Senior Managers regime.

How a case moves

1. Forensic discovery

Fact-finds, call notes, dealing timestamps and platform audit trails. The case is triaged before it is answered.

2. Separate the parties

Advice is separated from custody delay under COBS 2.1.1R and PRIN 2A.2, so liability sits with the firm that caused it.

3. Write the defence

A rebuttal or a final response: Handbook citations, a chronology, and language a client can follow.

4. Represent the file

Jurisdiction, the investigator, and any appeal to an Ombudsman. The same technical position, held all the way through.

5. Feed the board

The operational lesson goes into the risk taxonomy, the board pack, and the Consumer Duty management information.

Summary

A complaint file is a contemporaneous record, a jurisdiction point, and a number that can be explained. The tests above are how final responses, Ombudsman replies and redress are read before the case is conceded.

Where the need is an escalated dispute, a referral, or a redress model, the place to start is the contact page.

Other insights