Case Studies

S.E.A · Case Studies

Restrained, evidence-led readings of public records through one lens: how authority was obtained, trusted and abused, and what a board should ask next.

Every claim is labelled Documented, Reported or Inference.

Public-Incident Analysis & Client Confidentiality

S.E.A protects the confidentiality of its engagements. We do not identify clients or publish their logos or engagement details.

This series independently examines public incidents using publicly available records and reputable reporting. It distinguishes documented facts, reported claims and analytical inference; allegations remain identified as allegations. Inclusion does not imply that S.E.A advised, tested or worked with any organization discussed.

Episode 1 · Pilot

The Reset Desk

Transport for London · 2024

Who owns the standard of evidence behind each identity reset?

Authority, Obtained · Episode 2

The Final Payment

MacEwan University · 2017

C$11.8 million owed by MacEwan University, redirected by one changed payee record.

Authority, Obtained · Episode 3

Without Mandate

CMOC · Foglia · M & S Restorations · 2016–2019

US$6.91 million and €1.27 million paid by a bank in London, on instructions the company had never authorised.

Reading

Summary

Read the transcript

  • Documented
    In a primary public record: sentencing remarks, CPS, NCA, or TfL’s own statements (tagged as the victim’s statement).
  • Reported
    In reputable press reports of the sentencing hearing; not in the sentencing remarks’ wording.
  • Inference
    S.E.A’s own analysis.
Documented
The court dates the intrusion from 31 August to 3 September 2024. The attackers, acting with others unknown, gained access to TfL’s systems “at increasingly high levels”, and personal data was taken from the Oyster card database [1]. TfL severed all remote access and disabled its internet connection; no fewer than 27,000 users had to reset their passwords [1]. The NCA reports the resets were made in person and that 148 systems became inoperable [3]. The NCA says TfL “suffered a reported £29 million in loss and recovery costs” [3].
Reported
Press reports of the sentencing hearing describe how the intrusion began: someone posing as an employee asked the help desk for a reset [6][7]. The record does not say how the request was checked. It says the access was re-issued.
Inference
A service desk sits on an authority path. Re-issuing an identity is a privileged act, as consequential as approving a payment, and it deserves an owner at the level of the risk.

Method detail, people and data are omitted by design.

Record

Timeline

  1. Documented
    Intrusion begins[1]
  2. Documented
    TfL identifies suspicious activity (per TfL)[4][5]
  3. Documented
    Intrusion ends; remote access severed[1]
  4. Documented
    All-staff identity check; password resets made in person[3][5]
  5. Documented
    ICO: no regulatory action; matter closed (per TfL)[4]
  6. Documented
    Guilty pleas: conspiracy, base offence Computer Misuse Act 1990 s.3ZA[1][3]
  7. Documented
    Sentences: 5 years 6 months each (total)[1][2][3]

Lens

The authority path

Diagram: an employee identity claims access from the service desk, which can re-issue an access credential. A verification owner sits between the claim and the desk. Employee identity Service desk Access credential claims can re-issue Verification owner
Inference
S.E.A framing: a general description of service-desk roles, not TfL’s procedures.

Boardroom

The board question

When someone asks us to re-issue an employee’s access, what evidence must they give that they are that employee, who owns that standard, and when did this board last see it tested?

Held film

Transcript

Labels and source numbers are S.E.A’s editorial mapping. Inference identifies S.E.A’s analysis, not findings of the court.

Documented
In twenty twenty-four, London’s transport authority had to cut its own systems off from the outside world. [1]
Reported
It began, as the hearing was reported, with a request for help. Nothing about it was unusual. That was the point. Authority wasn’t stolen. It was issued. [6][7]
Inference
Episode one of Authority, Obtained. The Reset Desk. Every large organisation has a function whose job is to give access back to people who have lost it. A forgotten password. A locked account. The service desk restores it, quickly, because work stops until it does.
Reported
That makes the desk more than a support queue. It holds a quiet kind of authority: the power to re-issue an employee’s identity. Press reports of the sentencing hearing describe how this intrusion began. Someone posing as an employee asked the help desk for a reset, and that access was re-issued to the attackers instead. The claim was an ordinary identity. The power that mattered was the desk’s. [6][7]
Inference
The court dates the intrusion from the thirty-first of August, twenty twenty-four. What follows is our inference, not the court’s finding. A remote worker who cannot get in is among the most routine requests a service desk receives. The desk exists to say yes. Speed is usually how it is measured. [1]
Inference
And a request to restore access looks like every other request in the queue. That is why it was trusted. Not through carelessness, but because complying felt like good service. The record does not say how the request was checked. It says the access was re-issued.
Documented
From that point, the court records, the attackers, acting with others unknown, gained access to TfL’s systems at increasingly high levels. One courtesy had become a foothold inside the organisation. [1]
Documented
The judge described a combination of techniques, including social engineering and the use of sophisticated software. We will not go further into method. What matters to a board is the outcome. [1]
Documented
The intrusion ran for four days, to the third of September. In that time, the court records, a large quantity of personal data was taken from the Oyster card database. Access granted as a courtesy had been carried far beyond its purpose. The authority was real. The person using it was not. [1]
Documented
It stopped only when TfL took what the judge called extreme and desperate measures. It severed all remote access to its systems and disabled its connection to the internet. The court records that no fewer than twenty-seven thousand users had to reset their passwords. [1]
Documented
The National Crime Agency reports those resets were made in person, and that one hundred and forty-eight systems became inoperable. Dial-a-Ride, concessionary travel cards and digital payments were all affected. The agency reports that TfL suffered a reported twenty-nine million pounds in loss and recovery costs. [3]
Documented
The public record has since settled, in three dates. TfL states that on the thirteenth of February 2025, the Information Commissioner’s Office confirmed it would take no regulatory action and considered the matter closed. [4]
Documented
On the twenty-second of June 2026, what was to be the first day of trial, two defendants pleaded guilty to conspiracy to commit unauthorised acts in relation to a computer causing or creating risk of serious damage, the base offence being section 3ZA of the Computer Misuse Act 1990. One also admitted two further offences against other victims. On the sixteenth of July, at Woolwich Crown Court, each received a total sentence of five years and six months. [1][2][3]
Documented
The judge assessed culpability as medium to high, and the prosecution accepted their actions were reckless, not intended. We do not show them. This is not their story. It is the story of an authority path. [1]
Inference
Which brings it to the boardroom. A service desk does not sit on a support queue. It sits on that path. Re-issuing an identity is a privileged act, as consequential as approving a payment, and it deserves an owner at the level of the risk. Speed is easy to report to a board. The standard of evidence behind each reset is harder to see, and it is the one that matters.
Inference
So the question is this. When someone asks us to re-issue an employee’s access, what evidence must they give that they are that employee, who owns that standard, and when did this board last see it tested?

Evidence

Public sources

  1. Judiciary of England and Wales · 16 Jul 2026 · retrieved 5 Nov 2026
    Mr Justice Turner, sentencing remarks, Woolwich Crown Court (case name, which contains the defendants’ names, not reproduced in the text)
    Judgment page · PDF
  2. Crown Prosecution Service (CPS) · 16 Jul 2026 · retrieved 5 Nov 2026
    “Cyberhackers who targeted TfL jailed for more than five years each”
    cps.gov.uk (https://www.cps.gov.uk/national-news/news/cyberhackers-who-targeted-tfl-jailed-more-five-years-each)
  3. National Crime Agency (NCA) · 16 Jul 2026 · retrieved 5 Nov 2026
    “Two sentenced for hacking Transport for London…”
    nationalcrimeagency.gov.uk (https://www.nationalcrimeagency.gov.uk/news/two-sentenced-for-hacking-transport-for-london-in-uk-s-biggest-ever-cyber-crime-case)
  4. Transport for London · Last reviewed 16 Jul 2026 · retrieved 5 Nov 2026
    Cyber security incident page (victim’s statement)
    tfl.gov.uk (https://tfl.gov.uk/fares/free-and-discounted-travel/cyber-security-incident)
  5. Transport for London · 6 and 12 Sep 2024 · retrieved 5 Nov 2026
    Press releases: update on ongoing cyber security incident (victim’s statements)
    6 Sep 2024 (https://tfl.gov.uk/info-for/media/press-releases/2024/september/tfl-provides-update-on-ongoing-cyber-security-incident) · 12 Sep 2024 (https://tfl.gov.uk/info-for/media/press-releases/2024/september/tfl-provides-update-on-ongoing-cyber-security-incident---12-september)
  6. The Guardian · 16 Jul 2026 · retrieved 5 Nov 2026
    Sentencing coverage
    theguardian.com (https://www.theguardian.com/technology/2026/jul/16/hackers-2024-cyber-attack-transport-for-london-tfl-jailed)
  7. BBC News · 16 Jul 2026 · retrieved 5 Nov 2026
    Sentencing coverage
    bbc.co.uk (https://www.bbc.co.uk/news/articles/c4gyg0y6yg2o)

Sources are cited, not reproduced. Figures differ between sources; each is attributed.

Method

Method note

Settled public record only. Each claim is labelled Documented, Reported or Inference. Deliberately omitted: method detail, people and data. Defendants are not shown. Corrections are applied to the film, page and brief together.

Contact

Enquiries

Engagements by introduction.

REQUEST AN INTRODUCTION

Reading

Summary

Read the transcript

  • Documented
    In a primary public record: the Auditor General of Alberta, the university’s own annual report, or a court judgment.
  • Reported
    In reputable press reports, or in university or contractor statements as quoted in that press.
  • Inference
    S.E.A’s own analysis.
Documented
The Auditor General of Alberta recorded that “Senior-level approvals were also removed from processes related to changes to vendor master files.” It found no evidence the audit committee was told. The Auditor General attributed the loss to “a breakdown in internal control around vendor master files.” [1] The university’s annual report records a loss of C$11.8 million and a recovery of C$10.8 million, and that a task force’s recommendations were implemented, including mandatory training. [3] In March 2021 the Auditor General reported its recommendation implemented. [2]
Reported
In August 2017 the university paid C$11.8 million it owed to its building contractor; none of it reached the contractor. [4][5][6] It began, as the university described it, with a request to change a supplier’s banking details. The university says its systems were never breached. [4][6] One detailed press account, drawing on court filings, describes emails that appeared to come from the contractor’s accounts department, asking that payments go to a new account. The record was changed. [7] In April 2018 the university said it had recovered just over 92 per cent (C$10.92 million), with C$880,000 not recovered, at a cost of about C$250,000 in legal and banking fees; the loss stayed with the university. [4][5][10]
Inference
Every organisation that pays suppliers keeps a record of where each one is paid. Change that record, and every payment follows. Whoever can change it holds a quiet kind of authority: deciding where the money goes. The title of this episode, and the line “Authority wasn’t stolen. It was believed,” are S.E.A’s editorial framing, not a finding or a quotation.

Method detail, people, emails and interfaces are omitted by design.

Record

Timeline

  1. Reported
    Change request dated, according to court filings reported in the press. [7]
  2. Reported
    Payment of C$1.9 million. [4][5]
  3. Reported
    Payment of C$22,000. [4]
  4. Reported
    Payment of C$9.9 million. Total paid: C$11.8 million. [4][5]
  5. Reported
    The real contractor called about payments it had not received; the payments came to light. [4][6]
  6. Reported
    A court in Montreal ordered the seizure of C$6.3 million, according to court filings reported in the press. No court record of the order has been retrieved for this page. [7]
  7. Reported
    Public disclosure. The minister responsible instructed every post-secondary board chair in the province to review financial controls. [4]
  8. Documented
    The Auditor General recommended better reporting on internal controls to the university’s board. [1]
  9. Reported
    The university said it had recovered just over 92 per cent; recovery cost about C$250,000 in legal and banking fees; the loss stayed with the university. [4][5][10]
  10. Documented
    The Auditor General reported the recommendation implemented. [2]

Lens

The authority path

Diagram: a supplier identity claims a place in the payee record, which directs the payment run. Whoever can change the record decides where the money goes. Supplier identity Payee record Payment run claims directs
Inference
S.E.A framing: a general description, not MacEwan’s procedures.

Boardroom

The board question

Who can change a payee’s bank details, what independent confirmation is required, would the board know if that control were loosened, and do our contracts say who bears the loss?

Held film

Transcript

Labels and source numbers are S.E.A’s editorial mapping. Inference identifies S.E.A’s analysis, not findings of the Auditor General, the university or any court.

Reported
In August twenty seventeen, a Canadian university paid eleven point eight million dollars it owed to its building contractor. None of it reached the contractor. [4][5][6]
Reported
It began, as the university described it, with a request to change a supplier’s banking details. The university says its systems were never breached. [4][6]
Inference
Authority wasn’t stolen. It was believed.
Inference
Episode two of Authority, Obtained. The Final Payment. Every organisation that pays suppliers keeps a record of where each one is paid. Change that record, and every payment follows. Whoever can change it holds a quiet kind of authority: deciding where the money goes.
Reported
One detailed press account, drawing on court filings, describes emails that appeared to come from the contractor’s accounts department, asking that payments go to a new account. The record was changed. [7]
Reported
The contractor had worked with the university since two thousand and three, and was finishing a new arts campus. [4]
Inference
What follows is our inference, not a finding about any person. A long-standing supplier, late in a project, looks like housekeeping. Updating the record feels like good service.
Documented
Alberta’s Auditor General later recorded that senior-level approvals had been removed from changes to vendor master files, and found no evidence the audit committee was told. The Auditor General attributed the loss to “a breakdown in internal control around vendor master files.” [1]
Reported
The university’s review, as reported, found no manager check and no call to the supplier. [4][7]
Reported
Then the payment runs. On the tenth of August, one point nine million dollars. On the seventeenth, twenty-two thousand. On the nineteenth, nine point nine million. Three payments, one destination. [4][5]
Reported
That last payment, the contractor’s chief executive told CBC News, was “the holdback that was due to us for the final billing on that project.” A holdback is the share of each payment held back until the work is complete (UK: retention). [4]
Reported
On the twenty-third of August, the real contractor called about payments it had not received. That is how it came to light. A preliminary review found that a number of opportunities to identify the fraud were missed. [4][5][6]
Inference
The payment authority was real. The instruction it followed was not.
Reported
Two days later, according to court filings reported in the press, a court in Montreal ordered the seizure of six point three million dollars from the account that had received it. Funds traced to Hong Kong were pursued there. Counsel was instructed in Montreal, London and Hong Kong. No court record of the seizure has been retrieved for this page. [7][4]
Reported
In April twenty eighteen the university said it had recovered just over ninety-two per cent of the funds, at a cost of about two hundred and fifty thousand dollars in legal and banking fees. The contractor, as it had said from the start, would not lose money. The loss stayed with the university. [4][5][10]
Documented
The university’s annual report records a recovery of ten point eight million dollars. The April statement and the annual report differ; each is attributed. [3]
Reported
The public record then settled, in three dates. On the thirty-first of August, twenty seventeen, the minister responsible instructed every post-secondary board chair in the province to review financial controls. [4]
Documented
In February twenty eighteen, the Auditor General recommended better reporting on internal controls to the university’s board. In March twenty twenty-one, the Auditor General reported that recommendation implemented. [1][2]
Reported
The university says supplier changes are now confirmed by phone and follow-up email, and reviewed by a supervisor, manager or director. [5][10]
Documented
Training became mandatory. [3]
Inference
No staff or contractor is named here. This is not a story about people. It is the story of a payee record.
Documented
Between two businesses, who carries that loss? Courts in Ontario and British Columbia have held that the payer who follows false payment instructions bears it—unless a contract shifted the risk, or the payee was dishonest or negligent. In the British Columbia case, the payer was ordered to pay the supplier’s invoice. The British Columbia court set out that principle by quoting an earlier Ontario Small Claims Court decision as an example of the court’s reasoning. Neither case involved MacEwan. This is not legal advice. [8][9]
Documented
The court there described the payer as “the party who most enabled the unknown third party to create the fraud,” and as best placed to notice “changed or unusual payment instructions.” Both cases were commercial disputes: a settlement payment in the Ontario Small Claims Court, and a supplier’s invoice in the British Columbia Supreme Court, a trial court. [8][9]
Inference
They are not the last word on the law. They are a reason to read your contracts. This is not legal advice.
Inference
Which brings it to property. A REIT pays a contractor on a development, releases a holdback, or pays a vendor on an asset it already holds. The mechanism is the same at any size: a request, a change to a record, a payment that follows the record. The largest payments draw scrutiny. The everyday ones are the most numerous.
Inference
So the question is this. Who can change a payee’s bank details, what independent confirmation is required, would the board know if that control were loosened, and do our contracts say who bears the loss?
Inference
Confirm every change through contact details you already hold. A second person on every change. Decide in the contract, before money moves, who carries the loss. None of this guarantees a payment is safe. This is not legal advice.

Evidence

Public sources

  1. Office of the Auditor General of Alberta · Feb 2018 · retrieved 10 Nov 2026
    Report on Post-Secondary Institutions 2017 (especially pp. 5, 10).
    Report page (https://www.oag.ab.ca/reports/report-psis-feb2018/) · PDF (https://www.oag.ab.ca/wp-content/uploads/2020/05/AE_FS_Feb2018Report_on_PSIs.pdf)
  2. Office of the Auditor General of Alberta · Mar 2021 · retrieved 10 Nov 2026
    Report on Post-secondary Institutions 2020 (recommendation reported implemented, pp. 10–11).
    Report page (https://www.oag.ab.ca/reports/oag-report-on-psis-2020-mar-2021/) · PDF (https://www.oag.ab.ca/wp-content/uploads/2021/03/oag-advanced-education-psi-fs-mar-2021.pdf)
  3. MacEwan University · Annual Report 2017/18 · retrieved 10 Nov 2026
    Records a loss of C$11.8 million and a recovery of C$10.8 million, mandatory training, and a task force whose recommendations were implemented.
    PDF (https://www.macewan.ca/c/documents/annual_report_2017_18.pdf)
  4. CBC News · 31 Aug 2017, 1 Sep 2017 and 4 Apr 2018 · retrieved 10 Nov 2026
    Coverage of the payments, the university’s account of the change request, the contractor’s account of the holdback, and the April 2018 recovery statement. The 1 Sep 2017 headline, which names the contractor, is not reproduced.
    31 Aug 2017 (https://www.cbc.ca/news/canada/edmonton/macewan-university-phishing-scam-edmonton-1.4270689) · 1 Sep 2017 (https://www.cbc.ca/news/canada/edmonton/macewan-university-phishing-attack-fraud-1.4272350) · 4 Apr 2018 (https://www.cbc.ca/news/canada/edmonton/macewan-university-recovers-most-of-11-8m-online-phishing-scam-1.4604729)
  5. Edmonton Journal · 1 Sep 2017 and 4 Apr 2018 · retrieved 10 Nov 2026
    Coverage of the payments and of the university’s April 2018 recovery statement and new controls.
    1 Sep 2017 (https://edmontonjournal.com/news/local-news/11-8-million-transferred-from-macewan-university-accounts-in-phishing-attack) · 4 Apr 2018 (https://edmontonjournal.com/news/crime/macewan-university-recovers-10-9-million-lost-to-scammers)
  6. BBC News · 31 Aug 2017 · retrieved 10 Nov 2026
    Coverage of the payments and the university statement that IT systems were not compromised.
    bbc.com (https://www.bbc.com/news/world-us-canada-41116177)
  7. Toronto Star (StarMetro Edmonton) · 9 Oct 2018 · retrieved 10 Nov 2026
    Account citing court filings of the change request, the 25 August 2017 Montreal seizure of C$6.3 million, and the reported absence of a manager-review requirement. The article names staff and other individuals; those names are not repeated here.
    thestar.com (https://www.thestar.com/edmonton/how-a-fraudster-got-12-million-out-of-a-canadian-university-they-just-asked-for/article_d41251b4-9683-5eb4-9a48-41d83de08042.html)
  8. Supreme Court of British Columbia · 2023 BCSC 2529 · retrieved 10 Nov 2026
    Apex Aluminum Extrusions Ltd. v. KD Sales & Service Limited. Cited for the payer-bears-the-loss principle, including the court’s quotation of the Ontario decision at [9], and for the wording at paras 105 and 107. As at 11 Nov 2026, no published British Columbia Court of Appeal decision on this point was found. Not legal advice.
    bccourts.ca (https://www.bccourts.ca/jdb-txt/sc/23/25/2023BCSC2529.htm)
  9. Ontario Small Claims Court · 2019 CanLII 69697 · retrieved 10 Nov 2026
    St. Lawrence Testing & Inspection Co. Ltd. v. Lanark Leeds Distribution Ltd. Documented here as quoted in the British Columbia judgment at [8], paras 56–57, 60 and 61, and used as an example of a court’s reasoning. Not legal advice.
    canlii.org (https://www.canlii.org/en/on/onscsm/doc/2019/2019canlii69697/2019canlii69697.html)
  10. Global News · 4 Apr 2018 · retrieved 10 Nov 2026
    Coverage of the April 2018 recovery statement and of the university’s described new controls (confirmation by phone and email, with supervisor review).
    globalnews.ca (https://globalnews.ca/news/4122937/macewan-university-recovers-millions-lost-in-phishing-scam/)

Sources are cited, not reproduced. Figures differ between sources; each is attributed. C$11.8 million paid; C$10.92 million recovered (“just over 92 per cent”) and C$880,000 not recovered, university statement, April 2018; C$10.8 million recovered, MacEwan Annual Report 2017/18; about C$250,000 legal and banking fees, university statement, April 2018.

Method

Method note

Public record as at 10 Nov 2026. Each claim is labelled Documented, Reported or Inference. Deliberately omitted: method detail, people, emails and interfaces. No staff or contractor is named. S.E.A had no involvement in this case. Nothing here is legal advice. Corrections are applied to the film, page and brief together.

Contact

Enquiries

Engagements by introduction.

REQUEST AN INTRODUCTION

Reading

Summary

Read the transcript

  • Documented
    In a primary public record: an English court judgment, fetched from the National Archives.
  • Inference
    S.E.A’s own analysis.
Documented
In October 2017 CMOC Sales & Marketing Ltd, an English company, discovered that its bank in London, Bank of China, had paid US$6.91 million and €1.27 million in twenty transfers. None had been authorised by the company. The emails that instructed the bank appeared to come from a director who was one of only two authorised signatories; his email account had been hacked, and he did not know the instructions had been sent. The Commercial Court found that the fraud “incontestably occurred”, and the claims against the unknown perpetrators and named recipients succeeded. Bank of China was not a defendant to those claims, and the court made no finding that it was at fault or in breach. [1]
Documented
In July 2019 a caller impersonating an authorised signatory of an Italian fiduciary told CITCO, a Cayman bank, to expect a faxed instruction, then rang again to confirm it had been sent. The fax carried forged signatures, and on 18 July 2019 the bank paid €15 million to a company account in England. Summary judgment was granted against the recipients, not the bank; CITCO’s liability was not before the court. [3]
Documented
In January 2016 Banco Santander Totta S.A. acted on an email from a company director’s account instructing a payment of £35,425, after a fraudster supplied the invoice the bank asked for. The County Court found it was “the work of third party fraudsters, not the doing of any agent of the Company”, and entered judgment for M & S Restorations Ltd. On a later costs appeal, the High Court recorded that the bank had acted outside its mandate and could not debit the account. [2]
Inference
Each institution treated an instruction as normal business because it appeared to carry authority: a signatory’s inbox, a call ahead to a payment desk, a routine invoice check. The title of this episode, and the line “Authority wasn’t stolen. It was believed,” are S.E.A’s editorial framing, not a finding or a quotation.

Method detail, people, emails, calls, faxes and interfaces are omitted by design.

Record

Timeline

  1. Documented
    An email from a company director’s account instructs Banco Santander Totta to pay £35,425; the bank asks for an invoice, a fraudster supplies one, and the account is debited. As recited in the High Court. [2]
  2. Documented
    CMOC discovers twenty transfers by its bank in London, US$6,913,503.90 and €1,270,679.30, that it had not authorised. [1]
  3. Documented
    First hearing in the Commercial Court. [1]
  4. Documented
    The Commercial Court finds the fraud “incontestably occurred”; the claims against the unknown perpetrators and named recipients succeed. Bank of China in London is not a defendant to those claims; no finding of fault or breach is made against it. [1]
  5. Documented
    A caller impersonating an authorised signatory tells CITCO to expect a faxed instruction, then calls again to confirm it was sent. The fax arrives on the fiduciary’s letterhead; the signatures are forgeries. [3]
  6. Documented
    CITCO, a Cayman bank, pays €15 million to a company account in England. [3]
  7. Documented
    Summary judgment against the recipients, not the bank. €11,456,631 recovered; €3,543,368 plus interest outstanding. CITCO’s liability was not before the court. [3]
  8. Documented
    County Court trial: the work of third party fraudsters, not any agent of the company; judgment for M & S Restorations for £35,425 plus interest. As recited in the High Court. [2]
  9. Documented
    High Court costs appeal records that the bank had acted outside its mandate and could not debit the account. [2]

Lens

The authority path

Diagram: an instruction claims the authority of a signatory, which the bank mandate follows to make the payment. If the instruction was never the customer’s, the payment was made without mandate. Instruction Bank mandate Payment claims directs
Inference
S.E.A framing: a general description, not the procedures of any bank or company named here.

Boardroom

The board question

Who is authorised to instruct our bank? How is that authority independently confirmed? Would the board know if that control were loosened? And if an instruction was not ours, who bears the debit?

Held film

Transcript

Labels and source numbers are S.E.A’s editorial mapping. Inference identifies S.E.A’s analysis, not findings of any court.

Documented
In October twenty seventeen, C-M-O-C Sales and Marketing, an English company, discovered that its bank in London had paid six point nine one million US dollars and one point two seven million euros, in twenty transfers. None of those payments had been authorised by the company. [1]
Documented
The emails that instructed the bank appeared to come from a director who was one of only two authorised signatories. [1]
Inference
The perpetrators had not broken a vault. They had stepped inside his inbox, and sent purported payment instructions as if they were his.
Documented
The real signatory did not know they had been sent. [1]
Inference
Authority wasn’t stolen. It was believed.
Inference
Episode three of Authority, Obtained. Without Mandate. Earlier episodes looked at a help-desk identity reset, and at a supplier’s payee record. This one is about a different authority: the mandate a bank is built to follow, when an instruction arrives that looks as if it comes from someone entitled to give it.
Documented
The company took the matter to the Commercial Court in London. The court recorded that the perpetrators impersonated an authorised signatory, and caused twenty separate transfers, before the fraud was discovered. [1]
Documented
The court later found that the fraud incontestably occurred. The company had discovered it on the twelfth and thirteenth of October, and the first hearing followed later that month. [1]
Documented
The claims against the unknown perpetrators, and against named recipients, succeeded. The Bank of China in London was not a defendant to those claims. [1]
Documented
The court made no finding that the bank was at fault, or in breach. Its findings established that the instructions the bank received were not the company’s. [1]
Documented
Two years later, a different method reached an English court. In July twenty nineteen, someone telephoned a Cayman bank, CITCO, impersonating an authorised signatory of an Italian fiduciary, and told the bank to expect a faxed instruction the next day. The next morning, the caller rang again, to confirm that the fax had been sent. The fax arrived on the fiduciary’s letterhead. The signatures were forgeries. On the eighteenth of July, the bank paid fifteen million euros to a company account in England. [3]
Documented
The Commercial Court later granted summary judgment against the recipients, not against the bank. By then, just over eleven point four million euros had been recovered; just over three point five million, plus interest, remained. The paying bank was a Cayman bank. Whether that bank bore any liability was not before the court, and was left undecided. [3]
Documented
When an English court did decide a bank’s position, the facts were smaller, and the finding was stark. In January twenty sixteen, Banco Santander Totta received an email from a company director’s account, instructing a payment of thirty-five thousand, four hundred and twenty-five pounds. The bank asked for an invoice. A fraudster sent one. The next day, the account was debited. More than seven years later, in September twenty twenty-three, the County Court tried the claim. [2]
Documented
The trial judge found it was the work of third party fraudsters, not any agent of the company. This was not a case where a customer had been deceived into authorising a payment, and not a case of an agent with apparent authority. The High Court, on a later costs appeal, recorded the position: because the customer had not authorised the payment, the bank had acted outside its mandate and could not debit the account. At trial in twenty twenty-three, judgment had already been entered for the company, for that sum plus interest. [2]
Inference
This is not legal advice.
Inference
Three records, one path. The adversary exploited ordinary banking routine, and trust: stepping into a signatory’s inbox, calling ahead to prime a payment desk, or answering a routine invoice check. Institutions treated each instruction as normal business, because it appeared to carry authority. The mechanism is the same at any size. The authority was believed.
Inference
So the question is this. Who is authorised to instruct our bank? How is that authority independently confirmed? Would the board know if that control were loosened? And if an instruction was not ours, who bears the debit?
Inference
None of this guarantees a payment is safe. It is practice: confirm an instruction through contact details you already hold, put a second person on the mandate, and know, before the money moves, what your mandate actually says, and who carries the debit if it was never yours.

Evidence

Public sources

  1. England and Wales High Court (Commercial Court) · [2018] EWHC 2230 (Comm) · retrieved 13 Nov 2026
    CMOC Sales & Marketing Ltd v Person Unknown & Ors, 26 July 2018. Cited for the English company, the email compromise of an authorised signatory, Bank of China in London, the twenty transfers and the sums, discovery on 12–13 October 2017, the first hearing on 23 October 2017, the finding that the fraud “incontestably occurred”, the success of the claims, and that the bank was not a claim defendant. Not legal advice.
    caselaw.nationalarchives.gov.uk (https://caselaw.nationalarchives.gov.uk/ewhc/comm/2018/2230)
  2. England and Wales High Court (King’s Bench Division) · [2024] EWHC 2724 (KB) · retrieved 13 Nov 2026
    M & S Restorations Ltd v Banco Santander Totta S.A. & Ors, 28 October 2024. A High Court costs appeal, cited for the January 2016 facts as recited, £35,425, the September 2023 County Court trial and judgment for the company, the third-party fraudsters finding, the distinction from authorised-push-payment and apparent-authority cases, and the outside-the-mandate holding. Not legal advice.
    caselaw.nationalarchives.gov.uk (https://caselaw.nationalarchives.gov.uk/ewhc/kb/2024/2724)
  3. England and Wales High Court (Commercial Court) · [2021] EWHC 650 (Comm) · retrieved 13 Nov 2026
    Foglia v The Family Officer Ltd & Ors, 22 March 2021. Cited for the telephone impersonation of an authorised signatory (a call ahead, then a confirming call), the forged fax, the €15 million paid on 18 July 2019 by CITCO (Cayman) to a company account in England, the recoveries and outstanding sum, summary judgment against the recipients, and that CITCO’s liability was not before the court. Not legal advice.
    caselaw.nationalarchives.gov.uk (https://caselaw.nationalarchives.gov.uk/ewhc/comm/2021/650)

Sources are cited, not reproduced. The County Court trial judgment in M & S (21–22 September 2023) is not on the National Archives; liability facts are as recited in [2]. Related, not an appeal of the findings used here: CMOC interlocutory judgment [2017] EWHC 3602 (Comm), 17 November 2017. Appeal check, 13 Nov 2026: no Court of Appeal or Supreme Court judgment found reversing the CMOC fraud findings, the M & S liability finding, or the Foglia summary judgment. Figures are the judgments’ own: US$6,913,503.90 and €1,270,679.30 [1]; €15 million, €11,456,631 recovered and €3,543,368 plus interest outstanding [3]; £35,425 plus interest [2].

Method

Method note

Public record as at 13 Nov 2026. Each claim is labelled Documented or Inference; there is no press layer in this episode. Bank of China in London was not a defendant, and no finding of fault or breach was made against it. CITCO’s liability was not before the court. Receiving banks are not named. Deliberately omitted: method detail, people, emails, calls, faxes and interfaces. No staff or personal names. S.E.A had no involvement in these cases. Nothing here is legal advice. Corrections are applied to the film, page and brief together.

Contact

Enquiries

Engagements by introduction.

REQUEST AN INTRODUCTION