The FCA has banned and fined two former Blue Horizon Asset Management executives following misconduct connected with attempts to acquire a UK bank and Reading Football Club.
Controls cannot make people honest. But they can make accountability much harder to hide.
Former CEO Paul Taylor was fined £489,000 and former managing director Esmeralda Toni £121,200.
The FCA found that, during the proposed bank acquisition, false documentation was created concerning ownership of a bond portfolio worth approximately €200 million. Toni was found to have assisted Taylor in making misleading statements to the bank and in producing false documentation connected with that attempted acquisition.
Taylor later made further misleading claims about owning the same portfolio while attempting to acquire Reading Football Club.
The regulator concluded that Taylor and Toni had acted dishonestly over an extended period and that their actions were intended to mislead colleagues, counterparties and regulators.
The case itself is about individual dishonesty.
It is not a customer-communications enforcement case.
But it raises a broader operational question for regulated organisations:
When important information is created, changed, reviewed, approved or released, can the organisation reconstruct exactly what happened afterwards?
The problem is not only approval
Many regulated organisations already have approval processes.
A document may be reviewed by Compliance.
A wording change may require Legal approval.
An operations team may confirm that a communication is ready to go live.
But having an approval process and being able to prove exactly how that process operated are not necessarily the same thing.
The harder questions often come later:
Who created or changed the information?
What exactly changed?
Which version was reviewed?
Who reviewed it?
Who approved the final version?
When was that approval given?
Which approved version subsequently became available for use?
What evidence of those decisions still exists?
That is not simply an approval problem.
It is a communication accountability and evidence problem.
Where the evidence chain starts to break
In many regulated organisations, customer communications pass through several systems and teams before they reach the customer.
The wording may live inside application code.
A change might begin in a Jira ticket.
Compliance feedback may arrive through email or Teams.
A developer updates the template.
Approval may be recorded somewhere else.
The change then becomes part of a software release.
Each individual step may make sense.
The problem appears when somebody later needs to reconstruct the complete decision.
Version ambiguity
Several versions of the same communication may exist, while establishing exactly which version was reviewed, approved and ultimately used becomes difficult.
Approval ambiguity
An organisation may know that a change was approved without retaining a clear connection between the approval decision and the exact version that was approved.
Change ambiguity
When communication content is embedded in application code, a wording change can become part of a larger engineering release rather than a clearly identifiable communication decision.
Evidence reconstruction
When Compliance, Internal Audit, senior management or a regulator later asks what happened, teams may need to reconstruct the story from tickets, emails, messages, source control and deployment history.
The control may have existed.
The problem is proving how that control operated around the specific communication in question.
What a controlled communication workflow changes
A controlled workflow does not replace human judgement.
And it cannot guarantee that people will act honestly.
What it can do is create structure and evidence around the decisions people make.
For regulated customer communications, that can include:
Controlled editing
Changes are made within a defined workspace rather than across uncontrolled copies of documents or templates.
Version control
Each material change creates a traceable version, preserving the history rather than simply replacing what existed before.
Review and approval workflow
The organisation can connect a specific version with the people who reviewed and approved it, together with the timing of those decisions.
Controlled release
Only the appropriate approved version becomes available for use by downstream systems.
Personalised communication generation
Applications use the API to produce the correct approved communication using the customer, product or event data supplied at the point it is needed.
The content can therefore remain controlled and approved while the resulting communication is still personalised for the individual customer or situation.
Communication evidence
The governance history remains connected to the communication lifecycle, creating a clearer record of what changed, which version was authorised and how it progressed through the workflow.
In CommsPliant, that governance evidence is captured in the CommsPliant Evidence Vault, giving teams one place to return to when they need to trace the history of a communication decision.
The evidence is created as the work happens, rather than reconstructed afterwards from separate systems.
The result is not simply better template management.
It is a stronger communication evidence chain.
The same problem looks different depending on who you ask
The underlying governance problem may be the same, but different teams experience it very differently.
For Compliance
The question may be:
Can we demonstrate that the communication went through the required review and approval process?
Compliance needs more than the knowledge that “somebody approved it.”
It needs confidence that the approval relates to the correct content and the correct version.
For Operations
The question may be:
Can we see which version is current, what changed and who approved it without searching across several systems?
For operations teams, fragmented communication management creates delays and uncertainty around changes that may otherwise be simple.
For Engineering
The question may be:
Can communication changes be controlled without repeatedly tying wording updates to software releases?
Engineering should not need to become the permanent intermediary between Compliance and Operations every time approved customer wording changes.
Different teams experience different parts of the pain.
But underneath them is the same question:
How do you control changes to regulated customer communications and preserve evidence of the decisions around them?
Where CommsPliant fits
CommsPliant is a working platform for regulated customer communications.
CommsPliant brings editing, review, approval, version control, controlled release and communication evidence into one governed workflow.
Business and operations teams manage communication content within defined controls.
Compliance reviews and approves changes.
Applications use the API to produce the correct approved and personalised communication using the relevant customer, product or system data.
Engineering retains control of the integration without needing to own every future wording change.
As the workflow progresses, the CommsPliant Evidence Vault keeps the history of communication changes, reviews and approvals connected to the process from the start — not pieced together afterwards.
This creates a clearer chain between:
what changed → which version was reviewed → who approved it → what became available for use → what evidence remains
CommsPliant is a working platform open to new clients and potential design partners.
We are speaking with regulated businesses that manage customer emails, PDFs, letters or other important communication templates through engineering-heavy or fragmented workflows and want a more controlled, auditable way to manage communication change.
The practical takeaway
The question for a regulated organisation is not simply:
“Do we have an approval process?”
A stronger question is:
“If somebody asks us six months from now, can we show exactly what changed, which version was approved, who approved it and what happened next?”
Controls cannot make people honest.
But when accountability matters, a well-designed control environment can make the evidence much harder to lose.