By AIGAS
AIGAS Weekly | 8 October 2026
Research window: 1–7 October 2026; checked Wednesday morning.
Could your firm explain which AI tools it uses, what they can access and who can stop them?
This week’s developments make those questions practical. ICAEW has examined prompt injection, TaxCalc has highlighted insurance-renewal questions, and Sage has acquired a platform for building AI-powered applications. A former OpenAI safety employee has also challenged the culture behind rapid deployment.
Our view is straightforward: useful AI adoption needs clear boundaries, evidence and people who can raise concerns. That is the approach behind our AI governance framework for accounting firms.
ICAEW: documents can carry instructions as well as information
On 1 October, ICAEW published an examination of prompt injection: hostile instructions placed within material an AI system reads. Its examples concern earlier incidents, rather than attacks newly disclosed this week.
The underlying risk is also explained in NCSC guidance. An attacker may try to redirect a model into revealing information or triggering unintended actions.
For us, this changes how firms should assess connected tools. Consider an assistant reading incoming client emails. What else can it access? Can it send messages, amend records or reach another client’s documents?
Ask the supplier how those boundaries are enforced. Restrict access to the task, test the workflow and make sure consequential actions have an appropriate approval step. Training helps staff recognise problems, but technical safeguards need to support them.
TaxCalc: be ready to explain AI use at renewal
In commentary published on 2 October, TaxCalc says professional indemnity renewal packs increasingly ask which AI tools firms use, what work they support and who reviews their output.
This is vendor commentary, not a universal insurance condition. Firms should confirm their own insurer’s questions and policy wording with their broker.
We see a useful prompt to get the evidence organised. A partner should be able to describe actual practice, including embedded AI and tools staff use informally.
Start with the tool, its purpose, the client information involved and the reviewer. Keep a record of training and exceptions. That makes a renewal discussion more concrete and helps the firm manage its work throughout the year.
Sage: easier application building still needs ownership
On 5 October, Sage announced its acquisition of WholeHelp, whose AI Studio powers Sage 100 Experience Edition. Sage describes tools that turn natural-language requirements into applications and create automated workflows.
The technology is already used in France. Wider expansion is an intention; the announcement does not confirm UK availability.
Our takeaway is that easier creation makes ownership more important. If a team can build a useful dashboard or automation quickly, someone still needs to approve its access, test its calculations and maintain it.
For vendors and implementation partners, make that handover explicit: who owns the workflow, what was tested and what happens when a connected system changes?
OpenAI criticism puts escalation culture in focus
In an essay published on 3 October, former OpenAI safety employee David Robinson criticised the company’s deployment culture. Reuters reported his concerns and OpenAI’s response: the company said it pauses training or withholds models when necessary.
Robinson’s criticism is his assessment, not an independently established finding.
For accounting firms, the useful question is closer to home. Can someone flag an unreliable result without feeling they are obstructing progress? Who can pause a workflow when its controls are not working?
We would make that authority explicit. A contained pilot is valuable when concerns lead to action and lessons feed into the next decision.
This week’s action for your firm
Choose one AI-assisted workflow and check:
- Access: What information can it read, and what actions can it take?
- Evidence: Can we show its owner, review process and training record?
- Escalation: Who can pause it, and how are concerns recorded?