Outlook
Part of Accounting services outlook: six signals shaping 2027
Five risks to rehearse before 2027, from MTD reviewer queues to an AI that invents tax law
Exercise five accounting service risks for England in 2027 covering MTD capacity, agent registration, AI error, supplier outage and filing preparation.
Scenarios do not predict that an event will occur. They test whether the practice can detect a credible problem, make a decision, protect clients and recover before consequences grow. Run them with named participants and preserve findings.
What to take away
- Scenarios test whether a practice can detect a problem, decide, protect clients and recover before consequences grow.
- Each exercise needs named participants, staged facts and preserved findings, not a discussion that changes no control.
- Score authority, deadline protection, confidentiality, technical correctness, communication and recovery separately so one fast outcome hides no failure.
- Verify supplier claims against the current official record, including the 2028 accounts mandate date.
- Turn findings into owned actions with dates and rerun the failed stage.
Scenario 1: MTD onboarding creates a reviewer queue
Several clients enter the digital workflow with incomplete opening records. Capture succeeds, but uncertain classifications and duplicated transactions accumulate before quarterly updates.
MTD onboarding reviewer queue
- Clients enter digital workflow
- Incomplete opening records captured
- Uncertain classifications accumulate
- Duplicated transactions accumulate
- Reviewer capacity exceeded
- Pause or decline safely
Test segmentation, client cut-offs, exception ownership, reviewer capacity and escalation. HMRC's MTD for Income Tax guidance should control eligibility and process assumptions. Record what the practice can pause or decline safely.
Trigger: unresolved high-consequence items exceed the review capacity available before the internal deadline.
Scenario 2: the adviser entity lacks current registration evidence
A team discovers that its agent account, service enrolment and client authority are visible, but the required legal-entity registration cannot be confirmed.
HMRC's registration timetable describes staged windows, an application period and consequences of failing to register. Test who verifies the facts, stops affected interaction, obtains advice, protects deadlines and communicates without implying endorsement.
Trigger: registration evidence is absent or does not match the entity performing the work.
Scenario 3: an AI tool invents a plausible tax explanation
An approved assistant produces fluent text citing a rule that does not support the client's facts. A busy staff member is ready to send it.
Test source display, human review, confidence challenge, prohibited automation, audit history and correction. Use the ICO's AI guidance to inform data-protection controls for the actual system.
Trigger: the output cannot be traced to an authoritative source and client record.
Scenario 4: the core platform fails near payroll and filing work
Users cannot access records, the supplier status page is unclear and support is delayed. Staff begin downloading documents to personal devices.
Exercise alternative communications, protected backups, manual priority work, incident assessment, supplier escalation and restoration. Prevent an availability problem from becoming a confidentiality event.
Trigger: predicted recovery exceeds the approved tolerance for the next critical task.
Scenario 5: a supplier claims the accounts mandate starts in 2027
A sales proposal urges immediate purchase by describing commercial-software filing as a 2027 legal requirement. Companies House currently says the requirement begins on 1 April 2028.
Test claim verification, correction, procurement independence and the practice's genuine preparation plan. Preparation in 2027 may be sensible, but the decision must not rely on a false effective date.
Trigger: a material sales or website claim conflicts with the current official record.
Run and close each exercise
Give participants only the information their role would have. Record detection time, decisions, evidence preserved, customer impact, external advice, communications and recovery. Include a person who can challenge management assumptions.
Use a controller who reveals facts in stages and records what participants actually do. Do not rescue the team with information that normal monitoring would not provide. Invite relevant suppliers only after testing the practice's independent understanding of the dependency.
Score objectives individually: authority, deadline protection, confidentiality, technical correctness, communication and recovery. One fast outcome should not conceal a serious control failure.
Turn findings into owned actions with dates, then rerun the failed stage. Update scenarios after new rules, software, suppliers, staff or services. A tabletop meeting that produces no changed control is discussion, not assurance.
Before you act
- Name participants and give each only their role's information.
- Record detection time, decisions, evidence and customer impact.
- Include someone who can challenge management assumptions.
- Do not rescue the team with information normal monitoring would not provide.
- Score each objective separately rather than one overall result.
- Rerun the failed stage after new rules, software or staff.
Common questions
What is the point of running these scenarios?
The article says scenarios do not predict events. They test whether the practice can detect a credible problem, make a decision, protect clients and recover before consequences grow. Run them with named participants and preserve findings, then turn findings into owned actions with dates.
How should a practice handle a supplier claiming the accounts mandate starts in 2027?
Companies House currently says the requirement begins on 1 April 2028. Test claim verification, correction, procurement independence and the practice's genuine preparation plan. Preparation in 2027 may be sensible, but the decision must not rely on a false effective date. A material sales claim conflicting with the official record is the trigger.
What should be recorded during each exercise?
Record detection time, decisions, evidence preserved, customer impact, external advice, communications and recovery. Use a controller who reveals facts in stages and records what participants actually do. Score objectives individually: authority, deadline protection, confidentiality, technical correctness, communication and recovery. Invite suppliers only after testing the practice's independent understanding of the dependency.
