Eilidh Ferreira downgraded her current account in March. The bank confirmed it in writing, and then kept charging her the old account’s £32 monthly fee for eight months. In September a direct debit bounced and she was charged for that too. Her complaint is easy to understand and easy to uphold. The work is in getting the redress exactly right, and in making sure that a sum above the firm’s threshold is approved by someone other than the person who worked it out. This post follows her case on the demo firm’s data.

In short

  • Nine fees in question. The case researcher found eight £32 Premier monthly fees from 28 March to 28 October 2026 and a £10 returned payment fee on 15 September: £266.00.
  • Interest worked out to the penny. Each fee is refunded with simple interest at the illustrative 8% a year from the day it was charged: £7.49 in all, £273.49 in total.
  • Above the threshold, so four eyes. £273.49 is above the illustrative £250 approval threshold. The service agent submitted it; only a team lead who neither proposed nor submitted it can approve it.
  • The approval is on the record. The decision record keeps the items, the rate, the threshold, who proposed, who submitted and who approved. Nothing is paid from InsightService; the refund is made in the firm’s payment system.

The complaint

The demo firm is Fernhollow Bank & Insurance, fictional, with invented customers and fees. The email arrived on 11 November 2026 with the subject “Still being charged for Premier account”:

Eilidh Ferreira, by email

“I downgraded from the Premier account to the Everyday account on 2 March and got a confirmation letter. I’ve only just noticed you’ve carried on charging me the £32 monthly fee every single month since, and in September a direct debit bounced because of it and I got charged for that too. That’s hundreds of pounds. I want all of it back with interest and an explanation of how this happened.”

The triage agent classified it as a complaint about the current account and quoted the sentence that carries the dissatisfaction. The case opened as SVC-2026-000013, and the complaint clock started from receipt: an acknowledgement due by 16 November and a final response by 6 January 2027, under the demo’s illustrative policy of five days and eight weeks.

Case SVC-2026-000013 for Eilidh Ferreira: a complaint by email at the investigation stage, on track with 46 days left; what blocks closing; tiles showing 1 contact, 9 fees in question totalling £266.00, a remediation of £273.49 submitted, 1 reply sent; the quoted sentence; root causes Process failure and Fee charged in error; the case controls; and the complaint clock labelled illustrative policy
The case at a glance. Nine fees in question, £273.49 submitted, and three controls standing between the case and a close.

Finding the fees

Customers rarely list every fee, and handlers rarely have time to scroll six months of statements. The case researcher reads the customer’s accounts and fees from the firm’s records and picks out the fees the message names. Two things in her email matter. She names the monthly fee, and she uses recurring language (“every single month since”), so every monthly fee in the window is in question, not just the latest. She also names the returned payment, so that fee is in question too.

ChargedFeeAmountWhy it is in question
28 Mar 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly, as the customer says
28 Apr 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
28 May 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
28 Jun 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
28 Jul 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
28 Aug 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
15 Sep 2026Returned payment fee · Everyday Current Account£10.00The customer names the returned payment fee
28 Sep 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly
28 Oct 2026Monthly account fee · Premier Current Account£32.00Charged repeatedly

Every row is a fee in the firm’s records, with its fee identifier and the run that charged it. The researcher never invents a charge; if the records held no such fee, it would say so. The fee history underneath marks the nine as “in question” so the handler can see them in context.

The Customer and fees tab: nine fees in question with the charge date, fee, account, amount and why each is in question; Eilidh Ferreira's profile; related cases with the same root cause; knowledge-base articles including Monthly fees on packaged accounts; her four accounts; and the fee history with the nine fees marked In question
Fees in question. Eight Premier monthly fees and one returned payment fee, each with the reason it was picked out.

Working out the redress

The remediation calculator is deterministic code, not a model. For each fee it refunds the amount and adds simple interest: the amount, times the rate, times the days since the charge, divided by 365, rounded to the penny. The rate is SERVICE_REMEDIATION_RATE, 8% a year in the demo. That figure is an illustrative placeholder; your firm sets its own redress policy.

FeeChargedRefundDays to 21 NovInterest
Premier monthly fee28 Mar 2026£32.00238£1.67
Premier monthly fee28 Apr 2026£32.00207£1.45
Premier monthly fee28 May 2026£32.00177£1.24
Premier monthly fee28 Jun 2026£32.00146£1.02
Premier monthly fee28 Jul 2026£32.00116£0.81
Premier monthly fee28 Aug 2026£32.0085£0.60
Returned payment fee15 Sep 2026£10.0067£0.15
Premier monthly fee28 Sep 2026£32.0054£0.38
Premier monthly fee28 Oct 2026£32.0024£0.17
Total£266.00£7.49

The first row, as a check anyone can do: £32.00 × 8% × 238 ÷ 365 = £1.669, which rounds to £1.67. The total redress is £273.49. Because it is code, the QA reviewer can recalculate it later from the same items and confirm the case paid what the calculation says.

yes

no

9 fees in question

Refund each fee: 266.00

Simple interest per fee at the policy rate: 7.49

Total 273.49

Above the approval threshold of 250?

A team lead who did not propose or submit approves

The handler approves

The calculation and the routing. Rate and threshold are illustrative configuration.

Four eyes, enforced

The remediation calculator prepared the remediation; Amara Okafor, the service agent, accepted it, and it went on the case as proposed. Because £273.49 is above the £250 threshold (SERVICE_APPROVAL_THRESHOLD, illustrative), she couldn’t approve it. She submitted it for a team lead’s approval instead.

The rule isn’t a reminder on screen; the API refuses. An approval above the threshold must come from someone with the team-lead role, and that person must not be the one who proposed or submitted it. An agent can never approve or pay at all, at any amount.

The Remediation tab for SVC-2026-000013 as the service agent sees it: £273.49, Submitted, labelled illustrative rate and threshold, proposed and submitted by amara.okafor@fernhollow.example; each fee with its charge date, refund, days and interest; refund and interest £266.00 and £7.49; total £273.49; a Four eyes warning that £273.49 is above the £250 threshold and a team lead who didn't propose or submit it approves it; only a Reject button
What the service agent sees. The arithmetic, the four-eyes warning and no Approve button: she submitted it, so she can only withdraw it by rejecting.

Tom Hartley is a team lead. On his home page, the first thing that needs him is the approval. On the case, he sees the same calculation with an Approve button that Amara never had.

Tom Hartley's home page as team lead: 16 open cases, 1 complaint clock breached, 11 acknowledgements or responses due, and What needs me headed by Approve £273.49 remediation on SVC-2026-000013, submitted by amara.okafor@fernhollow.example, above the £250 threshold
The team lead’s home. The approval waiting for him sits at the top of “What needs me”, with who submitted it and why it needs him.
The same Remediation tab signed in as Tom Hartley, team lead: the nine fees, £273.49 total, the four-eyes warning, and Approve and Reject buttons
What the team lead sees. The same arithmetic, with Approve. Approving records a decision; it doesn’t move money.
Decision recordTeam leadService agentRemediation calculatorDecision recordTeam leadService agentRemediation calculatorThe approver cannot be the proposer or submitterPrepared: 273.49, above the thresholdAccept, remediation proposedSubmit for approvalApprove with a noteItems, rate, threshold, proposer, submitter, approver kept

Who does what. The agent prepares; two different people propose and approve.

The runbook

SVC-2026-000013, from email to closeWhat has happened, and what is still to do
1
Classified and openedtriage agent

Complaint about the current account, the dissatisfied sentence quoted. The clock starts from 11 November.

2
Researchedcase researcher

Nine fees in question, £266.00. No prior complaints. Root causes proposed: process failure, fee charged in error.

3
Root causes taggedservice agent

Accepted the proposal. The tags feed root-cause analysis.

4
Remediation prepared and acceptedremediation calculator

£273.49 with each item’s interest. Above the threshold.

5
Submitted for approvalservice agent

Amara Okafor submits it; she can no longer approve it.

6
Acknowledgement sentservice agent

Sent on 21 November, five days after the illustrative due date; the clock shows it as late.

7
Approve or rejectteam lead

Tom Hartley, who neither proposed nor submitted it. Waiting.

8
Outcomeservice agent

The supervisor proposes “upheld: the records show the fees in question”. A person records it.

9
Final responsereply drafter, then a person

Drafted with the approved refund and interest, the fees listed and cited, and the referral-rights wording flagged as a template. Held until sent.

10
Closeservice agent

Only once no control blocks it.

Until the lead decides, three case controls block a close: no outcome recorded, the final response not sent, and a remediation waiting for a decision. The reply drafter also won’t produce a final response while the remediation is pending, because the letter has to state the redress that was actually approved.

The Agents tab on SVC-2026-000013: one decision waiting, the supervisor's proposal to uphold because the records show the fees in question, listing each fee, with Accept, Reject and Ask; and the last run showing the triage agent, vulnerability spotter, case researcher, remediation calculator, reply drafter and supervisor with their results
The agents’ last run. Every agent ran at L1 with the model off, on rules only. The supervisor’s proposal to uphold waits for a person.

Asking the copilot

A team lead picking up the approval can ask the copilot about the case. It reads the case through read-only tools and never sends, pays, classifies or closes. In the demo the language model is switched off, so it answers from the case’s headline facts and says so.

The InsightService copilot beside SVC-2026-000013, labelled AI off, facts only: asked what the customer wants back and what still blocks closing, it replies with the case's stage, the clock on track with the final response due 2027-01-06 under illustrative policy, 9 fees in question, and the three things before closing
The copilot, model off. A facts-only answer: the clock, nine fees in question, and the three blockers.

For the head of complaints

Inconsistent redress is one of the commonest complaint-handling findings. Here the method is the same on every case, the rate and threshold are your policy, and the approval above it is enforced, not requested.

For the service operations lead

Your handlers stop doing interest arithmetic by hand. They check the fees in question, accept or correct, and route the approval. A lead’s queue shows exactly what needs a second pair of eyes.

For the board

The board can ask how much redress was paid above the threshold, and who approved each sum. The decision record answers both.

What this shows

Getting the outcome right was never the hard part of Eilidh Ferreira’s complaint. Getting nine fees, nine interest periods and a second approver right, every time and for every handler, is. The calculation is code anyone can rerun, the threshold is configuration, and the four-eyes rule is something the system refuses to skip.

Keep reading